CA JCLCheck Runtime Options › Description of Runtime Options › COND

COND

The COND option activates condition code simulation. If this option is specified without parameters, CA JCLCheck assumes that every step ends with a condition code of zero. This option also allows you to specify an alternate completion condition for a specific step.

This option has the following format:

CONd[(step.procstep code abendcc)]|NOCOND

Default: NOCOND

step.procstep

Defines the fully-qualified step name to which the completion code applies.

code

Defines the completion code value (0 to 4095) or one of the following keywords:

ABEnd, ABEndCC

abendcc

Defines either a system completion code (Sxxx) or user completion code (Uxxx). Specify S followed by three hexadecimal characters or U followed by a four-digit decimal user code.

• CA JCLCheck evaluates condition codes for IF statements and EXEC statements, including overrides from an EXEC PROC=statement. It skips any steps that have a condition satisfied.
• The default for the COND option is NOCOND. Thus, if you do not specify COND, CA JCLCheck assumes NOCOND, and every step runs regardless of condition codes specified in the JCL. If COND is specified without any parameters, CA JCLCheck assumes every step ends with a condition code of zero.
• If you specify ABEnd or ABEndCC, CA JCLCheck simulates an abnormal termination of the step and if there is any conditional disposition, CA JCLCheck uses all DD statements in the step. Execution of subsequent steps depends on the evaluation of an IF/THEN/ELSE/ENDIF construct with COND=EVEN and COND=ONLY as appropriate. Although subsequent steps can be bypassed, CA JCLCheck continues to analyze the JCL for syntactical (not logical) correctness.

  This option may be specified multiple times to simulate nonzero completion codes for more than one job step.

• If more than one COND option is specified for the same step name, CA JCLCheck observes the last COND parameter for the step.
• Typically only one job is processed when using the COND option to analyze conditional execution characteristics. If the input to CA JCLCheck is a series of multiple jobs, COND option specifications only apply to the first job stream. Condition code processing remains active for remaining jobs but all completion codes default to zero.

Examples: Assign completion codes

The following example causes CA JCLCheck to assign a completion code of 12 to the step named STEPA.PSTP2 as well as to simulate an abnormal termination of step STEPB. Conditional execution of all other steps is appropriately evaluated.

CON(STEPA.PSTP2 12) CON(STEPB ABEnd)

The following example causes CA JCLCheck to assign a user completion code of U1000 to the step named STEPA.PSTP2 as well as to simulate an abnormal termination of step named STEPA.PSTP2. Conditional execution of all other steps is appropriately evaluated.

CON(STEPA.PSTP2 ABEndCC U1000)