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.
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.

Product requirements
This section contains links to the HCL Workload Automation Product Requirements.
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.3.
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
      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.
      - 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. For examples of more complex configurations, see zos/src_inst/eqqi1configexamp.html#configexamp.
      - 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

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.

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.

The event records are stored in a sequential file called the event data set identified by the EQQEVDS DD name.

HCL Workload Automation for Z also uses the event data set to write checkpoint information for submission requests. The first record of the data set is used for this purpose, so the EQQEVDS DD name must be specified for all HCL Workload Automation for Z address spaces. The same data set can be used for both submit checkpointing and the event-writer subtask.

To add feedback about this topic, select the following checkbox:

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners Four, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site. Personal data should not be shared in this comment box. See our Privacy Statement to understand how personal data is used.