...
The following special processing features are available for running z/OS tasks:
- Special Processing on z/OS Tasks#Using Using Variables in JCL and In-Stream Data Sets
- Special Processing on z/OS Tasks#Skipping Skipping Steps during Initial Run
- Special Processing on z/OS Tasks#Overriding Overriding Key JCL Parameters from Universal Controller
- Special Processing on z/OS Tasks#Disabling Disabling Automatic Data Set Deletion
The following failure processing features are available for handling job failures:
- Special Processing on z/OS Tasks#ReRe-running a z/OS Task Instance
- Special Processing on z/OS Tasks#Interactively Interactively Ignoring a Step Code to Force a Task to Complete
The Controller supports compatibility with other schedulers:
- Special Processing on z/OS Tasks#CA7/CA7/CA11 Toleration
The Controller provides the following reports that track error processing:
- Special Processing on z/OS Tasks#Viewing Viewing Re-run Reports
- Special Processing on z/OS Tasks#Viewing Viewing Audit Trails on a Restart
Each of these features is described in detail below.
...
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 | ||||
---|---|---|---|---|
|
...
If you make any JCL changes, the Controller will prompt you for a confirmation, as described in Special Processing on z/OS Tasks#Re Re-run a z/OS Task Instance from a Specific Step, below.
During the confirmation process, UAG checks for the following JCL changes:
...
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: <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.)If you want to de-select a job step in the group for inclusion
| |||||
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. (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.
|
...
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. |
...
- 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.
...
...
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).
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.
...
, as shown in the following example.
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 | ||||
---|---|---|---|---|
|
...
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 | ||||
---|---|---|---|---|
|
The Controller maintains detailed audit records on all system activity. The following audit record is for a re-run launch on a z/OS task.