Solution document for running a restricted state backup

Console access is required to do that and that's a complex process.  Transferring your job into the QCTL subsystem is not the same as working from the console in restricted state.  That is what Lisa thought and when she ran the backup, it took the system down and ended her session. 

Before I could use the console, I had to fix it.  

On systems where the console is rarely used,  connectivity has to be reestablished before the console will connect to the system.  

If you need a system backup run, let me know and I can run them for you.  It's not an easy thing to document; there are a lot of steps, and the steps are not always the same.  Steps depend upon the state of the system and what is running at the time you need to bring it down.

These are the high-level step involved with running a restricted state save:

1. Start the console
2. Access the console
3. Review messages in QSYSOPR, handle any outstanding messages requiring a response
4. End the system gracefully
5. Run the backup
6. Validate the backup
7. IPL
8. Check the IPL status after the system comes back up
9. Scan the IPL log for error conditions, resolve if found
10. Review messages in QSYSOPR again, handle any outstanding messages requiring a response
11. Restart the system to run the startup job
12. Verify the startup job completed successfully
13. Validate all production processes are running
14. Verify users are able to log back in to QINTER