HCL Workload Automation, Version 9.4

Using

  • 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 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 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.
  • Switching domain managers
    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.