Parent abend

Parent abend usage

The parent abend scenario describes the following functional requirements:

• Getting the parent job status.
• If the parent job status is SUCC, this is considered as BAD.
• If the parent job status is ABEND, this is considered as GOOD.

This section describes only the case when the parent job ends in the SUCC state.

Parent abend ending in SUCC state

Figure 1 shows the job stream with the PARENT_ABEND function.

The job stream looks like the simple branch, the only difference is that you specified the parameter CONDITION_SWITCH=PARENT_ABEND for the branch job.

Figure 1. Parent abend (SUCC) definition

The job log shows the output of the generic branch job instance:

============ START of branch job BRANCH_1 ==========
================ Job environment ===================
MASTER_PLATFORM=UNIX
STREAM_NAME=GBJ_PARENT_ABEND
STREAM_CPU=SYDNEY
BRANCH_JOB_NAME=BRANCH_1
PARENT=IMPORTANT_JOB_SUCC
==========================================================
============= Input parameters =============
CONDITION_SWITCH=PARENT_ABEND
ACTION_SWITCH=CANCEL
==========================================================
============= MAIN DECISION MAKING =============
Evaluation dependent on PARENT_ABEND
FALSE: Searched for ABEND parent. 
Status of PARENT JOB(IMPORTANT_JOB_SUCC) is SUCC.
==========================================================
============= Action on STOP Branch =============
Performing action CANCEL on job SYDNEY#0AAAAAAAAAAAAEDA.G_DO_THE_GOOD_THING
%cj SYDNEY#0AAAAAAAAAAAAEDA.G_DO_THE_GOOD_THING;schedid;noask
Command forwarded to batchman for SYDNEY#GBJ_PARENT_ABEND[(2314 12/16/07),
   (0AAAAAAAAAAAAEDA)].G_DO_THE_GOOD_THING
==========================================================
============= Action on RUN Branch =============
Performing action RELEASE on job SYDNEY#0AAAAAAAAAAAAEDA.B_DO_THE_BAD_THING
Releasing of job SYDNEY#0AAAAAAAAAAAAEDA.B_DO_THE_BAD_THING is NOT NECESSARY,
because priority=10
==========================================================
============= Statistics of branch job BRANCH_1 =============
FALSE: Searched for ABEND parent. Status of PARENT JOB(IMPORTANT_JOB_SUCC) is SUCC
For action CANCEL - RUN_BRANCH=B_DO_THE_BAD_THING and 
   STOP_BRANCH=G_DO_THE_GOOD_THING
BRANCH selected to STOP: G_DO_THE_GOOD_THING
BRANCH selected to CONTINUE: B_DO_THE_BAD_THING
CANCELED_JOBS: G_DO_THE_GOOD_THING
PAUSED_JOB:
RELEASED_JOB:
============ END of branch job BRANCH_1 ==========

Required input parameters

Table 1 shows the parameters required for the negative branch scenario.

The following example shows the parameter definition. The text is entered into the Comments field of the job stream definition.

BRANCH_1-BEGIN
CONDITION_SWITCH=PARENT_ABEND
BRANCH_1-END

For details about how to specify the branch job parameters, see Specifying the branch job parameters.

Placing the branch job into the job stream

Put the generic branch job into the job stream after the parent job and rename the good child with the "G_" prefix and the bad child with the "B_" prefix.

Also, follow the best practice and rename the branch job with a suffix consisting of the underscore character and a numeric value. A typical name for the first branch job within a job stream is BRANCH_1.