...
| Anchor | ||||
|---|---|---|---|---|
|
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. | ||||||
| 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. |
...
Field Name | Description | ||||||
|---|---|---|---|---|---|---|---|
| Job step name to match. A blank value or an asterisk ( | ||||||
| Procedure step name to match. A blank value or an asterisk ( | ||||||
| Program name to match. A blank value or an asterisk ( | ||||||
| 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 ( | ||||||
| Action to take and the task status to set if the Step Condition matches. See Creating Step Conditions#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 |
| ||||||
Refresh | Refreshes any dynamic data displayed in the Details. | ||||||
Delete button |
| ||||||
Close | For pop-up view only; closes the pop-up view of this task. |
...
| Note | ||
|---|---|---|
| ||
The Controller searches Step Condition definitions based on their order in the Creating Step Conditions#Step Conditions list; the definition at the top of the list is searched first. To change the order of the definitions in the list, drag and drop them to any location. |
...
Continue/Success | Job execution continues and task status is set to SUCCESS. |
|---|---|
Continue/Failed | Job execution continues and task status is set to FAILED. |
Halt/Failed | Job execution is halted at the current step and task status is set to FAILED. |
Askoper | Job execution is stopped and the Controller sends a WTOR message to the console operator requesting a reply on how job execution should proceed. The action is dependent upon the operator reply (see Creating Step Conditions#Example Example 4, below). |
During job processing, the Controller issues message UAG1059A to the job log when it matches a Step Condition definition to a step that has completed execution. Message UAG1059A includes the Step Condition definition values including the action that is taken. The message provides an audit record of Step Condition processing that has influenced job execution.
...
- (1) CONTINUE/SUCCESS
- (2) CONTINUE/FAILED
- (3) HALT/FAILED
(See Creating Step Conditions#Step Condition Logic for an explanation of these replies.)
...