Configuring the controller to work with Tivoli Enterprise Portal

Perform the following steps to make the Tivoli® Enterprise Portal work with HCL Workload Automation for Z:
  • Include the data set used by the monitoring task in your JCL procedures and configure the start options of the controller.

    The DD Name of the data set used by the monitoring task to store events for IBM Z Monitoring is EQQMONDS. EQQMONDS is not in the list of required data sets, so you must include it in your JCL procedures if you want to be able to monitor events with the Tivoli Enterprise Portal. For information about creating JCL procedures and including optional data sets in the procedure, see HCL Workload Scheduler for Z: Planning and Installation.

  • Configure the MONOPTS initialization statement to enable monitoring by Tivoli Enterprise Portal.

    This statement defines the runtime options to HCL Workload Automation for Z and is used by the controller and the standby controller.

    If the MONOPTS option is set, a specific controller subtask called monitoring task is started at initialization time. This subtask is dedicated to sending events to the Tivoli Enterprise Portal.

  • Optionally, configure the OPCOPTS initialization statement to set the codepage used in the communication process between HCL Workload Automation for Z and Tivoli Enterprise Portal, and the MONALERT parameter of the ALERTS statement to define for what conditions alerts should be sent to the Tivoli Enterprise Portal monitoring agent.
  • Optionally, configure the MONPOL initialization statement to define monitoring policies so that, for example, operations are automatically selected for monitoring.
  • If you use a TCP/IP stack name different from TCPIP default value, code the TCPOPTS statement with the TCPIPJOBNAME parameter set to the TCP/IP stack name.

For a detailed description of the parameters and syntax of the ALERTS, MONOPTS, MONPOL, OPCOPTS, and TCPOPTS initialization statements, see Customization and Tuning.