MONOPTS

Purpose

The MONOPTS statement defines monitoring options needed for IBM® Z Workload Scheduler to work with IBM® Tivoli® Monitoring. This statement is used by a controller.

The MONOPTS statement defines the information needed to activate an IBM® Tivoli® Monitoring activity. If this statement is provided, the controller starts the monitoring task used to send events to the Tivoli® Enterprise Portal client interface.

MONOPTS is defined in the member of the EQQPARM library as specified by the PARM parameter on the JCL EXEC statement. Defining this statement requires the definition of an OMVS segment for the controller user ID.

Format


1  MONOPTS?  BULKDISC (
2.1! NO
2.1 YES
1 )  MONHOSTNAME (
2.1 hostname
2.1 IP address
1 )?  MONPORT (
2.1! 7500
2.1 port
1 )

Parameters

BULKDISC YES|NO)
Describes the bulk discovery policy. Valid values are YES and NO, the default is NO.
NO
IBM® Z Workload Scheduler does not perform an automatic discovery. A discovery is possible only manually using the TSO command.
YES
A bulk discovery is performed each time a daily planning action is requested. A discovery can also be requested manually.
MONHOSTNAME(hostname|IP address)
Specifies the hostname or the IP address of the remote monitoring application. For the integration with IBM® Tivoli® Monitoring, this is the hostname of the system where the TEP Integration agent is installed. This parameter is mandatory.
MONPORT(value|7500)
This parameter identifies the port number of the remote monitoring application. This is the port number used by the TEP Integration agent. If not specified, the default value of 7500 will be used. The value specified here must correspond to the value defined on the TEP Integration agent.
MONOPTS  MONHOSTNAME('9.122.227.72')        1
         MONPORT(7500)                      2
         BULKDISC(YES)                      3
In this example of MONOPTS statement:
1
This is the IP address of the TEP Integration agent (remote monitoring application).
2
This is the port number of the TEP Integration agent.
3
A bulk discovery of the monitored resources will be initiated automatically at every planning action (extend, replan).