Monitoring a single sysplex

When the enhanced 3270UI is running in single-sysplex mode, you can view data only for the managed systems that run in sysplex member LPARs that correspond to the sysplex where the enhanced 3270UI started task is running.

This capability enables a multi-client site that uses a single or shared hub monitoring server to run multiple enhanced 3270UI instances, each running in a unique sysplex and having a reduced (single sysplex) data scope.

Considerations for single-syplex mode

Review the following requirements and limitations when considering single-syplex operational mode deployment:

The Data Retrieval Agent (DRA) is a component used by the enhanced 3270UI to communicate with a hub monitoring server to retrieve data provided by OMEGAMON agents. Single-sysplex mode requires that a site configure and run at least one DRA in each sysplex member LPAR where OMEGAMON tasks are run. OMEGAMON is typically configured this way; however, it is possible to disable DRAs through configuration and filters. In single-sysplex mode, DRAs help the enhanced 3270UI uniquely identify sysplex member LPARs.
Single-sysplex mode should not be used in the case where a site is running CICSplexes that are defined to span across multiple sysplexes. If a single-sysplex enhanced 3270UI is deployed in such a configuration, data attributes for certain OMEGAMON AI for CICS capabilities might be incorrect (for example, Service Level Analysis and CICSplex overview information).

APARs for single-sysplex mode support

Single-sysplex mode support is delivered in the maintenance stream for existing OMEGAMON product components. You must apply the respective PTF for each of your installed products in order to use single-sysplex support for any of your products.

The following table lists the APARs that provide enhanced 3270UI single-sysplex mode support:

Table 1. APARs for single-sysplex support
Product	Version	APAR
OMEGAMON Base	7.5.0	OA68871
PARMGEN/Configuration Manager	3.1.0	OA69083
IBM Z® OMEGAMON AI for Db2	6.1.0	PH69153
IBM® OMEGAMON for IMS on z/OS	5.5.0	OA69233
IBM Z OMEGAMON AI for JVM	6.1.0	OA69153
IBM OMEGAMON for Messaging on z/OS	7.5.0	OA68731, OA68732
IBM Z OMEGAMON AI for z/OS	6.1.0	OA68914

Note: In a test system, the minimum maintenance required is APAR OA68871 (OMEGAMON Base 7.5.0); however, for deployment in a production system, all maintenance must be installed for effective use of single-sysplex mode.

Starting the e3270UI in single-sysplex mode

After the required maintenance has been installed, the enhanced 3270UI can be deployed in single-sysplex mode using a unique instance of its started task JCL. The enhanced 3270UI started task JCL provides the MODE parameter, which has the default value CUA. This parameter value must be changed from CUA to SYSPLEX to start the enhanced 3270UI instance in single-sysplex mode. You can use configuration parameter KOB_TOM_MODE to control this setting. When the procedure is started with the parameter set to SYSPLEX, the following message is issued in the console:

OMV020I e3270UI is running in SYSPLEX Mode

For more information, see Enabling single-sysplex mode.

Single-sysplex mode user session considerations

A single-sysplex mode enhanced 3270UI user session is very similar to the default non-single-sysplex mode (MODE=CUA) session. The following are some notable differences:

In single-sysplex mode, the viewable data scope in the enhanced 3270UI is limited to data associated with tasks or subsystems running in the corresponding sysplex member LPARs.
In single-sysplex mode, the user session initial (first) landing workspace displays the corresponding sysplex name in the upper right corner in the SYSPLEX field:
Figure 1. SYSPLEX field in single-sysplex mode