Home
HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
Scheduling End-to-end with z-centric Capabilities
Defining and managing dynamic workstations
When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
Submitting jobs by reference

HCL Workload Automation for Z
Welcome to the HCL Workload Automation for Z documentation, where you can find information about how to install, maintain, and use the product.
- Program Directory
- Dynamic Workload Console Readmes
  For the latest information about a Dynamic Workload Console fix pack, see the appropriate Readme File.
- Planning and Installation
- Customization and Tuning
- Managing the Workload
  You can plan when and how your workload runs and manage it as part of a plan.
- Scheduling End-to-end with z-centric Capabilities
  - About this publication
  - Configuring
  - Customizing the HTTP connections
    The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
  - Defining user IDs and passwords with the USRREC statement
    Use the USRREC initialization statement to define the passwords for the users who need to schedule jobs to run on Windows™ workstations. You do not need to do this if you run native job types on non-Windows workstations.
  - Defining variables and passwords for local resolution
  - Defining and managing HCL Workload Automation Agent workstations in the database
    After defining the destinations of your HCL Workload Automation Agents, you need to define the HCL Workload Automation Agents as HCL Workload Automation for Z computer automatic workstations.
  - Defining and managing dynamic workstations
    When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
    - Creating broker workstations
      Create broker workstations using the ISPF panels and the Dynamic Workload Console.
    - Defining a backup dynamic domain manager
      How you can define a backup dynamic domain manager.
    - Creating pools and dynamic pools
      You can create pools and dynamic pools using the Dynamic Workload Console.
    - Submitting jobs to pools or dynamic pools
    - Submitting jobs by reference
  - Setting the security features
  - Defining and managing jobs
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Monitoring and recovering jobs
  - Running a script when a job completes
  - Viewing the job logs from the host
    An overview on how to view or retrieve the job logs issued in the z-centric environment and how to attach a header with job run information on top of each log.
  - Troubleshooting
    Troubleshooting agent problems
  - Configuring to schedule J2EE jobs
  - Security order of precedence used for the execution of J2EE tasks
  - Configure to schedule job types with advanced options
  - Managing return codes
  - Collecting job metrics
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Submitting jobs by reference

About this task

When you submit a job by reference, you create a job definition in the distributed environment and submit it from HCL Workload Automation for Z to the distributed environment. In the distributed environment, the job is dynamically assigned to the best available resource. You write in the HCL Workload Automation for Z JCL only the job name of the job, without having to write or import the whole job into the JCL. You can submit jobs by reference only on broker workstations.

To submit jobs by reference from HCL Workload Automation for Z, perform the following steps:

Define a job with name broker_test by using the Dynamic Workload Console. This job contains the operations to be performed:
Create a JCL, by using the ISPF panels or the Dynamic Workload Console, specifying the name of the job you created in step 1. This references the job in the distributed environment.
Submit the JCL. As a result, the broker_test job is submitted in the distributed environment.