OMEGAMON XE for IMS v5.3.0 General Availability Notes

Content

Packaging

The SMP/E package contains the following FMIDs:

HKI5530 - OMEGAMON XE for IMS on z/OS v5.3.0

HKOB730 - OMNIMON Base with enhanced 3270UI

Software Prerequisites

z/OS v1.13 or higher

IBM Tivoli Monitoring v6.3.0 Fix pack 2 or higher

IMS v10.1 or higher

Recommended maintenance levels

Product	Release	Maintenance Level
OMEGAMON XE for IMS on z/OS	5.3.0	UA78634
OMNIMON Base	7.3.0	UA76751
PARMGEN	3.1.0	UA77851
IBM Tivoli Monitoring	6.3.0 Fp2 or higher	UA69363
IBM Connect Extensions	v2.2, v2.3, or v2.4
IMS Performance Analyzer	4.4	PI44855/UI30221
IMS Problem Investigator	2.4	PI44856/UI30338

Changes to the Global definitions

Definition of groups, RTA slots, and Bottleneck Analysis settings. in previous releases were defined via macros and compiled into a member called KOIGBLxx into RKANMODU. In this release the global definitions have been moved to a source member called KIPGLBxx in its own repository or by default, to RKANPARU.

PARMGEN will create the default global member, KIPGLB99 in the global repository during configuration. It is your responsibility to review your previous global definitions in KOIGBLxx and create one or more KIPGLBxx members. Best practice is to define as few as you need in a common repository dataset that can be shared across Runtime Environments (RTEs).

PARMGEN provides a sample, KIPGLBCV in RKANSAMU, to convert your old compiled global definitions into the new source format.

PARMGEN will add a KIPGLBL DD statement to your Realtime Monitor JCL. It will also add a GLOBAL=xx parameter to identify the KIPGLBLxx member to be used.

Failure to configure the global definitions will result in the following error messages when you start the Realtime Monitor (Classic).

KOIG0302E GVR UNABLE TO LOCATE GLOBAL SOURCE MEMBER KIPGLBM0

KOIG0111E GMP PROCESSING FAILED FOR GLOBAL KIPGLBM0

KOIG0114I GMP DEFAULT COPY OF GLOBAL HAS BEEN SELECTED

The Realtime monitor will continue to initialize with the default values which may not be what you need. In the above example, you need to create member KIPGLBM0. Clone KIPGLB99 and make any desired changes to correct this problem.

IMS User Exits

All of our IMS user exits are now isolated into the xKANMODR library. This was done to reduce the need to recycle the IMS control region in order to apply maintenance.

The xKANMODR library needs to be concatenated into the IMS control region STEPLIB. Remove any previous xKANMOD from a previous release.

In previous releases, components such as RTA and ATF would dynamically intercept IMS in order to collect their data. Now, it is required to have xKANMODR in place before these exits will function. Use the table below to configure the exits at the various IMS releases.

IMS exit types that are used in this product are:

• LOGWRT - Response Time Analysis (RTA)
• IMSMON - Application History (ATF)
• PPUE - Type-1 IMS command support

Best practice: Whenever possible based on the IMS release, you should configure these exits in DFSDFxxx. This allows maintenance to those exits defined in DFSDFxxx and allows the exit to be refreshed without recycling the IMS control region. Use the following table to guide you.

Type	ALIAS	NAME	Purpose	IMS Release	DFSDFxxx	Refresh
LOGWRT	DFSFLGX0	KRIFLGX0	RTA	10.1	no	no
LOGWRT	DFSFLGX0	KRIFLGX0	RTA	11.1	no	no
LOGWRT	DFSFLGX0	KRIFLGX0	RTA	12.1	no	no
LOGWRT	DFSFLGX0	KRIFLGX0	RTA	13.1	yes	yes
LOGWRT	DFSFLGX0	KRIFLGX0	RTA	14.1	yes	yes
IMSMON	n/a	n/a	ATF	10.1	no	no
IMSMON	n/a	n/a	ATF	11.1	no	no
IMSMON	n/a	n/a	ATF	12.1	no	no
IMSMON	n/a	n/a	ATF	13.1	no	no
IMSMON	n/a	KOIMON00	ATF	14.1	yes	yes
PPUE	DFSPPPUE0	KOIPPUE0	Type-1 cmds	10.1	no	no
PPUE	DFSPPPUE0	KOIPPUE0	Type-1 cmds	11.1	no	no
PPUE	DFSPPPUE0	KOIPPUE0	Type-1 cmds	12.1	yes	yes
PPUE	DFSPPPUE0	KOIPPUE0	Type-1 cmds	13.1	yes	yes
PPUE	DFSPPPUE0	KOIPPUE0	Type-1 cmds	14.1	yes	yes

