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.
Scheduling End-to-end with z-centric Capabilities
Monitoring and recovering jobs
Setting up and running automatic recovery for jobs
HCL Workload Automation for Z supports the use of automatic recovery statements in HCL Workload Automation Agent scripts.

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
- 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
  - About this publication
  - Configuring
  - Customizing the HTTP connections
    The communication between the HCL Workload Automation Agents and the HCL Workload Automation for Z controller is direct, through the HTTP or HTTPS protocol.
  - Defining user IDs and passwords with the USRREC statement
    Use the USRREC initialization statement to define the passwords for the users who need to schedule jobs to run on Windows™ workstations. You do not need to do this if you run native job types on non-Windows workstations.
  - Defining variables and passwords for local resolution
  - Defining and managing HCL Workload Automation Agent workstations in the database
    After defining the destinations of your HCL Workload Automation Agents, you need to define the HCL Workload Automation Agents as HCL Workload Automation for Z computer automatic workstations.
  - Defining and managing dynamic workstations
    When you add dynamic capabilities to your environment, you can schedule your workload dynamically.
  - Setting the security features
  - Defining and managing jobs
  - Administering IBM i dynamic environment
    On overview on how to administer the HCL Workload Automation IBM i dynamic environment.
  - Monitoring and recovering jobs
    - Job status notifications
    - Setting up and running automatic recovery for jobs
      HCL Workload Automation for Z supports the use of automatic recovery statements in HCL Workload Automation Agent scripts.
      - Automatic-recover-control statement for HCL Workload Automation Agent scripts
        Each automatic-recovery-control statement describes an error situation and the recovery actions for it.
  - Running a script when a job completes
  - Viewing the job logs from the host
    An overview on how to view or retrieve the job logs issued in the z-centric environment and how to attach a header with job run information on top of each log.
  - Troubleshooting
    Troubleshooting agent problems
  - Configuring to schedule J2EE jobs
  - Security order of precedence used for the execution of J2EE tasks
  - Configure to schedule job types with advanced options
  - Managing return codes
  - Collecting job metrics
- Quick Reference
- Diagnosis Guide and Reference
- Workload Automation Programming Language for z/OS User's Guide and Reference
- Driving HCL Workload Automation for Z

Setting up and running automatic recovery for HCL Workload Automation Agent jobs

HCL Workload Automation for Z supports the use of automatic recovery statements in HCL Workload Automation Agent scripts.

When you create or edit an HCL Workload Automation Agent script, start the lines where you specify the automatic recovery statements with //* OPC, //*%OPC, or //*>OPC. These lines are removed before the script is downloaded onto the HCL Workload Automation Agents.

You can run the following recovery actions on HCL Workload Automation Agent jobs:

Restart the current occurrence at the failed operation, with or without JCL changes.
Restart the current occurrence at another operation.
Add occurrences of special recovery applications. Make the restart of the failed occurrence dependent on the completion of the recovery occurrences.
Release a dependent occurrence.

Data set cleanup is not available.