Previous Topic: Failover and Recovery for an Unscheduled OutageNext Topic: Troubleshooting Best Practices


Quiesce Job Submission

During scheduled outages, it is sometimes best to quiesce job submission. This topic discusses the best practices for stopping job submission when preparing for a system IPL or other outage.

Enter the following top line commands:

HOLD,Q=REQ
HOLD,Q=RDY
SSCAN,SCAN=HLD

These commands result in the following:

You can stop schedule scan from waking up and bringing in work (turn off schedule scan) by issuing the following command:

SSCAN,TIME=0

If any jobs are active, you can wait for their completion if you prefer.

If you have not shut down CA7ONL, issue the following commands when you are ready to start regular processing:

RELEASE,Q=REQ
RELEASE,Q=RDY
SSCAN,SCAN=REL

These commands post the HOLD requirements added to jobs by the earlier HOLD commands. These commands and stop the adding of a HOLD requirement on all jobs that later come into the request queue (negates the SSCAN,SCAN=HLD command entered earlier). You can RELEASE the HOLD requirement on a job by job basis when you do not want to post all jobs that are held.

If you shut down CA7ONL after quiescing, consider starting CA7ONL with schedule scan turned off. To do so, change the initialization file INIT statement to RUNOPT=NSTA. You can also stop job queue movement (going from the request queue to the ready queue for submit) by changing the SCHEDULE statement in the initialization file, adding STOPQ=YES.

If you start CA7ONL with schedule scan turned off, you can turn it on with the following top line command:

SSCAN,SCAN=SCH

And if you chose to stop the queues (STOPQ=YES), you can start them with the following command:

START,Q=ALL

Next, you can issue the RELEASE commands described previously to post the HOLD requirements.

Business Value:

Quiescing job submission helps ensure that nothing is submitted without you first performing checks on your system.