We run a full backup from the console with the system in a restricted state. We have the job set to run at a specific time. The CL clears the operator message queue and changes the break level to 97. Recently we have been getting messages that prevent the backups from running, such as a forms error on a printer. When I checked, the messages are at a level 99 and as soon as the queue is cleared, they display back on the console preventing the backup from starting until the message is responded to. Has something changed on the level of messages or is there a good way around this problem?
If you are running this process unattended, then just change the QSYSOPR *MSGQ to HOLD:
CHGMSGQ MSGQ(QSYSOPR) DLVRY(*HOLD)
The messages are held in the message queue until they are requested by the user or program. After your BU finishes, set it back to DLVRY(*BREAK).
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 30 backup/recovery tips in 30 minutes .
Dig Deeper on Data backup, storage and retrieval on iSeries
Related Q&A from Ken Graap
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
IBM's iSeries Backup and Recovery manual answers many questions related to system backup and disaster recovery. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.