Step 16. Activating support for the API

Include this task when installing a Z controller, or standby Z controller that you want to communicate with through the HCL Workload Automation for Z API.

HCL Workload Automation for Z uses LU to LU communication to pass data between an ATP and a subsystem through the API. To use API requests GET, PUT, and DELETE, the LU that the ATP sends requests to (the target LU) must be owned by the Z controller. For CREATE requests, if the target LU is not owned by an HCL Workload Automation for Z address space where an event-writer task is started, the ATP must send requests so that the events are broadcast on the target z/OS system. Tivoli® Workload Automation: Developer's Guide: Driving Tivoli® HCL Workload Automation for Z and HCL Workload Automation for Z: Customization and Tuning describe when a request is broadcast.

To activate support for the API, perform these actions in the order shown:
  1. Define VTAM® resources.
  2. Update APPC options.
  3. Activate HCL Workload Automation for Z support for APPC.
If you are installing a standby Z controller, perform corresponding actions on the standby system.
You might need to refer to one or more of these publications:
  • VTAM® Resource Definition Reference
  • APPC Management
  • z/OS Initialization and Tuning Reference
  • Tivoli® Workload Automation: Developer's Guide: Driving Tivoli® HCL Workload Automation for Z, which documents the API

The actions described here are based on z/OS systems. If you use a later z/OS release, check for enhancements that might make some actions unnecessary.