...
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 | ||||
---|---|---|---|---|
|
Skipping Steps during Initial Run
In a z/OS task, you can specify that one or more steps from the JCL should be skipped when the Controller launches the job. You achieve this by adding SKIPSTNN variables (or parameters) to your z/OS task record.
...
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 | Repeat Steps 2 and 3 for each step you want to skip. Change the AA portion of the SKIPST for each parameter you add. Each Name must be unique.
|
Anchor | ||||
---|---|---|---|---|
|
Overriding Key JCL Parameters from Universal Controller
When you launch a z/OS task from the Controller, you can specify a different Jobname, Jobclass, Msgclass, Schedule ID or add a JOBPARM card. This enables you to run your JCL jobs from the Controller without having to go in and modify your JCL. You can do so by entering new value into the appropriate field in the z/OS Task Details.
Anchor | ||||
---|---|---|---|---|
|
Disabling Automatic Data Set Deletion
Universal Automation Center Agent (UAG) will automatically detect and delete data sets that would cause a NOT CATLGD 2 condition. The data set deletion takes place before the job is started. Automatic data set deletion can be disabled for a z/OS task by defining the OPSDSDEL parameter with a value of NO in the z/OS task definition.
...
- A value of YES specifies that automatic data set deletion is enabled for the z/OS task.
- A value of NO specifies that automatic data set deletion is disabled for the z/OS task.
The Re-run Report will indicate if the feature has been disabled.
Anchor | ||||
---|---|---|---|---|
|
Re-running a z/OS Task Instance
When you re-run a z/OS task, you must select job steps in the task to include in the re-run; you cannot simply click a Re-run button or Re-run in an Action menu, as with other tasks.
...
If you make any JCL changes, the Controller will prompt you for a confirmation, as described in 19365893 Re-run a z/OS Task Instance from a Specific Step, below.
During the confirmation process, UAG checks for the following JCL changes:
...
Note | ||
---|---|---|
| ||
UAG does not check for changes to steps which will not run. |
Anchor | ||||
---|---|---|---|---|
|
Re-running a z/OS Task Instance in Start Failure Status
If a z/OS task instance is in Start Failure status, the existence or non-existence of Restartable Job Steps will determine the outcome of a Re-run command.
- If Restartable Job Steps exist, you can re-run the task instance from any steps identified as Restartable under the Restartable Job Steps tab.
- If Restartable Job Steps do not exist, you must re-submit the task instance from the beginning, as when re-running a z/OS task instance from the In Doubt status.
Anchor | ||||
---|---|---|---|---|
|
Re-run a z/OS Task Instance from a Specific Step
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 | From the Restartable Job Steps list, select the steps that you want included in the re-run:
(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 | ||||
---|---|---|---|---|
|
Restartable Job Steps List Column Descriptions
The following table describes each column on the z/OS Restartable Job Steps 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 | ||||
---|---|---|---|---|
|
Interactively Ignoring a Step Code to Complete a Task
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 . |
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 | ||||
---|---|---|---|---|
|
CA7/CA11 Toleration
Anchor | ||||
---|---|---|---|---|
|
Non-Restartable Customized Job Steps
The Controller can read and interpret JCL DD 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.
...
- CA11NR - CA11 Non-Restartable
- UCC11NR - UCC11 Non-Restartable
- OPSNR000 - Opswise Non-Restartable
SCHID - Overriding the CA7 Schedule ID
Anchor | ||||
---|---|---|---|---|
|
The Schedule ID field in the z/OS Task Details allows you to override the CA7 SCHID (Schedule ID).
...
Panel |
---|
//SCHID JOB (IMS,001),JIM,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID, #JI,ID=1-39 // CLASS=A #JEND #JI,ID=40-79 // CLASS=B #JEND //S1 EXEC PGM=IGWSPZAP //SYSLIB DD DSN=OPS01.JS01.LOAD,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSIN DD * DUMPT WMSSETRC WMSSETRC /* // |
Anchor | ||||
---|---|---|---|---|
|
Non-Restartable Job Steps
A z/OS Agent determines that a job step is non-restartable if the step contains any of the following:
- One of the special DDNAMEs: CA11NR, UCC11NR, or OPSNR000.
- DD statement with DISP=(NEW,PASS) or (OLD,DELETE). (Note that the third DISP value is not considered by the agent.)
- A backwards volume reference. For example: VOL=REF=...
Anchor | ||||
---|---|---|---|---|
|
Viewing Re-run Reports
The Controller keeps a detailed record of task re-runs. This data is written to the Output tab on the task instance record, as shown in the sample below:
Anchor | ||||
---|---|---|---|---|
|
Viewing Audit Trails on a Restart
The Controller maintains detailed audit records on all system activity. The following audit record is for a launch on a z/OS task.
...