join
Defines a set of joined dependencies on a job or job stream. The set of joined dependencies is satisfied when the specified number of dependencies are met.
Syntax
[join join_name [number | numconditions | ALL] OF
DESCRIPTION "..."]
...
ENDJOIN
Arguments
- join_name
- A meaningful name for the set of joined conditions. The maximum length is 16 characters.
- number
- The number of dependencies that must be met for the joined conditions
to be satisfied. Supported values are:
- 0
- All dependencies must be met.
- 1
- The number of dependencies that must be met for the joined conditions to be satisfied.
- numconditions
- The number of dependencies that must be met for the joined conditions to be satisfied.
- ALL
- All dependencies must be met for the joined conditions to be satisfied
- DESCRIPTION
- A meaningful description for the set of joined conditions. This argument is optional.
Comments
For any single object, you are limited to a maximum of 4 join instances for each object with unlimited conditional statements within each join.
On a job, you can define standard and conditional dependencies, both internal and external.
On a job stream , you can define standard and conditional dependencies, only internal.
Internetwork dependencies are not supported.
Examples
The following example shows a
job stream containing the following dependencies:
- A follows dependency on a job stream in ABEND or SUPPRESS state
- A set of joined conditional dependencies, containing two dependencies, the first on job nc007108#COND_DEP_JS1.COND_DEP_J1, which must finish successfully for the dependency to be satisfied, the second on job nc007108#COND_DEP_JS2.COND_DEP_J2, which must meet the EXT_STATUS_PREREQ_SUCC_2 condition. This condition is defined by the user when creating the job definition. At least one of these conditions must be met for the set of joined conditional dependencies to be satisfied.
- A follows dependency on an external job stream in EXEC state.
- A second set of joined conditional dependencies, containing two dependencies, the first on job CDJ_PRED_2_163955532 which must be in SUCC state and the second on job CDJ_PRED_1_163955532, which must be in INT_STATUS_PREDEC_SUCC_1 state. The second condition is defined by the user when creating the job definition. Both these conditions must be met for the set of joined conditional dependencies to be satisfied.
SCHEDULE nc007108#CDJS_163955532
FOLLOWS nc007108#COND_DEP_JS1.@ IF ABEND | SUPPRESS
JOIN JOINDEP_COV_01 1 OF
DESCRIPTION "Description for join JOINDEP_COV_01"
FOLLOWS nc007108#COND_DEP_JS1.COND_DEP_J1 IF SUCC
FOLLOWS nc007108#COND_DEP_JS2.COND_DEP_J2 IF EXT_STATUS_PREREQ_SUCC_2
ENDJOIN
:
nc007108#CDJ_PRED_1_163955532
nc007108#CDJ_PRED_2_163955532
FTA_nc007108#CDJ_FTA_163955532
FOLLOWS nc007108#COND_DEP_JS1.COND_DEP_J1 IF EXEC
JOIN JOINDEP_COV_02 ALL OF
FOLLOWS CDJ_PRED_2_163955532 IF SUCC
FOLLOWS CDJ_PRED_1_163955532 IF INT_STATUS_PREDEC_SUCC_1
ENDJOIN
END