Re: Save-while-active questions / concerns

Thanks to everybody who replied.  I think I've got a better handle on the
concepts that I was missing.  Al makes a good case for the TAA Tool
SAVxxxACT commands which handles a lot of the details.  I may still
implement it with SAVLIB but we'll see.

The steps (as I understand them) are:
1.  Submit a job to QCTL to do a ENDSBS *ALL *IMMED.
2.  When a restricted state has been achieved start another subsystem.
3.  Starting that subsystem will also start the QSYSWRK subsystem so do a
ENDSBS QSYSWRK *IMMED
4.  Submit a job to the newly activated subsystem to monitor a message
queue for the message that the checkpoint has been established.
5.  Issue the SAVLIB command from the QCTL job with SAVACT(*SYNCLIB) PRECHK
(*YES) SAVACTWAIT(0) and a SAVACTMSGQ specified.
6.  When the job in the new job queue gets the checkpoint message then run
the job specified by the QSTRUPPGM to make the system available for use.

Feel free to correct me if I missed something or got something wrong.
Thanks again everybody.


Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx