Step 17. Activating support for the product dialog and programming interface using the server

Include this task when activating an HCL Workload Automation for Z server. To use the Dynamic Workload Console, see Step 20. Activating support for Dynamic Workload Console.

The HCL Workload Automation for Z dialogs and programming interface can be used on a z/OS® system other than the system where the controller is running. A server is required, running on the same z/OS® system as the controller.

The dialogs and the programming interface on the remote z/OS® system communicate with the server using APPC or TCP/IP. The EQQXLUSL help panels flow describes how to activate the communication with the server using the dialog.

The APPC communication requires also the VTAM® and APPC definitions that are described in the following sections.

For further information, see the following publications:
  • VTAM® Resource Definition Reference
  • APPC Management
  • MVS™ Initialization and Tuning Reference

See also member EQQVTAMS in the EQQJOBS output library or SEQQSAMP library.

To activate the APPC communication, perform the following steps:
  1. The server tasks run on the same system as the controller.
  2. On the system where the servers and the controller run, you must define the following LUs:
    • One LU for the server 'without' the BASE keyword, and specifying the server started task as SCHEDULER.
  3. On the system where you want to enable TSO users to communicate with HCL Workload Automation for Z via the server interface, you must define one LU with the keywords BASE and SCHED; that is:
    • An APPC MASTER LU 'with' the BASE keyword, and specifying SCHED(ASCH). This LU is not for HCL Workload Automation for Z; it is an APPC requirement that there be a BASE LU with SCHED(ASCH) on every system where APPC is used.
  4. When the servers and the APPC address space are all started, you will see messages in the SYSLOG and server EQQMLOGs, stating that communication has been established between the server and APPC. These messages are displayed during the first start and after an IPL.
  5. The dialog user then selects option 0.1 and specifies the name of the controller subsystem with which he wants to communicate, and the LUNAME of the server via which that communication is to be routed. For more information on specifying these values, press the PF1 (help) on panel EQQXLUSL.

The HCL Workload Automation for Z dialog code in the TSO logon address space then sends an APPC request which is picked up by the APPC BASE LU on that system and routed to the (server) LU specified in the request. The server then passes the dialog data to the controller across the z/OS® subsystem interface, serving as a local proxy for the dialog user. The controller cannot tell whether it is talking to a local ISPF dialog user, or to a remote user via a server.