...
Use the z/OS Task Details Parameters field to specify JCL symbolic parameters to be used in the JCL.
...
Use the z/OS Task Details Parameters field to specify parameters that can be used in any JCL statement and in in-stream data sets.
...
The following steps add a Universal Controller parameter with the name *@DATE1 and a value of 20110601:
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
|
...
To configure your z/OS task to skip specific JCL steps:
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.
|
...
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 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.
To configure your z/OS task with automatic data set deletion disabled:
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:
|
...
- 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.
...
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.
The Restartable Job Steps tab in the z/OS Task Instance Details provides a list of all job steps in the task and indicates from which steps you can start the re-run.
...
You also can re-run a z/OS task in the In Doubt status (see Re-run a z/OS Task Instance in the In Doubt Status).
Confirming JCL Changes
If you make any JCL changes, the Controller will prompt you for a confirmation, as described in Re-run a z/OS Task Instance from a Specific Step 206395906, below.
During the confirmation process, UAG checks for the following JCL changes:
...
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.
|
...
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. |
...
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.
...