We did a full save with minimal down time like so if I recall correctly:

1) Take the system to restricted state
2) Control group changes startup program to *NONE, does the SAVSYS. We also had it do LINK and DLO (DLO always gave us a few objects not saved if we didn't do it restricted) and I think *IBM.
3) Control group starts a subsystem, submits job to monitor for SWA sync and kicks off SWA of ALLUSR
4) The MONSWA program would wait for the SWA sync point (which was pretty quick since the system was still very close to restricted) and kick off the startup program and change the QSYSSTRUPGM back to what it should be.

It's been a while since we did that (previous shop), but it worked pretty well (especially since it replaced GO SAVE 21!)

Jeff Carey, MSIT, MBA
Sr. Systems Administrator

This communication, including any attachments, may contain information that is confidential and may be privileged and exempt from disclosure under applicable law. It is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender. Thank you for your cooperation.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page