Use the agent for z/OS to schedule work from HCL Workload Automation on the JES2 or JES3 subsystem of z/OS.

You install and configure the agent for z/OS in the z/OS system. As soon as it is configured, the agent automatically links with the dynamic workload broker component of HCL Workload Automation (defined during the configuration process) through the HTTP/HTTPS protocols or through the gateway. For more information about the installation of the gateway see

Configuring a dynamic agent

With the agent for z/OS you can define jobs and schedules on HCL Workload Automation and submit a subset of the jobs to a z/OS system. You run the planning tasks on HCL Workload Automation while the execution is demanded to the z/OS system.

The agent for z/OS acts as a proxy between dynamic workload broker, which is the HCL Workload Automation component that actually submits workload, and JES, which is the component in the z/OS® system that executes the workload. The agent passes the workload from HCL Workload Automation to JES, and returns all updates about its execution back to HCL Workload Automation in the form of events.

The agent for z/OS represents a lightweight end-to-end scheduling solution that enables users to define and manage workload that is to be processed by JES entirely from HCL Workload Automation.

The agent exploits the HTTP submission protocol to receive job submission requests and to asynchronously send back job status notifications.

The jobs submitted to an agent for z/OS are similar to other HCL Workload Automation dynamic jobs. The job definition uses the XML syntax of the Job Submission Description Language (JSDL), where the application name is JCL and includes one of the following:
  • The entire JCL definition of the task to be run by JES. In this case, the JCL is part of the job definition stored in the HCL Workload Automation database and is sent to the agent with the rest of the job at submission time. This is called submission by definition.
  • The names of the data set and of the file containing the JCL definition in the z/OS system where the agent runs. When the job is submitted, the agent uses this information to track the JCL definition in the z/OS system. This is called submission by reference.
You can use the following interfaces to define these jobs:
  • The composer or the dynamic workload broker command lines
  • Workload Designer of the Dynamic Workload Console
  • The dynamic workload broker graphical user interface

The agent supports the scheduling of jobs, but not of started tasks, on the z/OS® system.

JCL tailoring (variable substitution in z/OS® terms) is carried out before submitting the JCL to JES using the variable values specified in the variables tables in HCL Workload Automation.

You manage agent for z/OS jobs as you manage other HCL Workload Automation jobs. Use the Dynamic Workload Console to see them in graphical or tabular views, or in host-lists. You can also see the related job logs and carry out most actions (such as rerun, cancel, but not kill) typically available for other jobs.

From the Dynamic Workload Console or the HCL Workload Automation command line you can view the job log for as long as the job output is kept in the JES spool.

Compatibility issues between the agent for z/OS and the HCL Workload Automation for Z trackers

The agent for z/OS and the HCL Workload Automation for Z trackers can coexist as long as you run the standard HCL Workload Automation for Z tracker exits. If you are concerned about such coexistence, you must not therefore install any of the sample exits provided with the agent.