...
Step 1 | Open the z/OS task. | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Step 2 | In the Parameters field, click the + icon. | |||||||||
Step 3 | Add a parameter in the following format:
| |||||||||
Step 4 | When the JCL is submitted for execution, the parameter
|
...
|
Anchor | ||||
---|---|---|---|---|
|
...
Step 1 | On the Activity Monitor, click the Details icon next to the Instance Name of the task you want to re-run. The z/OS Task Instance Details displays. |
---|---|
Step 2 | Click the Restartable Job Steps tab to display a list of all job steps in the task. |
Step 3 | Assuming any failures were caused by error(s) in the JCL, examine the JCL and make your corrections. The Controller uses a background process to determine whether changes have been made to the JCL. Any changes trigger a confirmation process. |
Step 4 | Click the Details icon next to the Step Number of any step to see detail information about that step. |
Step 5 |
Confirm JCL Changes Tab Column Descriptions
The following table describes each column on the Confirm JCL Changes list.
Column Name | Description | |||||
---|---|---|---|---|---|---|
Job Id | Number assigned to this step by the Controller. | |||||
Step Number | JCL step number that was modified. | |||||
Error Message | Description of the change. | |||||
Old Data | JCL before the change. | |||||
New Data | JCL after the change. | |||||
Confirmed | Indicates (Yes or No) whether or not this JCL change was confirmed From the Restartable Job Steps list, select the steps that you want included in the re-run: <Shift> (You also can right-click a step and select Select to End for Re-run to include that selected step and all following steps in the re-run.) | |||||
Step 6 | Click the z/OS Task Instance tab to redisplay the z/OS Task Instance Details. | |||||
Step 7 | Click the Re-run button to re-run the task for the selected job steps. | |||||
Step 8 | If you have made changes to the JCL, the task instance goes into a status of Confirmation Required on the Activity Monitor.
| |||||
Step 9 | After the re-run is complete, the Failed column in the Restartable Job Steps list should show No for each step.
|
...
The following table describes each column on the z/OS Restartable Job Steps list.
...
Column Name
...
Description
...
Step Number
...
Number assigned to this step by the Controller.
...
If the JCL job fails, the Controller determines the latest step that you can restart from. Yes indicates that you can restart from this step.
...
Indicates (Yes or No) whether or not this step has been selected for re-run (the Selected for Re-run field is enabled in the Restartable Job Steps Details).
...
Specifies which other step(s), if any, must be completed successfully before you can run this step.
...
Step
...
Name of the JCL step (extracted from the JCL).
...
Procedure
...
Procedure step name from within the JCL step.
...
Program
...
Name of the program being executed by the step.
...
Step Code
...
Extracted from the JCL. Exit code for this step of the program.
...
Failed
...
Indicates (Yes or No) whether or not this step failed.
...
Updated By
...
Name of the user that last updated this step.
...
Updated
...
Date and time that this step was last updated.
<Shift>
(You also can right-click a step and select Select to End for Re-run to include that selected step and all following steps in the re-run.) | ||||||
Step 6 | Click the z/OS Task Instance tab to redisplay the z/OS Task Instance Details. | |||||
---|---|---|---|---|---|---|
Step 7 | Click the Re-run button to re-run the task for the selected job steps. | |||||
Step 8 | If you have made changes to the JCL, the task instance goes into a status of Confirmation Required on the Activity Monitor.
| |||||
Step 9 | After the re-run is complete, the Failed column in the Restartable Job Steps list should show No for each step.
|
Anchor | ||||
---|---|---|---|---|
|
The following table describes each column on the z/OS Restartable Job Steps list.
Column Name | Description | ||||||
---|---|---|---|---|---|---|---|
Step Number | Number assigned to this step by the Controller. | ||||||
| If the JCL job fails, the Controller determines the latest step that you can restart from. Yes indicates that you can restart from this step. | ||||||
| Indicates (Yes or No) whether or not this step has been selected for re-run (the Selected for Re-run field is enabled in the Restartable Job Steps Details). | ||||||
| Specifies which other step(s), if any, must be completed successfully before you can run this step. | ||||||
Step | Name of the JCL step (extracted from the JCL). | ||||||
Procedure | Procedure step name from within the JCL step. | ||||||
Program | Name of the program being executed by the step. | ||||||
Step Code | Extracted from the JCL. Exit code for this step of the program. | ||||||
Failed | Indicates (Yes or No) whether or not this step failed. | ||||||
Updated By | Name of the user that last updated the JCLthis step. | ||||||
Updated | Date and time that the JCL this step was last updated. |
...
If the step code (exit code) on a previous step is causing a step failure, but you still want to finish the job, you can change the step code in order to complete the task.
...
Step 1
...
From the Activity Monitor, open the task instance.
...
Step 2
...
From the Restartable Steps tab, click on the step whose code you want to change. The Restartable Job Step Details for this job step displays:
...
Step 3
...
Enter the new code in the Step Code field and click Update.
...
Step 4
...
Click the z/OS Task Instance tab and then click the Re-run button.
Note | ||
---|---|---|
| ||
By default, on a re-run, the return code in the restarted step will revert to the original return code. To retain the new step code, change the Retain Overridden Step Codes On z/OS Task Re-run Universal Controller system property to true. |
...
The Controller can read and interpret JCL step names that have been customized for CA11 and UCC. This allows you to launch your existing CA11 and UCC jobs from the Controller without modifying the JCL.
When the Controller encounters one of the following step names in your JCL, the Controller will skip the step during a restart:
- CA11NR - CA11 Non-Restartable
- UCC11NR - UCC11 Non-Restartable
- OPSNR000 - Opswise Non-Restartable
...
Confirm JCL Changes Tab Column Descriptions
The following table describes each column on the Confirm JCL Changes list.
Column Name | Description |
---|---|
Job Id | Number assigned to this step by the Controller. |
Step Number | JCL step number that was modified. |
Error Message | Description of the change. |
Old Data | JCL before the change. |
New Data | JCL after the change. |
Confirmed | Indicates (Yes or No) whether or not this JCL change was confirmed. |
Updated By | Name of the user that last updated the JCL. |
Updated | Date and time that the JCL was last updated. |
Anchor | ||||
---|---|---|---|---|
|
If the step code (exit code) on a previous step is causing a step failure, but you still want to finish the job, you can change the step code in order to complete the task.
Step 1 | From the Activity Monitor, open the task instance. |
---|---|
Step 2 | From the Restartable Steps tab, click on the step whose code you want to change. The Restartable Job Step Details for this job step displays: |
Step 3 | Enter the new code in the Step Code field and click Update. |
Step 4 | Click the z/OS Task Instance tab and then click the Re-run button. |
Note | ||
---|---|---|
| ||
By default, on a re-run, the return code in the restarted step will revert to the original return code. To retain the new step code, change the Retain Overridden Step Codes On z/OS Task Re-run Universal Controller system property to true. |
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
The Controller can read and interpret JCL step names that have been customized for CA11 and UCC. This allows you to launch your existing CA11 and UCC jobs from the Controller without modifying the JCL.
When the Controller encounters one of the following step names in your JCL, the Controller will skip the step during a restart:
- CA11NR - CA11 Non-Restartable
- UCC11NR - UCC11 Non-Restartable
- OPSNR000 - Opswise Non-Restartable
In the following example, step 3 has one of the above DD Names and therefore is a non-restartable step.
Anchor | ||||
---|---|---|---|---|
|
...
For example, the JCL shown below contains CA7 Scheduled Overrides statements #JI and #JEND. This JCL will set CLASS =A if the SCHID is between 1 thru 39, and set CLASS=B if the SCHID is between 40 thru 79. The user can set the SCHID by entering it into the Schedule ID field. The Agent scans for #JI and #JEND, and generates the appropriate JCL, as shown in the following example.
Panel | ||
---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
...