Communicating with EQQYCOM

Requests to HCL Workload Automation for Z to perform particular actions are calls to EQQYCOM, using normal z/OS® linkage conventions.

You must create a program that calls EQQYCOM and provide it with the necessary instructions, such as a parameter list, to enable HCL Workload Automation for Z to perform the required action. With each call to EQQYCOM, you can make one HCL Workload Automation for Z request.

EQQYCOM can be linked with the modules from which it is called, or it can be created as a separate load module and control passed to it using the link macro. If you create EQQYCOM as a separate load module and frequent calls are required, you should, for performance reasons, consider placing EQQYCOM in the link-pack area. All modules in the same job-step must be in an APF-authorized library. The first module loaded at the start of the job-step must also be link-edited with the APF-authorized attribute. In the TSO or TSO-batch environment, you need not have the PIF program authorized.

Details of your request to HCL Workload Automation for Z are a parameter list that you pass to EQQYCOM. Before passing control to EQQYCOM, you must load the address of your parameter list into general purpose register 1.

Note: If you want to run a PIF program from an HCL Workload Automation for Z dialog, ensure that your PIF program is invoked as a separate task. Otherwise, your dialog session will end when the PIF program has completed. For example, you can run a REXX exec that runs your PIF program using the ATTACH command.

Calling EQQYCOM from exits that are taken by the controller address space is not supported and will cause unpredictable results if attempted.