Cisco Cisco Workload Automation 6.3 User Guide

Working with the z/OS Agent

Shell Scripts vs z/OS JCL vs System Commands

File Dependencies

Use the 

// prefix when specifying a data set in a file dependency. 

For HFS files, use the same syntax as UNIX. 

The type of file dependency on 

Z

/OS data sets is limited to only two options, 

 and 

. If you choose 

any other file dependency option, dealing with changes in size or over a period of time, the dependency will never be 
satisfied.

Shell Scripts vs z/OS JCL vs System Commands

If CWA encounters 

 as the first two characters in a job file, it will submit it as a CWA job to JES2. If the first character 

of the command is $, the remaining string plus any parameters are submitted as an extended console command. All other 
files are considered to be shell scripts or programs and are run in USS.

The first line of all USS shell scripts must be 

.

For example,

#!/bin/sh 

/fin/bin/f101p 

Security for z/OS Jobs

To schedule jobs on the z/OS agent, you must authorize users in CWA to access the z/OS agent. This is a two-step 
process. First, create z/OS runtime user profiles to run jobs from CWA. Then, assign these to the appropriate CWA users 
by modifying their authorized runtime user list. Now, the CWA users can submit z/OS jobs on behalf of the authorized 
z/OS users. 

For more information on creating runtime users, refer to the User Configuration Procedures section in Chapter 3: Users 
in the Cisco Workload Automation User Guide.

The 

Z

/OS user must have an OMVS segment. The following is an example of using the RACF 

ADDUSER command to 

define a 

Z

/OS USS user:

#ADDUSER MARYK OMVS(UID(324) HOME('/u/maryk') \

PROGRAM('/bin/sh') 

You should not schedule jobs to run as a z/OS user which has an OMVS UID assignment of 0. This causes the job 

to run as the user you defined as SUPERUSER in the BPXPRMXX member of PARMLIB, usually, BPXROOT. Therefore, the 
job will not run as the correct z/OS user.