1.11 Here’s what I tried to do. My job JBACKUP runs at 10:00 AM every Monday and generates all the full backups for the week that will run each night. It also re-runs itself in theory every Monday at 10:00 AM. Come to find out after coming to work today that it streamed approximately 84 copies of the full backup job and one copy of itself for next week. What happened?
The problem is you used the command
STREAM JBACKUP.OPERATOR.SYS;at=10:00;DAY=MONDAY
too soon. Because this job is actually executing this command at 10:00 AM on a Monday, it will physically stream this job NOW, not next Monday. The streamed job will also stream this job again, as many times as possible until 10:01 AM is reached, when it will correctly stream itself for next Monday at 10:00 AM. A solution would be to put a PAUSE 60 before the command to stream the JBACKUP job for next Monday.