Cisco Cisco Workload Automation 6.3 User Guide

Working with the z/OS Agent

Return Codes and Job Output

In the above job definition example, the parameters will not be substituted, but will remain a part of the job definition. 

When a job completes abnormally and needs to be re-started (after correcting the condition that caused the abnormal 
completion), the customer simply needs to go to the override tab of the job and fill in the appropriate restart step after 
the "RESTART=" and use CWA controls to rerun the job. The parameter substitution logic will now honor the substitution 
and modify the JCL to contain the "RESTART=(STEP)" at the specified location.

Original JCL

//RESTART  JOB (20,FB3),IBMUSER,MSGLEVEL=(1,1),  THIS IS A RESTART TEST         

//            CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID,REGION=1M   

Modified JCL

//RESTART  JOB (20,FB3),IBMUSER,MSGLEVEL=(1,1), THIS IS A RESTART TEST 

// RESTART=(STEP03),CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID,REGION=1M

Notice comment re-inserted in original location.  Every effort is made to re-insert comments on the same line they 

were on or at the first opportunity thereafter.  Any left-over comments are added after the JCL command line as line 
comments.

Return Codes and Job Output

For the CWA agent to determine the highest return code of a job and to provide the master with output to view from a 
CWA Web client, all CWA jobs you submit must specify a 

 message class in the job card.

Piping Job Output

When you use the 

Pipe option in the output disposition and/or tracking method of a job rule, only POSIX (USS) 

commands, scripts or programs are allowed.