Overview

The different types of workload scheduling you can implement in your z-centric end-to-end environment:
Static scheduling
The HCL Workload Automation Agents are installed on the distributed systems and are connected to the z/OS® system through the HCL Workload Automation for Z controller.
Static scheduling including job types with advanced options
Figure 1. Static end-to-end environment with Java run time installed in which you can run job types with advanced options

Graphic showing HCL Workload Automation Agents connected to the HCL Workload Automation for Z controller for static scheduling.
The HCL Workload Automation Agents are installed on the distributed systems with the Java run time, and are connected to the z/OS® system through the HCL Workload Automation for Z controller. Static end-to-end environment with Java run time installed in which you can run job types with advanced options shows a static end-to-end environment in which HCL Workload Automation Agents:
  • Without the Java run time installed, can run existing job types
  • With the Java run time installed, can run both existing jobs and job types with advanced options
Dynamic scheduling
The HCL Workload Automation Agents are installed on the distributed systems with dynamic capabilities, and are connected to the dynamic domain manager. The dynamic domain manager is connected to the z/OS® system through the HCL Workload Automation for Z controller.
Dynamic scheduling including job types with advanced options
Figure 2. Dynamic end-to-end environment to run also job types with advanced options.

Graphic showing HCL Workload Automation Agents connected to the dynamic domain manager for dynamic scheduling.
The HCL Workload Automation Agents are installed on the distributed systems with dynamic capabilities and the Java run time, and are connected to the dynamic domain manager. The dynamic domain manager is connected to the z/OS® system through the HCL Workload Automation for Z controller. Dynamic end-to-end environment to run also job types with advanced options. shows a dynamic end-to-end environment in which HCL Workload Automation Agents:
  • Without the Java run time installed, can run existing job types
  • With the Java run time installed, can run both existing jobs and job types with advanced options

By using the z-centric end-to-end scheduling environment, you schedule and control both static and dynamic workload from the mainframe to distributed systems with a low cost of ownership. HCL Workload Automation for Z acts as a single point of control, providing you with all the mainframe capabilities to manage distributed workload.

HCL Workload Automation Agents can be installed on the UNIX, IBM® i, or Windows workstations where you run jobs scheduled from HCL Workload Automation for Z. After installation, you associate each agent to an HCL Workload Automation for Z workstation definition, so that it can be used as a target for HCL Workload Automation for Z jobs. The communication between the HCL Workload Automation Agent and HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol. If the connection is interrupted, the HTTP client retries to establish it until it is successful.

Process flow shows the process flow to submit and track jobs on HCL Workload Automation Agent workstations.
Figure 3. Process flow

Graphic showing the process flow to submit and track jobs on workstations
Installation and configuration steps for setting up an end-to-end with z-centric capabilities environment shows the steps required to set up your end-to-end with z-centric capabilities environment.
Table 1. Installation and configuration steps for setting up an end-to-end with z-centric capabilities environment
To... Refer to...
Plan your end-to-end environment with z-centric capabilities and install the HCL Workload Automation Agent. HCL Workload Scheduler for Z: Planning and Installation
Install the dynamic domain manager and agent. HCL Workload Automation: Planning and Installation
Configure the HCL Workload Automation Agent properties. Configuring the HCL Workload Automation Agent settings
Define the HCL Workload Automation Agent and dynamic domain manager destinations. Defining destinations with the ROUTOPTS statement
Define the HCL Workload Automation Agent workstations. Defining and managing HCL Workload Automation Agent workstations in the database
Define dynamic workstations. Defining and managing dynamic workstations
Configure the SSL connection protocol, if you did not change the default configuration of the HCL Workload Automation Agent. Setting the security features
Customize the connection parameters. Customizing the HTTP connection with the HTTPOPTS statement