As noted in the table above, IMSMON was introduced in IMS 14.1 For earlier releases, ATF will continue to collect its data via code intercepts.

Sample DFSDFxxx user exit definitions:

<SECTION=USER_EXITS>

EXITDEF=(TYPE=LOGWRT,EXITS=(KRIFLGX0))
EXITDEF=(TYPE=IMSMON,EXITS=(KOIMON00))
EXITDEF(TYPE=PPUE,EXITS=(KOIPPUE0))

Migration

PARMGEN is the only supported configuration tool for this release.

In this release, the journal logging facility which was used by ATF to record its data has been removed. Instead, ATF data is now recorded in a set of z/OS log streams.

These log streams must be configured via PARMGEN before the ATF component will become active. A decision of the type of log stream must be made between DASD only or Coupling Facility structure based log streams.

Look for these parameter variables in the PARMGEN deck for your RTE and configure them.

KI2_LOGR_EHLQ

KI2_LOGR_LS_PREFIX

KI2_LOGR_LS_DATACLAS

KI2_LOGR_LS_STORCLAS

KI2_LOGR_STG_DATACLAS

KI2_LOGR_STG_STORCLAS

KI2_LOGR_ATF_STRUCTNAME

KI2_LOGR_ATF_DASDONLY

KI2_LOGR_ATF_LS_SIZE_DL

KI2_LOGR_ATF_LS_SIZE_SM

KI2_LOGR_ATF_LS_SIZE_DX

KI2_LOGR_ATF_LS_SIZE_SX

KI2_LOGR_ATF_STG_SIZE_DL

KI2_LOGR_ATF_STG_SIZE_SM

KI2_LOGR_ATF_STG_SIZE_DX

KI2_LOGR_ATF_STG_SIZE_SX

A correctly configured ATF startup member would look similar to this:

START ATF,
SANDBOX=OFF,
AUTORESTART=YES,
ATFBUFF=512,
DETLLOGR=BRTEST.IA1W.DL,
SUMMLOGR=BRTEST.IA1W.SM,
DETXLOGR=BRTEST.IA1W.DX,
SUMXLOGR=BRTEST.IA1W.SX,
ATFACT=ON

Where BRTEST is the name of the RTE and IA1W is the name of the IMS system to be monitored. It shows the four log streams to be used. The KI2_LOGR_EHLQ value is added as a prefix to these log stream names and a suffix is added by the z/OS logger to complete the dataset name. There are length limitations to these names and those are noted in the PARMGEN comments for each parameter.

The suffixes used in the log streams are used for these types of records:

DL is used for the detail log stream

SM is used for the summary log stream

DX is used for the detail exceptions log stream

SX is used for the summary exceptions log stream

Transaction Reporting Facility has also been removed. It is replaced by ATF. It is recommended to install IMS Performance Analyzer and IMS Problem Investigator to produce the same TRF reports using ATF data. The recommended maintenance levels are noted above.

KI5DFINL Manual Steps

After PARMGEN configuration is complete, there remains a few important manual steps to perform to complete the configuration. These steps are listed in the KI5DFINL member in RKANSAMU. Some of these items are:

• Customize the Global member
• Configure the IMS exits in the IMS control region
• Define the z/OS log streams for use by ATF

Near Term History

The Tivoli OMEGAMON Monitor (TOM) allows Near Term History to be configured by product. Navigate from the View pulldown and select View History. Review the data tables shown in the KOBHISTB workspace and determine which ones to enable for history collection.

Select each table, define a collection interval, and distribute the collection request to the *MVS_IMSPLEX managed system list. This will cause the tables for each IMS system to be recorded on the specified interval.

Documentation

Knowledge Center replaces the book form of the documentation set. It is the new home for IBM product documentation.

It is recommended that users begin by reading the shared documentation.

http://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm

Read the Install or Upgrade Topics: "Getting Started", and "New in this Release" (September 2015)

Read Planning Topics: "Planning an upgrade or installation"

The following link will become active on September 4, 2015.

http://www-01.ibm.com/support/knowledgecenter/SSXS8U/com.ibm.omegamon_ims.doc_5.3.0/welcome.htm