If you customize control group weekly activity and also schedule backups late at night, you need to make sure the backup completes before the start of the next day. Scheduling delays could cause the backup control group to run later than scheduled, resulting in missed saves. Assume the following backup control group is scheduled to run nightly at 23:00.
Display Backup Control Group Entries RCHAS400
Group . . . . . . . . . . : SAMPLE
Default activity . . . . : *BKUPCY
Text . . . . . . . . . . : Create sample backup control group
Auxiliary Weekly Retain Save SWA
Backup List Storage Activity Object While Message
Seq Items Type Pool Device SMTWTFS Detail Active Queue
10 *EXIT *DFTACT
20 LIB1 *SYSBAS F *NO *NO
30 LIB2 *SYSBAS FIIIIII *NO *NO
40 *EXIT *DFTACT
Bottom
Press Enter to continue.
F3=Exit F11=Display exits F12=Cancel F14=Display client omit status
Suppose that the job scheduler submits the control groups to the same job queue that is used by the month-end batch job such that this backup control group does not start running on Saturday night as 23:00, but on Sunday morning as 00:00:03. When the backup starts to run, BRMS will retrieve the current date and because it is Sunday instead of Saturday, the following occurs:
You can easily avoid these problems by ensuring that the batch job queue allows more than one job to process, or use different batch job queues.