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
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.
Configuring the heartbeat checking interval for z-centric agents and dynamic domain managers

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.
    - Customizing HTTP connection with HTTPOPTS statement
      HTTPOPTS statement to customize HTTP connection.
    - Customizing the http timeout on the Dynamic Workload Console
      You can increase the length of the HTTP connection timeout in the Dynamic Workload Console to allow more time for retrieving objects related to the z-centric environment.
    - Configuring the heartbeat checking interval for z-centric agents and dynamic domain managers
    - Configuring the connection between the z-centric agent and controller through a proxy
      You can configure that one or more z-centric agents connect with the controller through a proxy server, by defining the proxy properties in the ROUTOPTS statement and JobManager.ini file.
    - Starting and stopping HTTP subtasks
      An HTTP Server subtask and an HTTP Client subtask run the transmission of data between the scheduler and the HCL Workload Automation Agents on the distributed side. These subtasks automatically start at controller startup.
  - 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
  - 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
  - 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

Configuring the heartbeat checking interval for z-centric agents and dynamic domain managers

You can configure the HCL Workload Automation for Z controller to check at intervals if all or specific attached z-centric agents and dynamic domain managers are running. Without the use of this mechanism the controller does not register, until the next job submission occurs, that a workstation has become unavailable. This may impact your scheduling plans.

The use of this feature is optional and configurable by adding the PULSEIVL keyword in the following HCL Workload Automation for Z initialization statements:

HTTPOPTS: The value for PULSEIVL is valid globally for all the attached z-centric agents and dynamic domain managers.
ROUTOPTS: PULSEIVL is featured as a parameter in the HTTP/HTTPS destination keyword and in this case defines the heartbeat checking interval of the specific agent defined in the destination. This option is useful when heartbeat checking is wanted only on the more strategic agents or when a different checking frequency is desired.
The pulse interval of a destination can be updated using the HTTP refresh destination command without having to stop the controller.

The value is expressed in minutes and can range from 0 to 1440. The value 0 means that the heartbeat checking:

Is not run for z-centric agents.
Is run for dynamic domain managers according to the policy established by the Z controller.

For example:

HTTPOPTS  ...
          PULSEIVL(60)
          ...

ROUTOPTS HTTPS(DDM1:’162.17.129.32’/65232/B/5)

This configuration sets a heartbeat checking interval of 60 minutes for all z-centric agents and dynamic domain managers, but for DDM1 the interval is set to 5 minutes.