| Previous | TContents | YIndex |
F The set tag value is used to pass data between jobs in a job set. The G first job in a job set that gets initiated will either pick up the set G tag value from the initiate operation or from the job tag value in the control file.
G For example, we have a series of jobs (MONTHLY, DAILY and REPORT, each F job initiates the next in this order). The MONTHLY job when completed F initiates DAILY. DAILY then initiates REPORT. In the REPORT job it is F important to be able to identify which job came first (either MONTHLY H or DAILY). This is easily done by establishing a default tag values for " each job in the following fashion.
|
" 4 $ SCHEDULE MODIFY MONTHLY/GENERAL=JOB_TAG:"MONTHLY" 0 $ SCHEDULE MODIFY DAILY/GENERAL=JOB_TAG:"DAILY" |
H In the REPORT job a check of the tag value can be made to determine how the set was started.
|
" < $ IF SCHEDULE_SET_TAG .EQS. "MONTHLY" THEN GOTO EXTRA_STUFF $! . . $EXTRA_STUFF: |
3 2.1.16.3 Using set ids
G The set id. number is a number that is used to identify a job set. All A members of a job set are assigned the same job set number during C processing. The job set number can be left off and the system will A automatically assign one. Alternately a number can be explicitly G provided when the first job of the set is initiated. The automatically assigned numbers D are always in the range 1 to 99,999. Thus it is best to only assign # manually numbers greater than this.
C The set number is needed if a failed job must be rerun manually to F allow a job set to complete its processing. For example to start up a E job to just run by itself and use a given set id., use the following command.
|
" ! $ SCHEDULE SUBMIT JOB1/SET_ID=23 |
A 2.1.17 Automatic job restarts
G Any job can be set up to be automatically resubmitted for execution if - a failure occurs. Typical failures are a node > shutdown or a program aborting. In a cluster environment it is F useful to have jobs submitted into a generic batch queue. In this way D if a node goes down the job gets resubmitted into the generic queue 5 which can then in turn route the job to another node.
D To enable restarts on any particular job set the restart count to a number greater then zero.
|
" 8 $ SCHEDULE MODIFY [DEMO.A]START/GENERAL=RESTART_COUNT=4 |
H The restart count indicates how many times a job can be restarted if it : fails. After this number of restarts have occurred the job @ is considered to have failed. Once a job has terminated (either E successfully or failed) the initiate list associated with the job is : examined and any appropriate jobs on the list are started.
A A group of DCL symbols is automatically set up whenever a job is < submitted. These symbols can be used by the job to determine F whether or not the job is restarting. The DCL symbols used are listed below:
| Symbol | &Description |
|---|---|
| SCHEDULE_STEP | current step number |
| SCHEDULE_ENTRY | # scheduling queue entry number |
| SCHEDULE_RESTARTING | ! 0 or 1 if job is restarting |
| SCHEDULE_RESTART_COUNT | + number of restarts that have occurred |
| SCHEDULE_RESTART_LIMIT | allowed number of restarts |
| Previous | VNext | TContents | YIndex |