Initiates

The forward going connection is called an "initiate". Initiates are triggered when a job completes. Associated with each initiate can be a condition or severity level at which the next job should be triggered. In this way, different branches can be taken based on the success/failure of a particular job.

Jobs that are initiated when the currently selected job finishes. Conditions can be set to control under what circumstance a job is initiated. Press this button to bring up this list. Click on the link to learn more about the operators and variables that are used in the initiates list. 

To add an Initiate job to the list fill in the name or click on the orange button beside the field and select a job from the Job list  and click Apply to add.

See Add Conditions to an initiate for information on adding conditions.

 

Select a job initiate:

 

 

Click More to add additional Initiate jobs. Click Less to remove the last item from the list.

Setting initiate conditions
The initiate list is made up of jobs that are executed upon completion of the currently selected job. A job can have any number of initiate jobs. On the completion of a job, all initiate jobs are readied for execution.

Each initiate branch can be conditioned only to occur under certain circumstances. Any of the conditions being true is enough to allow the initiate to execute (OR condition). The following conditions can be applied to an initiate:
 

Severity level (success, warning, error and fatal)

or the numeric value of the code can be specified. The initiates are entered in a list that can be specified with the job entry in the database.

Completion status

Completion status of the job is 1 if successfully completed and 0 if failed.

Expression is true

An expression can check the status of variables.

Comparison is true

A comparison between a parameter or variable and a value (including predefined values such as $Day or $Time).

 

The initiates are entered in a list that can be specified with the job entry in the database.

Each line in this list specifies a single job and under what conditions it should be initiated. The format of each line is detailed below:

General format:

[node::]job_name [,condition,...] [,ONE_OF]

 the job name can be any of the following:

job
[directory]job
[directory.subdirectory]job
[.subdirectory]job

the conditions are one or more of the following:

 

   ANY

start this job always (default)

   SUCCESS

only start if job finished successfully

   WARNING

only start if job finished with a warning

   INFORMATIONAL

only start if job finished with informational message

   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"

   IF CONDITION

only start if condition is met

 

The default condition is ANY. If no conditions are specified then it is always started whether the job succeeded or failed.

 

Here is an example of a initiate List for [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

Using variables, one or more initiate jobs can be selectively suppressed depending on the results of a variable evaluation attached to the initiate.

For example:

NEXT_JOB, IF DISK .lt. 1000
REPORT, IF RUN_REPORT == "TRUE"
FINISHED, SUCCESS, WARNING