Welcome
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. The documentation has been updated for version 10.2 Fix Pack 2.
Planning and Installation
Planning
Planning your configuration
When planning the configuration for your installation, consider the areas explained in the following topics, which describe the connections between the HCL Workload Automation for Z systems and provide some examples of basic configurations.
How to connect HCL Workload Automation for Z systems
HCL Workload Automation for Z systems can be connected by using any of the following methods.
z/OS cross-system coupling facility
HCL Workload Automation for Z uses the z/OS cross-system coupling facility (XCF) to connect HCL Workload Automation for Z systems using XCF communication links.

Product requirements
This section contains links to the HCL Workload Automation Product Requirements.
Detailed System Requirements for HCL Workload Automation, Version 10.2.5
Detailed System Requirements for Dynamic Workload Console, Version 10.2.5
Product Library in PDF format
This section contains links to the PDF versions of all the publications provided in Product Documentation for HCL Workload Automation.
Overview
Mobile Applications Userʼs Guide
Dynamic Workload Console User's Guide
AI Data Advisor (AIDA) User's Guide
Scheduling Job Integrations with HCL Workload Automation
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.2.5.
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. The documentation has been updated for version 10.2 Fix Pack 2.
- 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
  - About this publication
  - Planning
    - Overview
    - Planning your configuration
      When planning the configuration for your installation, consider the areas explained in the following topics, which describe the connections between the HCL Workload Automation for Z systems and provide some examples of basic configurations.
      - Trackers
      - Initialization statements
        HCL Workload Automation for Z initialization statements specified in the parameter library describe, among other things, the configuration of your installation.
      - Communication
      - How to connect HCL Workload Automation for Z systems
        HCL Workload Automation for Z systems can be connected by using any of the following methods.
        TCP/IP
        HCL Workload Automation for Z uses Transmission Control Protocol/Internet Protocol (TCP/IP) to connect a tracker to the controller using a TCP/IP link.
        z/OS cross-system coupling facility
        HCL Workload Automation for Z uses the z/OS cross-system coupling facility (XCF) to connect HCL Workload Automation for Z systems using XCF communication links.
        VTAM® (network communication function)
        HCL Workload Automation for Z uses the network communication function (NCF) to connect a tracker to the Z controller using a VTAM link. The Z controller transmits work to the tracker through NCF, and the same connection is used to pass back event information.
      - Workstation destination
        The various physical and logical locations where tasks are performed at your installation are represented in HCL Workload Automation for Z by workstations. Each workstation groups related activities. Every operation in the application description database and the current plan is associated with a workstation. You define workstations in the workstation description database.
      - Workload restart
        You can use workload restart (WLR) to restart and reroute work in your HCL Workload Automation for Z configuration. WLR tracks the status of workstations. It can be invoked when a workstation becomes inactive; that is, when the Z controller cannot communicate with the tracker at the destination that the workstation represents.
      - JES considerations
        The JES type and configuration in your installation has implications on your HCL Workload Automation for Z configuration.
      - Basic configuration examples
        The examples in this topic shows the configurations using the various connection methods. They are based on a single-image z/OS environment.
      - Basic data store configuration examples
        You need to install a Data Store for each spool tracked by HCL Workload Automation for Z in the configuration.
      - Configuring a backup controller for disaster recovery
    - Planning your installation
      During the planning stage of your HCL Workload Automation for Z project, consider carefully how you want to install the scheduler to control your production workload. The installation consists of installing the tracker and Z controller in combinations to suit your processing environment, and connecting them using one or more of the communication methods described in zos/src_inst/eqqi1planyrconfig.html#planyrconfig. Later, you can customize your HCL Workload Automation for Z systems to include more functions.
  - Installing and migrating HCL Workload Automation for Z
  - Installing Dynamic Workload Console and Z connector
    How to install, upgrade, configure, and uninstall the Dynamic Workload Console and Z connector, which is automatically installed with a Dynamic Workload Console instance.
  - Deploying with containers
    Docker is a state-of-the-art technology that creates, deploys, and runs applications by using containers. Packages are provided containing an application with all of the components it requires, such as libraries, specific configurations, and other dependencies, and deploy it in no time on any UNIX, Windows, and Linux on Z workstation, regardless of any different settings between the source and the target workstation.
  - Deploying AI Data Advisor
    You can deploy AI Data Advisor (AIDA) by using Docker or Kubernetes.
  - Installing HCL Workload Automation Agent (z-centric)
    The following topics describe how to install, migrate, and uninstall the HCL Workload Automation Agent (also known as z-centric agent).
  - Installing HCL Workload Automation Agent on IBM i systems
  - Integrating Workload Automation with Zowe™
    Zowe™ is an open source project that enables you to interact with z/OS through modern interfaces. You can issue Workload Automation commands through the Zowe command-line interface (CLI), and access Workload Automation REST APIs through the Zowe API Mediation Layer (ML).
  - Sample library (SEQQSAMP)
    The SEQQSAMP library contains samples to help you install and customize HCL Workload Automation for Z.
  - Invoking the EQQEXIT macro
  - Invoking the EQQLSENT macro
- 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
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z
Messages and Codes
Glossary
Notices

z/OS cross-system coupling facility

HCL Workload Automation for Z uses the z/OS cross-system coupling facility (XCF) to connect HCL Workload Automation for Z systems using XCF communication links.

When one or more trackers are connected to the Z controller through XCF communication links, the HCL Workload Automation for Z systems form an XCF group. The systems use XCF group, monitoring, and signaling services to communicate. The Z controller submits work and control information to the trackers using XCF signaling services. The trackers use XCF services to transmit events back to the Z controller.

XCF connections let HCL Workload Automation for Z support a hot standby Z controller and automatic-workload-restart functions.