/
Creating Step Conditions

Creating Step Conditions

Jan 30, 2024

Overview

A z/OS JES batch job consists of one or more steps defined by JCL EXEC statements. The JCL EXEC statement identifies the program that the step is to execute. During job execution, steps are executed sequentially under conditions defined by the JCL statements. When a step completes execution, a Step Condition code is recorded by JES. The Step Condition code is either an integer condition code, in the range of 0 - 4095, or an ABEND code. If a step does not execute, which can be for a number of reasons, it is referred to as FLUSH'ed.

A task's status of SUCCESS or FAILED is determined by task exit code processing. The z/OS Task Details Exit Code Processing field specifies the method used to determine the task status for a z/OS batch job. When the Step Conditions method is selected, the task status of the z/OS batch job is controlled by the Step Conditions defined in the z/OS Task and parent workflow.

In addition to determining the z/OS Task status, Step Conditions provide a means to control the execution of job steps without any changes to the batch job JCL. A Step Condition definition can specify that job execution is halted, continued, or determined by a console operator. For example, if a multi-step job has a step that ends with a condition code of 8, you could include a Step Condition check to decide whether or not to run the following steps.

Step Conditions can be applied at the z/OS Task level or at the workflow level that apply to all z/OS tasks in that workflow and sub-workflows.
 

Note

If Step Conditions has been selected for Exit Code Processing, and you then select a different option, a confirmation pop-up displays to warn that any defined Step Conditions will be removed.

Runtime Monitoring

You can monitor Step Conditions at run time via the Activity Monitor, which lets you add or change Step Conditions for a single task instance and then re-run that job.

Creating a Step Condition

Step 1

From the Automation Center navigation pane, select Tasks > z/OS Tasks. The z/OS Tasks list displays.

Step 2

Select the task for which you want to create one or more Step Conditions. The z/OS Task Details for that task displays.
 

Step 3

In the Exit Code Processing field, select Step Conditions from the drop-down list and then click the Update button.

Step 4

Click the Step Conditions tab. The Step Conditions list displays a list of any currently defined Step Conditions for this task.
 

Step 5

Click New. The Step Condition Details pop-up dialog displays.
 

Step 6

Using the field descriptions, below, as a guide, complete the fields as needed.

Step 7

Click a Save button to save the record and return to the Step Conditions list.

Step 8

If appropriate, repeat these steps for any additional Step Conditions you want to add.

Step Condition Details Field Descriptions

The table below describes the fields and buttons in the Step Conditions Details pop-up dialog.

Field Name

Description

Field Name

Description

Step

Job step name to match. A blank value or an asterisk (*) will match any job step name. Generic matching characters asterisk (*) and question mark (?) match zero or more characters and one character, respectively.

Procedure

Procedure step name to match. A blank value or an asterisk (*) will match any procedure step name. Generic matching characters asterisk (*) and question mark (?) match zero or more characters and one character, respectively.

Program

Program name to match. A blank value or an asterisk (*) will match any program name. Generic matching characters asterisk (*) and question mark (?) match zero or more characters and one character, respectively.

Condition Codes

Conditions codes are integer return codes from the program or ABEND codes. Integer return codes are specified as a comma-separated list of integer values or ranges. Ranges are specified with a dash (-) separating the lower and upper bounds of the range. The z/OS job step return code range is 0-4095. ABEND codes are specified directly as either a user ABEND or a system ABEND. The ABEND code must be specified verbatim including leading zeroes.
 
For example: 1,6-4095,Sxxx,Unnnn,JCLERR

Action

Action to take and the task status to set if the Step Condition matches. See Step Condition Logic, below, for an explanation of the actions.

Metadata

This section contains Metadata information about this record.

UUID

Universally Unique Identifier of this record.

Updated By

Name of the user that last updated this record.

Updated

Date and time that this record was last updated.

Created By

Name of the user that created this record.

Created

Date and time that this record was created.

Buttons

This section identifies the buttons displayed above and below the Step Condition Details that let you perform various actions.

Save

Saves a new record in the Controller database.

Save & New

Saves a new record in the Controller database and redisplays empty Details so that you can create another new record.

Save & View

Saves a new record in the Controller database and continues to display that record.

New

Displays empty (except for default values) Details for creating a new record.

Update button

Saves updates to the record.

Refresh

Refreshes any dynamic data displayed in the Details.

Delete button

Deletes the current record.

Close

For pop-up view only; closes the pop-up view of this task.