Go save option 23 is nice, but how about a way to do it from a scheduled CL job? I don't like to stay late.
The short answer .... NO
This is because the SAVLIB *ALLUSR command can only run from the console in a restricted state. The restricted state is the result of executing the ENDSBS SBS(*ALL)OPTION(*IMMED) command and this command can only be executed from an interactive job running in the controlling subsystem.
Option 23 from the GO SAVE menu executes the following commands:
ENDSBS SBS(*ALL)OPTION(*IMMED) CHGMSGQ MSGQ(QSYSOPR)DLVRY(*BREAK or *NOTIFY) SAVSECDTA SAVCFG SAVLIB LIB(*ALLUSR)ACCPTH(*YES) SAVDLO DLO(*ALL)FLR(*ANY) SAV DEV('/qsys.lib/tapexx.devd') + <--- Specify a real tape device name OBJ(('/qsys.lib' *OMIT) + ('/qibm/proddata'*OMIT) + ('/qopensys/qibm/proddata' *OMIT)) + UPDHST(*YES) STRSBS SBSD(QCTL)
There are third-party backup restore packages that can help you automate this process quite a bit.
MORE INFORMATION ON THIS TOPIC
Ask the Experts yourself: Our Backup & Recovery gurus are waiting to answer your questions.
Search400.com's targeted search engine: Get relevant information on backup & recovery.
Check out this Search400.com Featured Topic on backup & recovery.
Dig Deeper on Data backup, storage and retrieval on iSeries
Related Q&A from Ken Graap
Find out if log files can be omitted during a save without causing problems in a full restore. Continue Reading
The BRMS Network feature allows a BRMS system to connect to other BRMS systems via a network, and enables a user to consolidate media such as backup ... Continue Reading
The only option to correct damage preventing file journaling is to use the RCLSTG command. Continue Reading