Conference iosg::all-in-1_v30

    David,
    
    OA$FORM_DISPOSE really should be working.  If you look at
    DOCCREATE.SCP, that's what it uses to determine if GOLD-F or GOLD-K is
    pressed.  If you're doing it interactively, you might not be seeing the
    correct OA$FORM_DISPOSE.  Try <EDIT "file"\GET #Z = OA$FORM_DISPOSE,
    then look at #Z.  It should be 0 or 2.  Maybe you're seeing the value
    after it's been reset by coming back to the menu screen? (but I think
    that would be 3)
    
    BTW, I didn't know OA$FORM_DISPOSE could ever be 4.  Does anyone know
    if this is an undocumented feature?
    
    -- Paul

    
    Well, let me try this from another angle.
    
    The customer wanted something set up that would allow them to invoke
    the WPS-PLUS editor from DCL, create a file, and then do some other
    stuff to it after leaving the editor.  Since the customer doesn't have 
    WPS-PLUS for VMS, the only way to access it is through ALL-IN-1.  So, I 
    wrote a little command procedure that basically invokes ALL-IN-1 with 
    an $ ALLIN1/SCRIPT = edit_script qualifier, and the edit_script calls the 
    ALL-IN-1 EDIT function to bring up the WPS-PLUS editor and exit from 
    ALL-IN-1 when the user exits the editor.
    
    This all works fine.  The problem comes about when users try to use
    such things as HELP or GOLD G from within the editor.  Pressing the
    HELP key, for example, produces the message:
    
      FORM USA_LK201
    
      You cannot exit here as you have an edit session open.
    
    Subsequent pressings of HELP result in an "Error occurred during
    operation: NULL_POINTER" message being displayed before dropping back
    to DCL.  Everything works fine when the same script is invoked _after_ 
    entering ALL-IN-1, rather than calling it from the /SCRIPT qualifier.
    GOLD G exhibits similar behavior.
    
    Any ideas?  Is this a question for the WPS-PLUS conference?
    
    - David
    
    
    

If I remember my WPS-PLUS correctly (and I may not!), the determination of
which terminal device to use for I/O is setup through logicals.  That's great
for the editing session, but Help and Gold-I and other terminal I/O outside
the editor code will be processing SYS$INPUT, which you may have pointing to
your command procedure, not the user's terminal.

Have you done:

	$ DEFINE/USER SYS$INPUT 'F$TRNLNM("SYS$OUTPUT")
	$ ALLIN1/SCRIPT=...

/Marty

    
    Redefining SYS$INPUT does enable the display of FMS forms so that HELP
    and GOLD G work properly, but it also seems to cause ALL-IN-1 to
    access violate if the user quits (GOLD K) rather than exits the editor.
    
    - David