Home
HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.1 Fix Pack 5.
Scheduling with the Agent for z/OS
Using the agent for z/OS
Defining jobs
Like you do for all other HCL Workload Automation jobs, you can define jobs for an agent for z/OS from either the composer command line or from the Dynamic Workload Console.

HCL Workload Automation
Welcome to the HCL Workload Automation documentation, where you can find information about how to install, maintain, and use HCL Workload Automation. The documentation has been updated for HCL Workload Automation Version 10.1 Fix Pack 5.
- Fix pack readmes
- Planning and Installation
- User's Guide and Reference
- Administration Guide
- Scheduling with the Agent for z/OS
  - Overview
    Use the agent for z/OS to schedule work from HCL Workload Automation on the JES2 or JES3 subsystem of z/OS.
  - Installing and configuring
    This chapter describes the tasks you need to complete to download, install, and configure the agent for z/OS software on the target z/OS system.
  - Using the agent for z/OS
    - Computer and workstation names of the agent
      The first time the agent for z/OS connects with HCL Workload Automation, it is automatically given a computer name.
    - Listing the agents for z/OS
      In the Dynamic Workload Console and in composer, the agents for z/OS® are listed as workstations of type agent.
    - Defining jobs
      Like you do for all other HCL Workload Automation jobs, you can define jobs for an agent for z/OS from either the composer command line or from the Dynamic Workload Console.
      - Defining and editing jobs in the Dynamic Workload Console
        The easiest way to define an agent for z/OS job is with the Dynamic Workload Console.
      - Defining jobs in composer
        You can also use the composer command line to define jobs for the agent for z/OS.
    - Defining the JCL
      How to define the JCL.
    - Running event-driven workload automation
    - Submitting jobs
      All agent for z/OS jobs can be either part of a job stream and be submitted in a plan, or be submitted at any time using the conman submit commands or proper Dynamic Workload Console panels.
    - Using variables in your agent for z/OS jobs
      You can include variables in your job definition.
    - Managing job instances
      You manage jobs submitted to an agent for z/OS with the same commands available for all HCL Workload Automation jobs.
    - Tracking jobs
      The agent uses the JES/SMF exits to track the status changes for all the jobs submitted through it.
    - Viewing job logs
      Viewing the logs of jobs submitted through the agent for z/OS.
    - Using system commands to control the agent
      You can use z/OS® system commands to start, stop, cancel, or modify the agent for z/OS.
    - How the agent responds to a domain manager switch
      This section describes the mechanism that keeps the agent for z/OS connected to your HCL Workload Automation network when you switch to a backup manager.
  - Troubleshooting and reference
    This chapter documents potential problems and reference information.
- Database Views
- High Availability Cluster Environment
- Driving HCL Workload Automation
- Extending HCL Workload Automation

Defining jobs

Like you do for all other HCL Workload Automation jobs, you can define jobs for an agent for z/OS from either the composer command line or from the Dynamic Workload Console.

Because all agent for z/OS jobs are submitted through dynamic workload broker, the task section of their job definitions is laid out in the JSDL XML language. If you define the job through the Dynamic Workload Console, the information you provide in the input panels is made into JSDL automatically.

The following characteristics qualify a job as an agent for z/OS job:

The executing workstation is a agent for z/OS.
In the JSDL definition in composer, the application keyword has name jcl. In the Dynamic Workload Console, the job definition type is z/OS.
The job definition in JSDL either includes the JCL that is to be run by JESn or points to its location (data set and member names) in the z/OS system. In the first case, the JCL is said to be submitted by definition, otherwise it is said to be submitted by reference.

While the JCLs specified by definition are part of the agent for z/OS jobs and as such are stored in the HCL Workload Automation database, the JCLs specified by reference are stored in data sets in the z/OS system hosting the agent and are retrieved at submission time using the coordinates provided in the corresponding jobs.