Configuring the OMEGAMON AI for CICS monitoring agent

Edit online

You configure the OMEGAMON® component of the monitoring product to define Sysplex-level entities, assign the current runtime environment to a Sysplex, install product-specific data on the Tivoli Enterprise Monitoring Server, and register the OMEGAMON AI for CICS monitoring agent in the Tivoli Enterprise Monitoring Server address space.

You also configure the persistent data store for the product historical data and allocate the data sets to store the system-level data. These parameters are specified in the KC5 section of the PARMGEN configuration profile.

Default values are provided for all required parameters and some optional ones. If you do not want to customize these parameters, and you do not want to enable optional features, you can complete the configuration by accepting these defaults.

The first time you configure OMEGAMON AI for CICS into an runtime environment, you should accept the configuration default values where ever possible. You should consider enabling the self-describing agent feature prior to connecting the OMEGAMON AI for CICS and OMEGAMON AI for CICS TG agents to the Tivoli Enterprise Monitoring Server. See the IBM® Tivoli® Monitoring Administration Guide Version 6.3.0 for additional information about the self-describing agent.

After you complete the runtime environment configuration and run the product Installation Verification Program (IVP), then you should consider reviewing the various product features that are available and adjusting configuration parameters to meet your site's installation requirements.

Modifying VTAM® node and application definitions

The OMEGAMON AI for CICS agent (IBMC5) has optional VTAM configuration; review the following common agent parameter configuration default parameters:

** (Optional) Agent's local VTAM and logon information:  
KC5_AGT_VTAM_APPL_PREFIX          CTDC5   
KC5_AGT_VTAM_NODE                 CTDC5N  
KC5_AGT_VTAM_APPL_OPERATOR        CTDC5OR 
KC5_AGT_VTAM_APPL_KC5INVPO        CTDC5VP 
KC5_AGT_VTAM_APPL_NCS             CTDC5NC 
KC5_AGT_VTAM_APPL_AA              CTDC5AA

For more information on these common agent parameters see "Common parameters" in the Reference section in OMEGAMON shared documentation.

If your agent is configured to communicate to the Tivoli Enterprise Monitoring Server through SNA, then the following primary Tivoli Enterprise Monitoring Server VTAM configuration values must be supplied:

** Agent's Primary TEMS VTAM information:  
KC5_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS 
KC5_TEMS_VTAM_LU62_MODETAB        KDSMTAB1 
KC5_TEMS_VTAM_NETID               USCACO01 
KC5_TEMS_VTAM_APPL_LLB_BROKER     CTDDSLB

For more information on optional local agent VTAM and logon information and primary Tivoli Enterprise Monitoring Server VTAM configuration values, see OMEGAMON shared documentation and the IBM Z OMEGAMON AI for CICS: Parameter Reference.

Updating agent and Tivoli Enterprise Monitoring Server protocols

If you are configuring the agent with the default protocols of IP and IP.PIPE and you modified the Tivoli Enterprise Monitoring Server port number, you must update the agent parameters. Change all occurrences of 1918 to your installation assigned Tivoli Enterprise Monitoring Server port number. The hub, the Tivoli Enterprise Monitoring Server and the connecting agent(s) must all use the same port number:

KC5_TEMS_TCP_PIPE_PORT_NUM        1918     * IP.PIPE
KC5_TEMS_TCP_UDP_PORT_NUM         1918     * IP.UDP

If you are configuring the agent and Tivoli Enterprise Monitoring Server with a TCP/IP protocol, you will need to specify the hostname of the Tivoli Enterprise Monitoring Server and the hostname where the agent is running:

KC5_TEMS_TCP_HOST                 "hostname"

where hostname is the hostname of the Tivoli Enterprise Monitoring Server that the agent is connecting to.

KC5_AGT_TCP_HOST                 "hostname"

Where hostname is the hostname of the system that the agent will be running.