| Previous | TContents | YIndex |
0 2.1.8 Initiates
G A job can have any number of initiate jobs. On the completion > of a job all initiate jobs are readied for execution.
1 Figure 2-1 Initiates Job Example
? For example in Figure 2-1 H when Job A completes, Job B is readied and is immediately submitted for ? execution. When Job B completes Jobs C and D are ready and are $ submitted immediately for execution.
D Each initiate branch can be conditioned only to occur under certain F circumstances. The conditions are based on the completion code of the C job. The severity level (success, warning, error and fatal) or the + numeric value of the code can be specified.
G The initiates are entered in a list that can be specified with the job entry in the database.
1 Each line in this list specifies a single job and F under what conditions it should be initiated. The format of each line is detailed below:
|
" General format: 0 [node::]job_name [,condition,...] [,ONE_OF] * the job name can be any of the following: job [directory]job [directory.subdirectory]job [.subdirectory]job 1 the conditions are one or more of the following: 5 ANY - start this job always (default) 9 SUCCESS - only start if job finished successfully ; WARNING - only start if job finished with a warning K INFORMATIONAL - only start if job finished with informational message 8 ERROR - only start if job finished with an error = FATAL - only start if job finished with a fatal error ( CODE=n - start if status was "n" 4 IF CONDITION - only start if condition is met |
H The default condition is ANY. If no conditions are specified then it is F always started whether the job succeeded or failed. For a description U of all conditional operators, see Section 3.1.4.
E The ONE_OF control word indicates that only the first job of all the H ones marked with ONE_OF that has a matching condition will be initiated. A Any of the pieces of the name that are left off are picked up by G default from the current job. A typical initiate list can be displayed by using the following command:
|
" * $ SCHEDULE TYPE/INITIATE [DEMO.A]UPDATE_A [DEMO.A]UPDATE_A.initiates < IF JOB_CHECK == FAILED THEN UPDATE_A_FAILED,ERROR,FATAL REPORT_1,SUCCESS,WARNING SUMMARY_A,SUCCESS,WARNING ERROR_4,CODE=18934028 |
G The addition of a node name to a job name indicates that the system is A to send a message to that remote node requesting that the job be initiated on that node. This G is 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.
D As one job initiates another job three bits of information are sent E along. They are the SET_ID, SET_PARAMETER, and SET_TAG. Of these the E SET_ID is the most important. The SET_ID identifies a job as being a ? member of a set. Only jobs of the same set can be connected by prerequisites conditions.
| Previous | VNext | TContents | YIndex |