I'm suggesting that if you have a startup routine which brings you into ISPF, that routine can issue whatever commands you need executed after ISPF finishes.
If that routine queues a command to start ISPF and then immediately ends, it will have to be changed to actually issue the ISPF command directly so that when the user ends ISPF the startup routine will still be alive to issue the back-end commands.
Frank Clarke
Tampa Area REXX Programmers' Alliance
REXX Language Assn Listmaster