Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user IT Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

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
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, 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

...

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

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>

Action menu

(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.
 
Image Removed

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:
     
    Image Removed
     
  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.

...

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.


Html bobswift
<ol>
<li> Click the first step that you want included in the re-run.
<li> Press and hold the

<Shift>

Html bobswift
 key.
<li> Click the last step that you want included in the re-run.
<li> Right-click any step in the selected group to display an

Action menu

Html bobswift
.
<li> Click <b>Select for Re-run</b>.
</ol>


(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.
 
Image Added


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:
     
    Image Added
     
  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.

Anchor
Restartable Job Steps List Column Descriptions
Restartable Job Steps List Column Descriptions
Restartable Job Steps List Column Descriptions

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.

Anchor
Restartable
Restartable
Restartable

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.

Anchor
Selected for Re-run
Selected for Re-run
Selected for Re-run

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).

Anchor
Depends On
Depends On
Depends On

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:
 
Image Removed

...

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
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.

...

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
Interactively Ignoring a Step Code to Force a Task to Complete
Interactively Ignoring a Step Code to Force a Task to Complete
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:
 
Image Added

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
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.

Anchor
CA7/CA11 Toleration
CA7/CA11 Toleration
CA7/CA11 Toleration

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

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
SCHID
SCHID
SCHID - Overriding the CA7 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.

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

...