Use the repeat scheduling feature to run jobs repeatedly throughout the day.
You can set up a job to run continuously. Use trailer steps in the job to DEMAND itself back in during specified time frames with #J or #X statements around the SASSTRLR step. These repeat runs cannot be forecasted and required JCL changes.
We recommend using the repeat scheduling feature to run jobs repeatedly throughout the day. Jobs can be scheduled to run periodically throughout a 24 hour period on one SCHID without having to DEMAND themselves back in by using this feature. The repeat scheduling feature can be forecasted.
Business Value:
This feature lets you run repeatedly a job on one SCHID.
Additional Considerations:
On the DB.2.1-E panel, specify the interval between iterations of the job. Also specify how many times to repeat the job, when to no longer repeat the job, or both.
The repeat run only occurs when the latest iteration of the job completes successfully. The decision to repeat is made at successful completion of previous iteration. The next iteration is not added to the request queue until successful completion (or forced complete).
The DEMAND(H) command also has a repeat option for more scheduling flexibility.
Repeating jobs can trigger other jobs, but it is best that repeat jobs do not have job requirements. The reason for no job requirements is because job requirements must meet sequence testing. In other words, the required job has to run between each run of the job with the requirement.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|