1. SNDBRKMSG to warn all users to sign-off due to Backup in 10 minutes
2. ENDSBS QINTER, QBATCH, QSERVER with OPTION(*CNTRLD) DELAY(*NOLIMIT)
3. After 10 minutes, ENDHOSTSVR SERVER(*ALL)
4. ENDTCP
5. ENDSBS QCMN, QINTER, QBATCH, QSERVER with OPTION(*IMMED) using CPF1054
6. After 5 minutes, start the backup.
7. Restart QCMN, QINTER, QSERVER, & TCP/IP
8. After the backup, restart QBATCH
This assumes that:
1. The procedure is either run from the console, or from a custom batch subsystem and job queue (external from QBATCH subsystem/jobq).
2. All memory resident programs check for the end-job status flag.
3. There are no other active batch or interactive subsystems. Steps 3, 4, & 5 will definitely kick out everyone but the console operator. Step 7 will allow people to connect/signon and initiate some jobs that may interfere with the backup. To remove this possibility, you could interchange steps 7 and 8. However, it is my experience that you should allow people to connect so that in case anything goes wrong, the technical staff can still get in to fix it remotely. You could opt to insert an initial sign-on program into your non-technical users’ user profiles to check if the backup is in progress, and if so, bar them with an informative message.