Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following special processing features are available for running z/OS tasks:

The following failure processing features are available for handling job failures:

The Controller supports compatibility with other schedulers:

The Controller provides the following reports that track error processing:

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:

  • Name is the name of a variable preceded with @. For example: *@DATE1.
  • Value is the value you want to set to the variable. For example: 20110601.

Step 4

When the JCL is submitted for execution, the parameter *@DATE1 (shown in the following example) will be substituted with the value 20110601 in the JCL or
in any in-stream data. The example also shows the *@DATE1 parameter being used in an in-stream data and in a JCL IF statement:
 

Panel
Panel
 
If a Universal Controller parameter must be concatenated with a non-space character, end the parameter name with a period (.). The example below
uses the *@DATE1 parameter


Html bobswift
<pre>
//INPUT DD *
@DATE1
/*
</pre>



Panel


Html bobswift
<pre>
//AIF   IF @DATE1 > 20110101 THEN
</pre>


 
If a Universal Controller parameter must be concatenated with a non-space character in an in-stream data set:
 

panel

, end the parameter name with a period (.). The example below
uses the *@DATE1 parameter concatenated with a non-space character in an in-stream data set:
 

Panel


Html bobswift
<pre>
//INPUT DD *
DATE@DATE1.ACT9898
/*
</pre>



Anchor
Skipping Steps during Initial Run
Skipping Steps during Initial Run
Skipping Steps during Initial Run

...

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.
 

 
Check the Restartable column to see from which steps you can start the re-run (Yes or No).
 
If applicable, the Failed column indicates at which step(s) the task failed.

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:

  1. Click the first step that you want included in the re-run.
  2. Press and hold the <Shift> key.
  3. Click the last step that you want included in the re-run.
  4. Right-click any step in the selected group to display an Action menu.
  5. Click Select for 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.)
 
If you want to de-select a job step in the group for inclusion in the re-run, right-click the step and, in the Action menu, click Deselect for 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.
 
To confirm the changes:

  1. From the Activity Monitor, open the task instance.
  2. Click the Confirm JCL Changes tab to display a list of all changes that were made to the JCL:
     

     
  3. Click the Confirm button at the top of the list.
  4. Click the z/OS Task Instance tab. Verify that the JCL Changes Confirmed field is checked and then click the Re-run button.
Note
titleNote

If a z/OS task instance transitions into the Confirmation Required status, and the Controller determines that the number of steps did not change, it preserves the step re-run selection.

However, if the Controller detects a change in the number of steps, all steps will be de-selected.


Step 9

After the re-run is complete, the Failed column in the Restartable Job Steps list should show No for each step.
 

Note
titleNote

If you repeat the above process on the same task instance, the previous list of JCL changes, if any, is replaced with the most recent list of changes.


...

Note
titleNote

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.

...

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


Html bobswift
<pre>
//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
/*
//
</pre>


Anchor
Non-Restartable Job Steps
Non-Restartable Job Steps
Non-Restartable Job Steps

...