Configuring OMEGAMON AI for CICS using the PARMGEN method

You configure OMEGAMON AI for CICS by accepting or customizing the values of parameters that begin with KC2 (OMEGAMON for CICS (3270)) and KC5 (OMEGAMON® component).

For guidance on setting parameter values, see the following sources of information:

Comments in the configuration profiles
Online help for the configuration profile
OMEGAMON shared documentation
IBM® OMEGAMON AI for CICS: Parameter Reference

Before you configure the OMEGAMON AI for CICS agent, you must complete the tasks listed in the following table.

Table 1. Tasks to complete before configuring OMEGAMON AI for CICS
Configuration task	Location of instructions
Set up PARMGEN work libraries for your runtime environment	OMEGAMON shared documentation
Set up the PARMGEN configuration profile for your runtime environment	OMEGAMON shared documentation
(Optional) Configure a Tivoli® Enterprise Monitoring Server Note: If OMEGAMON AI for CICS is the only product in this runtime environment, then this step is not required. Review the documentation for your other products in this runtime environment to determine if this step is required.	OMEGAMON shared documentation. In addition to Configuring, see the Scenarios and how-tos section, and "Common parameters" in the Reference section.
(Optional) Configure an OMEGAMON Subsystem Note: If OMEGAMON AI for CICS is the only product in this runtime environment, then this step is not required. Review the documentation for your other products in this runtime environment to determine if this step is required.	OMEGAMON shared documentation Note: Configure only one OMEGAMON Subsystem for each LPAR.
(Optional) Configure the OMEGAMON enhanced 3270 user interface address space	OMEGAMON shared documentation Note: You only need to configure one OMEGAMON enhanced 3270 user interface address space in a Sysplex.

Configuration prerequisites

Identify where your hub Tivoli Enterprise Monitoring Server is to reside. Then, determine which Tivoli Enterprise Monitoring Server your OMEGAMON AI for CICS and OMEGAMON AI for CICS TG agents will report to and where your monitored subsystems will run. See the OMEGAMON shared documentation for additional information regarding Tivoli Enterprise Monitoring Server planning and configuration.

Each OMEGAMON AI for CICS and OMEGAMON AI for CICS TG agent must report to a Tivoli Enterprise Monitoring Server. The Tivoli Enterprise Monitoring Server, that these agents report to, can either be installed on a z/OS® system or on a distributed platform. OMEGAMON AI for CICS and OMEGAMON AI for CICS TG can report to a Tivoli Enterprise Monitoring Server configured with any of the supported IBM Tivoli Monitoring protocols.

Review your system environment to determine where the CICS® regions and CICS TG daemons will run for your monitoring. You will need to run one OMEGAMON AI for CICS agent and OMEGAMON AI for CICS collection address space on each LPAR where the CICS regions that you wish to monitor. You will need to run one OMEGAMON AI for CICS TG agent on each LPAR where the CICS TS daemon that you wish to monitor.

Review your runtime environment configuration default settings to determine whether or not they can be used for your OMEGAMON AI for CICS product configuration. See "Common parameters" in the Reference section of OMEGAMON shared documentation for additional information regarding runtime environment and Global configuration parameters.

Review the PARMGEN configuration profiles required for user customization:

WCONFIG($GBL$USR) global configuration profile
If you want to configure the full IBM Z OMEGAMON AI for CICS product into a runtime environment, you must specify Y for the following parameter values:
```
** IBM Z OMEGAMON for CICS: KC5 flag   
CONFIGURE_CICS_KC5           "Y"                       
** IBM OMEGAMON for CICS TG on z/OS: KGW flag
CONFIGURE_CICS_TG_KGW        "Y"   
```
WCONFIG(RTENAME) LPAR-specific runtime environment configuration profile

The first time you create a runtime environment for the OMEGAMON AI for CICS product, complete the configuration using runtime environment and product or configuration default values where ever possible. There are some parameter default values that are typically overridden due to installation requirements.

These are the OMEGAMON AI for CICS product defaults you might want to override:

Started tasks names, which might be generated as part of your runtime environment configuration, use these default configuration values:

IBMDS

Tivoli Enterprise Monitoring Server; you can optionally define a Tivoli Enterprise Monitoring Server on a distributed platform.

IBMCN

OMEGAMON Subsystem; this is an optionally started task.

IBMTOM

OMEGAMON enhanced 3270 user interface; this started task is recommended, but you only need to create one started task. You do not need one in every runtime environment, because it can communicate with multiple hub Tivoli Enterprise Monitoring Servers and agents across multiple runtime environment configurations.

IBMOC0

OMEGAMON for CICS (3270)

IBMC5

OMEGAMON AI for CICS agent; by default, the agent is configured in its own address space, but during configuration, you can to configure the agent to run in a Tivoli Enterprise Monitoring Server address space.)

IBM is the default started task prefix. You can either override this default during the product configuration or you can change it by modifying the runtime environment configuration parameter. For example, the PARMGEN parameter is: RTE_STC_PREFIX.
VTAM® Node and application definitions
Many of the components configured to run with OMEGAMON products require VTAM application definitions. CTD is the VTAM node and applid prefix generated by default. For each component that you configure that requires VTAM, you might want to specify a default other than the configuration default. See the following sections to see a list of the applicable product parameters which you might want to modify depending on your site's installation requirements.

For more information on PARMGEN, see OMEGAMON shared documentation.

Excluding products from the PARMGEN customization list

After installing OMEGAMON AI for CICS V5.6.0 into the CSI, PARMGEN presents the following products in the PARMGEN customization list:

KC5  IBM Z OMEGAMON for CICS V560     
KDS  Tivoli Enterprise Monitoring Server V623         
KGW  IBM OMEGAMON for CICS TG on z/OS V560

Exclude any components that you do not want to configure in this runtime environment.

If you plan to monitor CICS regions from the LPAR associated with this runtime environment, then OMEGAMON AI for CICS is required. If you are connecting your OMEGAMON AI for CICS agent to a Tivoli Enterprise Monitoring Server on a distributed platform or a Tivoli Enterprise Monitoring Server that is configured in another runtime environment, then you can exclude Tivoli Enterprise Monitoring Server V6.3.0 from this runtime configuration.

If you plan to monitor CICS TG daemons or daemons on the LPAR associated with this runtime environment, then OMEGAMON AI for CICS is required.

During the PARMGEN runtime environment configuration process for all of the previously mentioned products, the following component parameters are generated:

OMEGAMON Subsystem (Optional)
The default STC: IBMCN and the parameter prefix: RTE.
Tivoli Enterprise Monitoring Server
The default STC: IBMDS and the parameter prefix: KDS

Customizing component parameters with PARMGEN

During the PARMGEN configuration process for OMEGAMON AI for CICS, the following component parameters will also be generated and configured:

OMEGAMON enhanced 3270 user interface (default STC): IBMTOM)
OMEGAMON for CICS (3270) (default STC): IBMOC0)
OMEGAMON AI for CICS (default STC): IBMC5)

While all of these components are configured, they do not all need to be started in your runtime environment.

OMEGAMON for CICS (3270) is the only required started task.