TCP/IP connected
A z/OS system with a TCP/IP connection shows two HCL Workload Automation for Z address spaces with a TCP/IP connection on a z/OS system.
You represent this system to the scheduler by defining
a computer workstation with a destination field that specifies the
destination name of the tracker.
The controller transmits
JCL, release commands, WTO messages, and cleanup requests across the
TCP/IP link. The tracker receives
data across the TCP/IP link and performs the following actions:
- Submits JCL for batch jobs to the JES internal reader
- Writes the JCL for started tasks into the EQQSTC data set and
issues
START procname
z/OS commands - Issues JES release commands for jobs in HOLD status
- Submits the cleanup job.
The event-tracking routines create event records to describe activities that occur on the system. These records are added to the tracker event writer queue in ECSA. The tracker processes the queue, transmits the records to the controller across the TCP/IP link, and writes the events into the event data set. The IP task in the controller receives the event records, and the current plan is updated.
Note: You must specify EQQEVDS for a controller, even if
an event writer is not started in the controller address space. The
EQQEVDS data set is used for submit checkpointing. It can be the same
data set that is used by an event-writer function. Use a unique EQQEVDS
for each address space of the scheduler.
Example EQQPARM members for Figure 4 shows the initialization statements you can use to create the configuration in A z/OS system with a TCP/IP connection.
Members for the controller | Members for the tracker |
---|---|
OPCECNT
|
TRKA
|
STDEWTREWTROPTS EWSEQNO(01) |
Note: In this example, the name of the destination is
DEST1. The destination name is defined also in the destination field
of the workstation.