Activating and configuring Output collector

This is a summary about how to activate and configure the Output collector started task.

To activate the Output collector, run the EQQJOBS installation aid and go to panel EQQJOBSC of option 1 - Create sample job JCL. In the EQQJOBSC panel you specify that Output collector will be running and you enter the names of the SYSOUT class and of the WRITER task that Output collector uses to copy the logs to the JES spool. This creates the sample started task procedure and initial parameters for running Output collector and allocates the data sets (EQQOUCEV and EQQOUCKP) used for receiving job log information from the controller. See HCL Workload Scheduler for Z: Planning and Installation for a detailed description.

To fully configure Output collector, you must act on the following initialization statements in the controller:
HTTPOPTS
Add the following keywords:
OUTPUTCOLLECTOR
Specify that the feature will be running.
JLOGHDRTEMPL
Specify the name of the EQQPARM library member that contains the job log header. This keyword is not exclusive to the Output collector, but can be used for all the job logs produced in the z-centric environment.

These keywords are independent of the JOBLOGRETRIEVAL keyword, which enables users to request job logs manually through the usual HCL Workload Automation for Z interfaces.

ROUTOPTS
To work with the Output collector task, it is required that at least one HCL Workload Automation Agent (z-centric) destination is defined in the keyword HTTP or HTTPS.
OPCOPTS
Optionally, add the OUTCOL keyword to specify the name of the Output collector started task to the controller. In a sysplex environment this enables the standby controller to continue the interaction with Output collector.
OUCOPTS
Add this initialization statement and its keywords to define:
  • The names of the JES SYSOUT class and of the WRITER task used by Output collector (if they were not defined with EQQJOBS).
  • The name of the EQQPARM library member that contains the OPCOPTS, ROUTOPTS, and HTTPOPTS statements.
  • The number of threads (range) that Output collector can open.
  • The maximum number of job logs that Output collector can retrieve concurrently from an agent.
  • The name of the controller for which Output collector is started.

In a sysplex configuration the Output collector started task must reside in the same image where the controller is.