Cisco Cisco Workload Automation 6.3 User Guide

Installing the z/OS Agent

Getting Started with the z/OS Agent

Information on the files being installed is displayed. Once the files are installed, the 

 is 

displayed with options for adding, editing and deleting agent instances.

You must add at least one agent instance and configure it.

After selecting the option to add an agent instance (1), you must enter a name for the agent, a port number and the 
directory path to the Java binaries directory.

It is recommended to use the default port number, 

5912, if possible. If you have used the default locations when 

installing, you can just press the 

 

button.

Once you confirm the selections, you are returned to the 

. Quit the 

by typing 

Q and pressing 

. 

Getting Started with the z/OS Agent

Requirements for Starting the Agent 

There are two ways to start the CWA Agent for z/OS, from OMVS or from a Started Task script. Each has its own 
prerequisite that must be configured to be successful.

OMVS

The TSO user starting the CWA Agent for z/OS from OMVS must be configured for a minimum of 

1024000 of virtual 

storage. The user can configure the 

SIZE parameter by logging onto TSO and specifying the parameter on the TSO 

logon screen. For example,

 tso tidal size(1024000).

If starting the agent from OMVS, ensure that the user account has an OMVS segment defined in their profile or that 

user cannot start the agent via OMVS.

Started Task Script

If starting the CWA Agent for z/OS from a Started Task script, the started procedure must have the parameter 
REGION=ØK specified on the EXEC statement. This parameter enables the Java Virtual Machine to start with the 
necessary virtual storage. Refer to the 

 chapter.

With either method, OMVS or Started Task script, the user starting the CWA agent must have Operator Level Authority 
because the agent inherits the user’s level of authority during startup and running of the agent. 

Authority Requirements 

To run a job in z/OS, the CWA agent for z/OS must be started by a user with Operator Level Authority since the agent 
inherits the user’s level of authority during the startup and running of the agent. If any of the user rights listed below are 
missing, then the CWA agent cannot successfully launch, track and manage the completion of a job.

The Operator Level Authority must include the rights to run the following commands:



JES Commands

$DJ (JES Display Job command)

$CJ (JES Cancel Job command)

$TOJ,Q (Change MSGCLASS)

$OJ (Release Held output)