It is advisable to suspend the execution of all jobs while a STORE is
being performed. (If a job step attempts to open a file for write
access which is being stored, the open fails, with possible negative
consequences for the job.)
 |
 |  |
 |
 | NOTE:
Advise users not to schedule jobs during the time schedule for backups.
STORE does not copy files opened by suspended jobs. Therefore, a backup
undertaken with suspended jobs may be incomplete. |
 |
 |  |
 |
To check whether there are any jobs running on the system, enter:
If you see a message stating NO SUCH JOBS, or if the list contains
no executing jobs (check the STATE column for EXEC), skip to the "Send
Another Warning" step below. If any jobs are in the EXEC state, you
should temporarily stop them. To do so, use the job numbers that appear
in the first column on your screen with the BREAKJOB command, as
follows:
Repeat the BREAKJOB command for each executing job in the list. When
you have suspended all executing jobs, check their status by entering:
Each job should now be listed as SUSP, or suspended. However, jobs
that have resources allocated to them do not suspend immediately; you
may have to wait for them to suspend.