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
Installing HCL Workload Automation for Z
Migrating
This chapter provides information to help you plan your migration from HCL Workload Automation for Z version 9.5 with APAR HC00002 installed, to version 10.1 Fix Pack 3.
Planning for migration
Migration strategies
Getting the correct software parts

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
  - Installing HCL Workload Automation for Z
    - Installing
      This chapter describes the tasks you perform to install HCL Workload Automation for Z.
    - Verifying your installation
      What to consider when verifying your installation.
    - Migrating
      This chapter provides information to help you plan your migration from HCL Workload Automation for Z version 9.5 with APAR HC00002 installed, to version 10.1 Fix Pack 3.
      - Planning for migration
        Migration considerations
        Customization considerations
        Migration strategies
        Establishing the required environment
        Program requirements
        JES and SMF exits
        Migrating to existing subsystem definitions
        Migrating to new subsystem definitions
        Getting the correct software parts
        Load modules
        The ISPF environment
        Installation and verification
        Parallel testing
        Migrating DB2 reporting
        If you are migrating from V9.5 with APAR HC00002 installed, you do not need any migration action for the reporting data.
        Migrating the backup controller
        Changing a shared DASD tracker-to-controller connection to an NCF, XCF, or TCP/IP connection
        Running on upgraded operating systems
      - Migrating actions
      - Migrating the controller with the IWSZSELFUPGRADE application
      - Installing or upgrading the HCL Workload Automation for Z agent automatically
      - Performing fallback
  - 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

Getting the correct software parts

The HCL Workload Automation for Z load modules, panels, messages, and other software parts have the same name as they had in previous HCL Workload Automation for Z releases. Make sure that the users of HCL Workload Automation for Z services run the same level of software as the subsystem address space.