For both file equations, and the command stack, we need an automatic or
optional method of saving the environment so that if the network drops the
connection or the PC needs to be rebooted (I know these circumstances are
very rare in the computing world <g>), the carefully built set of file
equations and good commands can be reconstituted.

Yes, I know that I can issue all of the file equations that I need and
execute a LISTREDO;UNN into a file and make that a command file. That's
tedious, and I have to maintain the file. As for preserving my commands,
that would require a plethora of hard-to-maintain command files.

In any event, I'd have to do this manual step consciously before my session
fails or before I run out quickly to catch the train home or before I get a
call from the operator that there is a problem that requires a START
NORECOVERY or -- well you get the idea.

As for implementing the command environment, perhaps the MPEX methodology
might be a model. The command stack is stored in a ;TEMP file. My UDC for
MPEX is

     MPEX PARM=1 INFO=" "
     IF FINFO ("MPEXREDO","EXISTS") THEN
         FILE MPEXREDO;TEMP
         COPY MPEXREDO,*MPEXREDO
         PURGE MPEXREDO
     ENDIF
     FILE MPEX.REDO.VESOFT=MPEXREDO,OLDTEMP;SHR;TEMP
     RUN MAIN.PUB.VESOFT,MPEX;PARM=!PARM;INFO="!INFO"
     SAVE MPEXREDO

Admittedly, this does not preserve the MPEX commands in the event of a
crash, but does keep the commands from one invocation of MPEX to the next,
and it is portable from one account to another.

====================
Leonard S. Berkowitz
(work) mailto:[log in to unmask]