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.
Planning and Installation
Planning
Planning your configuration
This chapter describes several areas to consider when planning the configuration for your installation. It explains connections between HCL Workload Automation for Z systems and provides some examples of basic configurations.
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.

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
  - About this publication
  - Planning
    - Overview
    - Planning your configuration
      This chapter describes several areas to consider when planning the configuration for your installation. It explains connections between HCL Workload Automation for Z systems and provides some examples of basic configurations.
      - Planning considerations
        HCL Workload Automation for Z must recognize when events occur; for example, when a started task or job begins to run or terminates, or when a data set has been printed. It uses JES and SMF exits to obtain this information from z/OS and to create event records describing the changes in the system.
      - 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.
      - 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 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
        Examples of HCL Workload Automation for Z configurations using the various connection methods.
      - 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.
        SNA-only connection
        XCF-only connection
        TCP/IP-only connection
        Mixed SNA and XCF connection
        Mixed TCP/IP and XCF connection
      - Configuring a backup controller for disaster recovery
    - Planning your installation
  - Installing HCL Workload Automation for Z
  - Installing Dynamic Workload Console and Z connector
  - Deploying with containers
    Getting started with containers
  - Deploying AI Data Advisor
    You can deploy AI Data Advisor (AIDA) by using Docker or Kubernetes.
  - Installing HCL Workload Automation Agent (z-centric)
    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
    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.
  - Configuration examples
  - 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

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.

If you have a shared spool, for example, JES2 MAS, you can have a single Data Store for multiple trackers. Three kinds of controller-Data Store connections are supported: SNA, XCF, and TCP/IP. The Data Store type must be defined either as SNA, XCF, or TCP/IP. The same controller can connect, at the same time, with more than one Data Store, using a different connection type for each Data Store. Note that you need separate LU values: one for the Data Stores and one for the trackers. All Data Stores work on a reserved destination which must always have the same name.