cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual


 o T Y  
PreviousContentsIndex

3

2.1.9 Activated by



>The activated-by list that is associated with each job in the FSCHEDULE database specifies all jobs that reference this job =on their initiate lists. The activated-by list is the inverseCof the initiate list. This list can be manually updated if needed. ;Normally only the initiate list is modified and the system ,automatically updates the activated-by list.

FThe SCHEDULE REBUILD command can be used to recreate the activated-by "and held-up-by lists for all jobs.6

2.1.10 Prerequisites



FA job can have any number of prerequisite jobs. A job cannot #be submitted into a queue until all.prerequisite jobs have completed successfully.

4Figure 2-2 Prerequisite job example



mFor example in Figure 2-2 Job D cannot be submitted until Jobs B and EC have completed successfully. Job B cannot be submitted until Job A has completed successfully.

HThe prerequisites are entered in a list that can be associated with any Cjob entry in the database. All the jobs on this list must complete successfully before the job is allowed to proceed.

GEach line of this list specifies one job either on the local system or >on a remote system. The format of each line is detailed below:

 

" 
 General format:  $    [node::]job_name [IF condition]  *The job name can be any of the following:      job     [directory]job      [directory.subdirectory]job     [.subdirectory]job  



lFor a description of all conditional operators, see Section 3.1.4. Any Eof the pieces of the name that are left off are picked up by default Ffrom the current job. A typical prerequisite list can be displayed by using the following command:

 

" 
 /$ SCHEDULE TYPE/PREREQUISITES [DEMO.A]REPORT_3  [DEMO.A]REPORT_3.prerequisites  "    IF COUNT .NE. 4 THEN UPDATE_C 
    UPDATE_B 
    UPDATE_A  



GThe addition of a node name to a job name indicates that the system is Gto send a message to that remote node requesting a return message when $the prerequisite job completes. ThisGis used in a "peer-to-peer" network configuration where another system H(or cluster) has its own scheduling database and job synchronization is -needed between these two independent systems.

EOne very important point is that the SET_ID is used to clarify which 8job is a prerequisite job. In other words if a job C hasHjobs A and B as prerequisites they must have completed successfully and Ebe members of the same set (i.e. have the same SET_ID) as job C. The Cmechanism that can be used to propagate the SET_ID is the initiate Glist. In this example all three jobs A, B, and C should be initiate by the same parent job.



 o V T Y  
PreviousNextContentsIndex