cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual



 o T Y  
PreviousContentsIndex



8The DO_MY_JOB procedure contains the following commands:

 

"
)$! SOME PROCESSING HAS BEEN DONE AND THE  )$! PROCEDURE ARRIVES AT ONE OF THE BELOW  $! EXIT POINTS.  $!  $IT_WORK_OKAY:  ,$ EXIT 1 ! ANY ODD NUMBER SIGNIFIES SUCCESS  $!  $IT_FAILED:  -$ EXIT 0 ! ANY EVEN NUMBER SIGNIFIES FAILURE  




GThe EXIT command in the above procedure returns a completion status to Gthe point of invokation (i.e. the "@" command). The DCL symbol $STATUS @in the parent procedure is then load with this code. Since that Aprocedure immediately ends this value is then passed back to the GSCHEDULE System and used as the completion status for the job.

BCertain DCL symbols are automatically established when the job is ?entered into an execution batch queue. The various symbols are: ! &                                          
Symbol Description
 SCHEDULE_FULL_NAME  job name and directory
 SCHEDULE_NAME  job name
 SCHEDULE_SET_ID  current set id. number
 SCHEDULE_SET_TAG  current set tag value
 SCHEDULE_SET_PARAMETER ! current set parameter value
 SCHEDULE_STEP  current job step
 SCHEDULE_ENTRY # scheduling queue entry number
 SCHEDULE_RESTARTING  0/1 restarting flag
 SCHEDULE_RESTART_COUNT  number of restarts done
 SCHEDULE_RESTART_LIMIT  maximum allowed restarts


BAll the above symbols are entered into the DCL GLOBAL symbol table6and are available throughout the execution of the job.<

2.1.4 Jobs with no DCL commands



@A job that does not have any DCL commands associated with it is Fprocessed through the system in a slightly different fashion from one .that does. Such a job is never entered into anDexecution batch queue. These jobs are marked as having successfully *completed whenever execution is requested.

GThis type of job is very useful when a more complex scheduling mode is Dneeded than what is provided by a single job. For example, two data Hfiles are required before a job can execute. A single job can only wait Ffor a single file. In this case two jobs are defined each one waiting for one file.

AThe first job initiates the second job. The first job has no DCL Bcommands associated with it. All the job commands are part of the Gsecond job. The first job will never be entered into a execution batch Hqueue. It will however proceed through the various scheduling queues in Fa normal fashion. Once both files have been found the second job will (be entered into a execution batch queue.




 o V T Y  
PreviousNextContentsIndex