cRSCHEDULE Automated Job Submission System Guide and Reference Manualc

SCHEDULE
Automated Job Submission System
Guide and Reference Manual


 o T Y  
PreviousContentsIndex



 

" 
 <$ SCHEDULE MODIFY ANALYSIS_JOB/RESOURCE=DISK:(DUA1:,100000)  



?The file requirement is specified as a single file that must beEfound on the system before the job is allowed to proceed to the next Hscheduling state. For example to have this same job not start until the <input file INDATA.DAT is present, use the following command.

 

" 
 B$ SCHEDULE MODIFY ANALYSIS_JOB/RESOURCE=FILE:SYS$LOGIN:INDATA.DAT  



3

2.1.3 Line Commands

EEach job has a series of DCL commands associated with it. These jobs /can do anything any ordinary VMS batch job can.

GEach line specifies a DCL command. The format of each line is detailed below:

 

" 
General format:      $ DCL_commands     .   .   .



FThe commands associated with a job can be displayed by using the TYPE command:

 

" 
 *$ SCHEDULE TYPE/COMMANDS [DEMO.A]UPDATE_B  [DEMO.A]UPDATE_B   +$! THESE ARE THE DCL COMMANDS FOR UPDATE_B  $!  $ RUN UPDATE_PROGRAM  



>The success or failure of a job is determined by checking the Dterminating status code of the job. This status code is obtained in Fdifferent ways depending on how the job terminates. All line commands Eplace their completion status codes in the DCL symbol $STATUS. Under Gnormal circumstances the value of this symbol at the end of the job is Fwhat is sent to the SCHEDULE System to use as the completion Fstatus of the job. Under abnormal circumstances were the job aborts orDis manually deleted out of the batch execution queue the completion Dstatus would be that error message. It is sent to SCHEDULE ESystem by the VMS JOB_CONTROLER. Below are some illustrations on how !the completion status code works.

ACASE 1: A particular job just needs to run a single program. The $command associated with this job is:

 

" 
 $ RUN SPECIAL_PROGRAM  



5The above single line is the entire job. This programDreturns a completion status to the system on exit. 2 VMS @then in turn places this value into the DCL symbol $STATUS. The FSCHEDULE System will then pick up this last status value and 6use it to represent the completion status for the job.

?CASE 2: A particular job entails executing several commands andEexplicitly specifying the completion status. The commands associated with this job are:

 

" 
 )$! SOME PROCESSING HAS BEEN DONE AND THE )$! PROCEDURE ARRIVES AT ONE OF THE BELOW  $! EXIT POINTS.  $!  $IT_WORKS_OKAY:  1$ $STATUS = 1 ! ANY ODD NUMBER SIGNIFIES SUCCESS  $ GOTO DONE  $!  $IT_FAILED:  2$ $STATUS = 0 ! ANY EVEN NUMBER SIGNIFIES FAILURE  6$ GOTO DONE ! ANY STANDARD VMS ERROR CODE CAN BE USED  $!  $DONE:  



?CASE 3: A particular job requires executing a standard command Eprocedure. The completion status will be provided by this procedure. (The command associated with this job is:

 

" 
 $ @SYS$LOGIN:DO_MY_JOB 





/   
N
Note

 O

2 One way to have a program terminate L and return a status code to the system is to use the system service  LIB$STOP.







 o V T Y  
PreviousNextContentsIndex