Tracker and controller in a single address space

A tracker and controller configured in a single address space shows one HCL Workload Automation for Z address space performing the function of both the tracker and the controller. To optimize availability, do not use this configuration in your production environment. However, at least one of your HCL Workload Automation for Z test environments will probably use this configuration.

You represent this system to HCL Workload Automation for Z by defining a computer workstation with a blank destination field. The submit subtask 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
The event-tracking routines create event records to describe activities that occur on the system. These records are added to the subsystem event writer queue in ECSA. The event writer subtask processes the events and:
  • Adds the event to the data router queue, and the current plan is updated
  • Writes the events into the event data set.
Figure 1. A tracker and controller configured in a single address space

eqqi10cd The graphic shows a controller and tracker in the same address space.

Example EQQPARM members for Figure 6 shows initialization statements to create the configuration in A tracker and controller configured in a single address space.

Table 1. Example EQQPARM members for Figure 6

EQQPARM members for the address space
OPCECNT
OPCOPTS  OPCHOST(YES)
         ERDRTASK(0)
         EWTRTASK(YES)
         EWTRPARM(STDEWTR)
STDEWTR
EWTROPTS EWSEQNO(01)

Configuration examples contains HCL Workload Automation for Z configuration examples for more complex environments.