OMEGAMON for CICS (3270) upgrade considerations

You might want to consider a staged upgrade, which might include upgrading your OMEGAMON AI for CICS agent prior to upgrading your OMEGAMON for CICS (3270) component.

See Performing a staged upgrade for further information.

CICS-specific PARMGEN updates

The following CICS-specific PARMGEN updates have been made.

The KC5_WLM_BLOCKS configuration parameter has been changed from 236 blocks to 2048 blocks. This change also affects the Service Task Details situation.
The KC2_CCnn_CLASSIC_XMIT parameter is used to specify the XMIT number for the OMEGAMON for CICS (3270) address space starting in V5.3.0, you can minimize the JCL changes that are required to your CICS® regions. In earlier releases, you were required to add load libraries to your CICS regions and DD cards that controlled the monitoring of those regions (RKCPXMnn, RKC2XMnn and KC2GLBcc). V5.3.0 or later release implement support for a new CICS library definition.
The default started task prefix specified with the KC2_CCnn_CUA_STC parameter has been changed from CANS to IBM®.

Impact of near-term history on the persistent data store

In version 5.3.0 or later, OMEGAMON AI for CICS supports near term history for the enhanced 3270 user interface (3270UI) workspaces.

Near term history provides the capability to investigate problems that occurred in the recent past by using the enhanced 3270UI. Near term history provides intuitive access to historical data collected by both agents and IBM Tivoli Monitoring. Two types of historical workspace are provided: the historical summary and the historical snapshot.

This enhancement requires that the size of the persistent data store (PDS) on z/OS® or the number of persistent data stores be increased. See the historical data tables in this guide for more information about PDS sizing. Also, see Maintaining the persistent data store topic in the Reference section of the OMEGAMON shared documentation Version 6.3.0 Fix Pack 2.

Because of this change, the number of persistent data store historical files is increasing from three to six, and the group file count is decreasing from three to one.

This enhancement increased the count of persistent data store historical files from three to six to increase the amount of online viewing data because one file is always empty. The group file count was decreased from three to one as only one file is needed and there is no need to swap the group files.

For more information about using near term history, see the OMEGAMON shared documentation Version 6.3.0 Fix Pack 2: OMEGAMON Enhanced 3270 user interface.

Change to the definition of KOCOME00 in CICS

It is now recommended that you define KOCOME00 as follows:

DEFINE TRANSACTION(OMEG) PROGRAM(KOCOME00) GROUP(OMEGAMON)       
       TASKDATAKEY(CICS) TASKDATALOC(ANY)

This change of the TASKDATALOC to ANY avoids a potential situation where OMEGAMON® forces application GETMAINs to obtain storage below the line.

The sample provided in hilev.TKANSAM(KOCCSD) contains the currently recommended values.

Cross-memory considerations

The PARM=LXRES parameter is not coded on the EXEC statement. PARMGEN generates the PROC without this statement. If you are reusing an existing PROC, you should ensure this statement is removed.

Basic system configuration

Configuring OMEGAMON AI for CICS creates a set of address spaces independent of your existing CICS regions. To avoid installing processes that invade any CICS system, the basic system that you configure will not include the following functions:

Response time collection
Task history collection
Internal bottleneck collection
Interval record collection
Resource limiting

Dispatching priority

To ensure availability, you must run the OMEGAMON for CICS (3270) (required) and OMEGAMON AI for CICS (required) components and OMEGAMON AI for CICS agent with a z/OS system dispatching priority higher than any CICS region you are monitoring. OMEGAMON AI for CICS attempts to raise its dispatching priority higher than the target CICS region. If this is not possible, OMEGAMON AI for CICS produces the following message:

OC0830 OCRO CAUTION DISPATCHING PRIORITY GREATER THAN 239

Running OMEGAMON AI for CICS at a dispatching priority that is less than the target CICS region, especially while you are collecting response time data, can seriously degrade the overall performance of your system. Running OMEGAMON AI for CICS at a dispatching priority that is less than the target CICS region affects the 3270 interface.

Address spaces that are running OMEGAMON components must run at a higher priority service class than the address spaces and/or subsystems that are being monitored; this is a requirement for accurate reporting. These considerations apply to the OMEGAMON enhanced 3270 user interface as well as components that participate in the data collection. For example, Tivoli Enterprise Monitoring Server (hub or remote) and OMEGAMON Tivoli® Enterprise Management Agents.

What elements to upgrade

The following table shows the elements you can upgrade from prior versions of the OMEGAMON AI for CICS.

Table 1. Elements to upgrade from versions of OMEGAMON AI for CICS.
Element	Upgrade Considerations
OMEGAMON Subsystem	OMEGAMON Subsystem V7.0.0 is included in this product package. As other OMEGAMON products share these common components, you might need to coordinate the deployment of these common component upgrades. If you have upgraded from a previous version of the OMEGAMON Subsystem, and there are multiple LPARs, OMEGAMON Subsystem use the KCNDLINT V7.0.0 load module; the version included in this package. If you are using a global LINKLST, verify that KCNDLINT is V7.0.0.
Global Data Area	The Global Data Area contains the parameters that control the OMEGAMON AI for CICS monitoring options. The values in these parameters apply to all sessions that are monitoring the same CICS region. A default global data module is shipped with the product. You can install and migrate the current release level, or change the default settings.
SMF type 110 performance monitoring record collection	OMEGAMON AI for CICS V4.1.0 and higher does not require any monitoring control table (MCT) event monitoring points to enable task history or response time analysis to fully function. The MCT definitions are only required if you have user written reports that rely on the definitions.
OMEGAMON for CICS (3270) external security exit	If you are upgrading from a previous release and you have installed one of the OMEGAMON AI for CICS sample security exits, you must reinstall the exit using the updated samples.
CICS Region JCL	Support for the xKANMODR library was introduced in V3.2 (for DFHRPL usage). The new xKANMODR library contains only those modules which are loaded through the CICS DFHRPL DD statement. Concatenation of RKANMOD is no longer a CICS DFHRPL requirement. Instead you can choose to use the xKANMODR library, where x = T for SMP sharing RTEs; otherwise it is R. You can modify your CICS region JCL or use dynamic allocation to dynamically add the RKANMOD DD and CICS Dynamic program library concatenation to add the *KANMODR data set.

Historical reporting considerations

This table lists the considerations for the elements in historical reporting.

Table 2. Historical reporting considerations for OMEGAMON for CICS (3270).
Element	Considerations
Global Data Area	The Global Data Area lets you set options for the task history collector and the historical reporter.
Initialize OMEGAMON AI for CICS in the CICS region where historical data is to be collected.	To enable the task history collector, OMEGAMON AI for CICS must be initialized in the CICS region.
SMF Logging	You specify all the options for System Management Facilities (SMF) logging using the Global Data Area.

Command Security considerations

If you are submitting the upgrading job as part of upgrading your OMEGAMON for CICS (3270) component, you must rerun the KCIJPSEC job on the SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP menu. The KCIJPSEC job in the RTE's RKANSAMU data set picks up the new commands and security.

For more information about implementing security for OMEGAMON for CICS (3270), see Securing the OMEGAMON for CICS (3270).