Reference: KIPGLB global definitions members

A KIPGLB global definitions member contains global parameters that define groups of transactions, PSBs, logical terminals (LTERMs), and classes that you want to monitor. It also controls operating characteristics for the Bottleneck Analysis and Response Time Analysis (RTA) components in the Realtime Monitor. With KIPGLB members, you can record options permanently so that each time you start your OMEGAMON® for IMS for the monitored IMS, the same global settings go into effect.

When an OMEGAMON for IMS started task begins, it determines which KIPGLBxx member to use based on GLOBAL=xx in the PARM setting of the JCL, where xx is the suffix of the KIPGLB. The OMEGAMON for IMS started task loads the member from the RKIPGLBL DD data set. You use the KI2_I1nn_CLASSIC_GLOBAL parameter in PARMGEN to specify the suffix, and the GBL_DSN_GLOBAL_SOURCE_LIB to indicate the name of the partitioned data set that you will use to contain the KIPGLB members.

If you set KI2_I1nn_CLASSIC_GLOBAL to a value of 99, then PARMGEN configures the task to use member KIPGLB99, which is the default member that PARMGEN automatically creates. With any other value, you must run a post-configuration job to create the member and store it in the data set identified by GBL_DSN_GLOBAL_SOURCE_LIB. If you do not specify a value for KI2_I1nn_CLASSIC_GLOBAL, the default is the same value that is assigned to KI2_I1nn_CLASSIC_MPREFIX, such as M0. You still must run the post-configuration job to create the KIPGLB member.

When you run PARMGEN, consider specifying a common partitioned data set for GBL_DSN_GLOBAL_SOURCE_LIB, so that the data set and its KIPGLB members can be shared across multiple runtime environments. Each OMEGAMON for IMS started task does not require its own KIPGLB member. You can reuse KIPGLB members across each task, and, if the data set is accessible, across your runtime environments.