Troubleshooting No-data Conditions on the OMEGAMON Enhanced 3270 User Interface

Document Version 1.0

September, 2012

Copyright International Business Machines Corporation 2012. All rights reserved.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

1

Table of ContentsTrouble Scenario.................................................................................................................4

Some background information..............................................................................................4

Components...........................................................................................................4

Communications and data retrieval............................................................................5

Configuration..........................................................................................................6

e3270ui log-on profile..........................................................................................6

Hub monitoring server settings.............................................................................6

Component initialization/startup and operation...........................................................6

Enhanced 3270 user interface (e3270ui, or TOM)....................................................6

E3270ui local registry..........................................................................................7

OMEGAMON XE for xxx on z/OS agent(s) and e3270ui DRAs.....................................7

OMEGAMON agent startup process........................................................................7

OMEGAMON agent recycle....................................................................................7

Hub Tivoli Enterprise Monitoring Server (hub monitoring server)...............................7

Troubleshooting no-data conditions.......................................................................................7

Possible causes for no data conditions........................................................................8

Troubleshooting the possible causes..........................................................................8

2

Illustration IndexIllustration 1: OMEGAMON configuration with enhanced 3270 interface components....................5

Illustration 2: No data in initial workspace..............................................................................8

Illustration 3: TEMS information panel with no settings specified...............................................9

Illustration 4: Current hub settings........................................................................................9

Illustration 5: Panel with corrected server name....................................................................10

Illustration 6: Sample Display Local Registry List of available data sources...............................11

Illustration 7: Sample Display Local Registry Managed Systems..............................................13

Illustration 8: Sample Display Local Registry Managed Systems Lists.......................................15

Index of TablesTable 1: Product Managed Systems Naming Conventions........................................................14

Table 2: Product Managed Systems Lists Naming Conventions.................................................15

Table 3: e3270ui Data Retrieval Request Time-out Parameters................................................16

3

Trouble ScenarioThe new OMEGAMON enhanced 3270 user interface (e3270ui) has been installed and configured. The e3270ui address space is started and users are able to log on, but the interface is displaying an empty workspace. For example:

What can I do to investigate the cause of this no-data condition?

Some background informationLet's begin with some background information to assist with identification of component areas where problems could arise and lead to an e3270ui no-data condition.

Components

The following OMEGAMON components facilitate the display of data in the e3270ui:

Tivoli OMEGAMON XE Agents (TEMAs). The OMEGAMON XE V5.1.0 agents (such as OMGAMON XE for CICS on z/OS) deliver capability that builds on e3270ui infrastructure to provide the OMEGAMON capability on the e3270ui.

Hub Tivoli Enterprise Monitoring Server (hub monitoring server). Monitoring servers are part of the Tivoli Management Services on z/OS infrastructure shared by the OMEGAMON XE agents. The e3270ui requires Tivoli Management Services on z/OS V6.2.3 (5698-A79) or later.The master monitoring server is called the hub monitoring server. The hub monitoring server acts as the focal point for data collection and distribution. It communicates with monitoring agents, with the OMEGAMON enhanced 3270 user interface, and with other Tivoli Management Services components. Monitoring servers that communicate only with the monitoring agents that report to them and with the hub monitoring server are referred to as remote monitoring servers.The hub monitoring server receives data requests from the e3270ui data retrieval agent and drives OMEGAMON agents for data collection and retrieval. The hub monitoring must be seeded with OMEGAMON XE V5.1.0 agent data.

OMEGAMON Enhanced 3270 User Interface (e3270ui or TOM) address space. The e3270ui address space, new in V5.1.0, provides data retrieval and user interface 3270 interaction functions. One or more e3270uis may be deployed in a given z/OS Sysplex.

OMEGAMON Enhanced 3270 user interface data retrieval agent (KOBAGENT or DRA). This new V5.1.0 component runs in any z/OS monitoring server or TEMA address space. The DRA receives data requests from the e3270ui and connects to the hub monitoring server to drive data collection by OMEGAMON V5.1.0 monitoring agents.

4

There must be at least one DRA deployed and running in the Sysplex where components of a given configuration (that is, hub or remote monitoring servers and agents) are running to enable e3270ui data retrieval and display. The e3270ui must also run in the same Sysplex as the DRA.

These components must be installed, configured, started, and running to enable successful rendering of OMEGAMON agent data on the e3270ui. The OMEGAMON agent configuration step of adding support for the V5.1.0 monitoring agent to the hub monitoring server must be performed to enable successful rendering of OMEGAMON agent data on the e3270ui.

Communications and data retrieval

The e3270ui employs WLM Services to discover DRAs that are running in its Sysplex. It uses TCP/IP services to communicate with DRAs.

The DRA uses TCP/IP services to communicate with the hub monitoring server. The DRA employs WLM Services to register/publish their existence within its Sysplex.

OMEGAMON XE monitoring agents employ TCP/IP or SNA services to communicate with monitoring servers. The monitoring agents register with the hub monitoring server as part of their startup process.

The e3270ui employs VTAM services to enable users to log on and communicate with the e3270ui. Users log on to the e3270ui via a VTAM Appl ID that is opened during e3270ui startup.

Illustration 1 is a graphical representation of an OMEGAMON configuration including deployment of the enhanced 3270 interface components: the e3270ui (TOM) address space and the DRA (KOBAGENT):

Illustration 1: OMEGAMON configuration with enhanced 3270 interface components

5

Configuration

The following minimal configuration considerations must be addressed to enable the e3270ui to select and connect to a hub monitoring server.

e3270ui log-on profile

One or more custom log-on profiles must be created. These profiles specify the settings for the hub monitoring server from which data is to be collected. The RKOBPROF DD statement in the e3270ui started task JCL procedure specifies the dataset that contain site and user log-on profile settings. Customized site or user profiles are stored as members of the rte.UKOBDATF dataset. When a user logs on, the e3270ui looks for a profile member named user_id (the ID of the logged on user) or CUASITE (a site-customized profile) to establish profile settings for the user session. Establish a site or user_id named log-on profile member by copying (and renaming) the product- provided profile member KOBCUA from the target thilev.TKOBDATF or runtime rte.TKOBDATF dataset to the runtime rte.UKOBDATF dataset.

Hub monitoring server settings

The settings for the hub monitoring server settings are specified in the log-on profile member. By default, the settings are provided as commented statements:

/* HUBNAME=HUBNAME /* HUBIPADDRESS=::ffff:HUBADDRESS /* HUBPORTNUMBER=HUBPORTNUMBER

Edit the profile member copy to specify the desired hub settings; locate, un-comment the following statements (i.e., remove the leading /* and move the setting statements to begin in column one). For example:

HUBNAME=HUB1:CMS HUBIPADDRESS=::ffff:9.44.44.22HUBPORTNUMBER=55555

whereHUBNAME is the configured name of the hub monitoring server. The monitoring

server may be configured to run on z/OS or a distributed system; e.g. Linux. Note: Often a hub monitoring server configured to run on distributed systems employs a mixed-case or all lower-case name. The value specified in the profile setting statements must match the case of the configured value.

HUBIPADDRESS is the TCP/IP address of the host system where the hub monitoring server runs. Note: The setting must be an TCP/IP address as shown in the preceding example; do not specify a TCP/IP Host name.

HUBPORTNUMBER is the TCP/IP port number of the configured hub monitoring server (by default, 1918).

Component initialization/startup and operation

Enhanced 3270 user interface (e3270ui, or TOM)

Although startup of the e3270ui address space is relatively fast, the e3270ui should probably be the last component in the startup sequence. This is because the interface requires that all other components in its environment (the OMEGAMON monitoring agents, the DRA and the hub and/or

6

remote monitoring servers) be initialized and running before it is able to retrieve data.

E3270ui local registry

The e3270ui startup process discovers registered DRAs and connects to related hub monitoring servers to establish a local registry of data source information, that is, managed systems names (MSNs) and managed system lists (MSLs). After startup, by default, the registry is refreshed on a five- minute interval.

OMEGAMON XE for xxx on z/OS agent(s) and e3270ui DRAs

The OMEGAMON XE v510 agent address spaces run both an instance of the product agent and also an instance of a e3270ui DRA. The DRA employs WLM services to publish its existence (register). The product agent registers with the hub monitoring server. These registration processes facilitate e3270ui discovery of OMEGAMON agents. Note that some OMEGAMON agents, such as OMEGAMON XE on z/OS, run under a remote z/OS monitoring server; the e3270ui DRA also runs under remote z/OS monitoring servers.

OMEGAMON agent startup process

There may be cases where an OMEGAMON agent startup process requires up to 10 minutes to complete startup and registration. As a result, the e3270ui will not be able to retrieve data for that agent during this period.

OMEGAMON agent recycle

Similar to the previous agent startup case, there may be cases where an OMEGAMON agent address space is terminated (e.g., LPAR shutdown); i.e. goes off-line and, in some cases the agent is performing the role of a proxy agent. As a result, the e3270ui will not be able to retrieve data for that agent until the off-line agent condition is resolved; for example, in a multi-LPAR configuration another agent will assume proxy-agent role.

Hub Tivoli Enterprise Monitoring Server (hub monitoring server)

To enable e3270ui data retrieval, the hub monitoring server must be:

Running Tivoli Management Services version 6.2.3 or later

Seeded with OMEGAMON for xxx on z/OS v510 agent data

Started and connectable via TCP/IP; that is, listening on the configured TCP/IP port

Have connected/on-line OMEGAMON for xxx on z/OS V5.1.0 agents

Troubleshooting no-data conditionsIllustration 2 is an example e3270ui workspace display depicting a case of no-data after initial log-on.

7

By default, Enterprise Summary (KOBSTART) is the initial e3270ui workspace. (The initial workspace parameter setting is specified in the log-on profile using the FIRSTWS parameter.)

Possible causes for no data conditions

The above KOBSTART example could occur as a result of a one or more possible conditions; for example:

1. No custom log-on profiles have been created or the hub monitoring server settings have not been configured in the e3270ui log-on profile.

2. The hub monitoring server settings in the e3270ui log-on profile do not match the hub monitoring server configured values.

3. There are no OMEGAMON XE for xxx on z/OS version 510 agents running in the same Sysplex where the e3270ui address space is running so there are no e3270ui DRAs registered.

4. The hub monitoring server is off-line; e.g., not started; has not completed startup; is not able to establish TCP/IP communications, etc.

5. The hub monitoring server has not been seeded with OMEGAMON for xxx on z/OS version 510 agent product provided seed information.

6. The OMEGAMON XE for xxx on z/OS agent is off-line; e.g., not started; has not completed startup; is not able to connect to the hub monitoring server, etc.

7. The e3270ui local registry has not yet obtained information about recently started OMEGAMON agents.

8. Data retrieval delays due to say network or system workload conditions leading to request time-outs and e3270ui no-data conditions.

Troubleshooting the possible causes

Investigation of the root cause can be started with capability provided by the e3270ui interface. The troubleshooting information provided in the following items corresponds to possible causes listed in the previous section.

1. Verify that the site and/or user_ID-named log-on profile members have been created.

a. From the e3270ui, select the View menu, then select 2 (Hub Information) to display e3270ui hub monitoring server settings.

Illustration 2: No data in initial workspace

8

If you see a panel similar to Illustration 3, indicating that no values are assigned, either no site and/or user ID-named log-on profile has been created, or the profile in effect for this session has not been customized to specify hub monitoring server settings. Complete steps a, b, and c to create a custom profile and/or specify the settings, as necessary.

If the panel indicates that the hub settings have been specified in the current log-on profile (see Illustration 4, for example), but the no-data condition persists, continue to step 2.

b. Ensure that a site (CUASITE) or user_ID-named data set member exists in rte.UKOBDATF.

If necessary, create the member, as described in the section on Configuration.

c. Ensure that the hub monitoring server settings in the profile for the current session have been customized to specify the required hub monitoring server configured values. For example:

HUBNAME=RTE1.CMS HUBIPADDRESS=::ffff:9.42.46.22HUBPORTNUMBER=21618

d. After you customize the log-on profile member, log-off the e3270ui and log-on to pickup the profile changes. If you repeat step a, you should see the hub settings you have specified:

2. Verify that rte.UKOBDATF profile members have specified the configured hub

Illustration 4: Current hub settings

Illustration 3: TEMS information panel with no settings specified

9

monitoring server settings and that these settings match the hub monitoring server configured values.

The settings shown in the Current Hub TEMS information panel shown in Illustration 4 indicate that a custom profile member has been created and customized. However, the e3270ui no-data condition persists. Inspect the profile in effect for the current session to determine if the specified settings match the configured hub monitoring server settings. For example, the panel in Illustration 4 shows that the server name is set to RTE1.CMS (with a period. However, the actual configured hub monitoring server name is RTE1:CMS with a colon.

Corrected the settings in the profile menu, then log off and back on to the e3270ui to pickup the profile changes. The Current Hub TEMS Information panel should now display the correct settings:

3. Verify that there are registered e3270ui DRAs online.

The e3270ui startup process discovers WLM-registered DRAs and connects to the DRAs to retrieve hub monitoring server information about OMEGAMON agent data sources. This information is stored in the e3270ui local registry. By default, the registry information is refreshed every five minutes.

If you have verified the existence of a custom profile, in which the hub monitoring settings are correctly specified, but the no-data condition persists, the next step is to very that there are registered DRAs.

In the e3270ui, select the View menu then select 3 (Data Retrieval Agents) from the dropdown menu. The KOBLOGON workspace is displayed, listing all available DRAs and their associated hubs.

Illustration 5: Panel with corrected server name

10

The three rows shown in Illustration 6 list the hub monitoring server RTE1:CMS. This is an indication that there are three registered DRAs running in the same Sysplex as the e3270ui address space. Assuming that there are no problems with agent data collection, the e3270ui should be able to connect to any one of these DRAs to retrieve OMEGAMON data from a V5.1.0 monitoring agent that is connected to the RTE1:CMS hub monitoring server.

If there are no DRAs registered for a given hub monitoring server, the KOBLOGON workspace will either be empty or, if there are multiple hub monitoring servers configured, it may contain DRA rows for other monitoring servers running in the Sysplex.

If the KOBLOGON list does not contain the hub monitoring server that is specified in the e3270ui log-on profile, there is a high probability that the OMEGAMON XE for xxx on z/OS agent(s) and or related monitoring server address space are off-line. There is also a possibility that the DRA (KOBAGENT) initialization has failed. The messages shown below, written to an OMEGAMON XE for xxx on z/OS agent (TEMS) and/or monitoring server (TEMS) address space log are an indication of normal DRA initialization/startup.

...0040-D51B5EB3:kobdrag,626,"kobipsrv") Port assigned is nnnnn

...(0005-D51B5EB3:kobdrag,648,"kobipsrv") Host Name is ip host name

...+0005 Host Address is ip host address

...(0009-D51B5EB3:kbbssge.c,52,"BSS1_GetEnv") KOB_HUB_NAME="configured TEMS name" ...(000B-D51B5EB3:kbbssge.c,52,"BSS1_GetEnv") KOB_HUB_IPADDR="TEMS IP address" ...(000D-D51B5EB3:kbbssge.c,52,"BSS1_GetEnv") KOB_HUB_IPPORT="TEMS IP Port" The absence of the above messages in the TEMS/TEMA log is an indication of an DRA startup failure. DRA startup failures may be caused by one or more of the following conditions:

a) A configuration issue; e.g. the TEMS or TEMA was upgraded but not reconfigured.b) The DRA was not able to establish a TCP/IP connection (e.g. bind failure). c) The DRA was not able to connect to the Hub TEMS.

Illustration 6: Sample Display Local Registry List of available data sources

11

4. Verify that the hub monitoring server is started, initialized, and prepared to receive data requests (that is, listening on the configured TCP/IP port).

The hub monitoring server may be running on either a z/OS LPAR or on a distributed system. Verify that the monitoring server has been started and has successfully completed initialization. The following monitoring server log messages are a good indication regarding the hub monitoring server operations health:...KDSMA001 Tivoli Enterprise Monitoring Server (TEMS) data collection server started....KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete....

If you cannot find these messages in the hub monitoring server log, examine the log for indications of potential problem. For example:

The monitoring server startup is in progress and initialization has not completed.

The monitoring server initialization failed; e.g., the monitoring server was not able to bind to its configured TCP/IP port; the monitoring server is not properly configured, etc.

There are unexpected error messages in the monitoring server log

Refer to the IBM Tivoli Monitoring Troubleshooting Guide for more information: http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/trouble/itm_troubleshoot.htm

5. Verify that version 5.1.0 product application support (seed data) has been added to the hub monitoring server

If this configuration step was not completed, the e3270ui may be missing data for one or more OMEGAMON products.

For a hub on z/OS, see Adding application support to a monitor server on z/OS :http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623fp1_zconfigtems74.htm?path=3_0_3_2_6_1#install_support

For a hub on a distributed operating system, see Installing application support on Tivoli Enterprise Monitoring Server: http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623FP1_install208.htm?path=3_0_3_0_6_3_5_2_0#agsupp_ms

Also refer to step 7, Review reasonableness of e3270ui local registry content.

6. Verify that the OMEGAMON XE for xxx on z/OS monitoring agent is started and on-line.

There are multiple methods that can be employed to investigate the online status of an OMEGAMON agent. Start by examining the content of the local registry.

a. From the e3270ui View menu, select 4 (Managed Systems). The resulting display should be similar to the example shown below:

12

The various OMEGAMON monitoring agents employ unique conventions to identify agents and managed systems. For example, in the sample display, rows that display names ending in :MVSSYS and :SYSPLEX along with MS Online Status value of Y are an indication that there are OMEGAMON XE on z/OS agents on line. As a result, the e3270ui should be able to retrieve data for that product. The following table lists the conventions used by individual OMEGAMON products to compose managed system names.

Illustration 7: Sample Display Local Registry Managed Systems

13

Product name Managed System naming conventions

OMEGAMON XE for CICS on z/OS cics_region_name:lpar_smfID:CPIRAcics_region_name:lpar_smfID:CEIRAcics_tg_ID:lpar_smfID:CICSTGcics_tg_ID:lpar_smfid:GWIRAcicsplex_name::CICSPLEXlpar_smfid:.cics_region_name

OMEGAMON XE for DB2 PE DB2plex:DB2plex:Plexviewdb2_ID:lpar_smfid:DB2 XEDB2:lpar_smfid

OMEGAMON XE for IMS on z/OS IMSplex:IMSplex:Plexview ims_ID:lpar_smfid:CONNECTims_ID:sysplex_name:SQGROUPims_ID:lpar_smfid:IMSXEIMS:lpar_smfid:MVS

OMEGAMON XE for Mainframe Networks agent_jobname:lpar_smfid:KN3AGENT tcpip_ID:lpar_smfid vtam_ID:lpar_smfid

OMEGAMON XE for Messaging mq_ID:lpar_smfid:MQESA

OMEGAMON XE for Storage on z/OS agent_jobname:lpar_smfid:STORAGE

OMEGAMON XE on z/OS SYSPLEX:SYSPLEX:PLEXVIEWsysplex_name:MVS:SYSPLEXsysplex_name:lpar_smfID:MVSSYS

Table 1: Product Managed Systems Naming Conventions

Again, if examination of the KOBMSNS workspace content indicates no online agents for a given product, the agent address space should be examined to verify that that it has been started and it has successfully initialized. In some cases, it may be necessary to verify that the corresponding monitored systems or subsystems (e.g., CICS regions) are also running.

7. Review the reasonableness of e3270ui local registry content. The e3270ui registry must have accurate information about the configuration of the environment to enable the composition and routing of data queries to appropriate OMEGAMON agent Managed Systems. The registry is first populated during the e3270ui address space initialization process and thereafter, by default, at five-minute intervals.Given startup considerations for OMEGAMON monitoring components and monitored systems/subsystem, it is possible for the e3270ui local registry content to take up to 10 minutes to be stabilized, assuming a fairly stable configuration.Having allowed for these startup considerations, the e3270ui local registry can be examined for content reasonableness. Use the e3270ui menu bar options to examine the local registry. Following are some things to look for:

Verify the existence of online registered e3270ui data retrieval agents: Select the View menu, then select 3 (Data Retrieval Agents) from the dropdown menu. The e3270ui workspace KOBLOGON must contain a minimum of one DRA row to enable e3270ui data retrieval.

Verify the existence of OMEGAMON agent's Managed Systems Lists: From the e3270ui View menu, select 5 (Managed Systems Lists). You should see a list of online managed systems lists:

14

The rendered e3270ui workspace, KOBMSLS, should list rows with managed system names such as those provided in the following table:

Product name Managed system naming conventions

OMEGAMON XE for CICS on z/OS *CPIRA_MGR*GWIRA_MGR *IBM_CICSplexes *IBM_CICSplex *MVS_CICSTG *MVS_CICS KCP_CICSplex_plex_name

OMEGAMON XE for DB2 PE *MVS_DB2

OMEGAMON XE for IMS on z/OS *MVS_IMSPLEXKIP_ims_system_IMS

OMEGAMON XE for Mainframe Networks *OMEGAMONXE_MAINFRAME_NTWK_TCP *OMEGAMONXE_MAINFRAME_NTWK_VTAM*OMEGAMONXE_MAINFRAME_NTWK

OMEGAMON XE for Messaging mq_ID:lpar_smfid:MQESA

OMEGAMON XE for Storage on z/OS agent_jobname:lpar_smfid:STORAGE

OMEGAMON XE on z/OS *MVS_SYSPLEX *MVS_SYSTEM

Table 2: Product Managed Systems Lists Naming Conventions

Verify the existence of online OMEGAMON agents' Managed Systems: From the e3270ui

Illustration 8: Sample Display Local Registry Managed Systems Lists

15

View, select 4, Managed Systems. The rendered e3270ui workspace, KOBMSNS, should list rows with Managed System names such as those described in step 6, Verify that the OMEGAMON XE for xxx on z/OS agent is started and on-line....

8. For data retrieval delays leading to time-out conditions, review the e3270ui log file.

Logs are written to the address space SYSPRINT DD statement. By default, the e3270ui is configured with the request time-out parameters shown in the following table:

Parameter description Parameter name Defaults and overrides

User Interface workspace query time-out

QUERYTIMEOUT= Default is 10 seconds. Note: Some e3270ui workspace queries are delivered with an time-out override; e.g., where the composition of data requests anticipates an elongated response.

DRA ping/health-check (endpoint ping) time-out

PNG_TIMEOUT Default is 2 seconds.

DRA data request (socket) time-out

SO_TIMEOUT Default is 15 seconds.

Registry refresh (discovery data request) time-out

DIS_TIMEOUT Default is 2 seconds.

Table 3: e3270ui Data Retrieval Request Time-out Parameters

These parameter defaults have been established for reasonable/normal operational conditions. There may be unique operational conditions where the defaults are not optimal. In that case, the defaults can be modified by way of creating customized e3270ui workspaces and/or specifying parameter overrides in the e3270ui environment parameters file (rte.RKANPARU(KOBENV) referenced by the e3270ui address space RKANPAR DD statement. Elongated response times when interacting with the e3270ui may be a symptom of time-out conditions. For example, if during e3270ui log-on the initial (KOBSTART) workspace takes a significant amount of time (e.g. more than a few seconds) to render and/or if the workspace is rendered with partial or no data, this may be a symptom of delay/time-out conditions. Note: The "KOBCM0010E: Conduit Manager Recv Error..." message is written to the e3270ui SYSPRINT log files when request time-outs occur; following is a sample message: 2012/08/22 14:58:35 00000048_02E8A810+ KOBCM0010E: conduit manager Recv Error, rc = -1, microseconds = 60971935 The items listed below identify most common causes for delay/time-out conditions. Given that investigation of these may be complex, there is no attempt to provide comprehensive information for methods of investigation. The information provided may serve as hints for further investigation. The hub monitoring server is running under degraded system conditions (e.g., heavy system workload; under-capacity system) and is being delayed when attempting to service e3270ui data requests. In this case, the availability and priority of the system resources provided to the hub monitoring server should be examined.

16

The OMEGAMON for xxx on z/OS agent is running under degraded system conditions (e.g., heavy system workload; under-capacity system) and is being delayed when attempting to service e3270ui data requests. In this case, the availability and priority of the system resources provided to the agent should be examined. Data requests submitted from the e3270ui to a given DRA, via a TCP/IP conduit, are being impacted by degraded network conditions. In this case, the availability, priority, and configuration of network resources and paths associated with communications between the e3270ui and the hub monitoring server and OMEGAMON agents should be examined. An OMEGAMON component (monitoring server or agent) that played a role in a given data request path has gone off-line; e.g., the LPAR was terminated, or the address space was terminated. In this case, information provided above in the step Review reasonableness of e3270ui local registry content, may be employed to investigate the status of OMEGAMON components (e.g., Managed Systems: on-line/off-line). The Hub and or a remote monitoring server is experiencing operational issues and as a result, is being delayed when attempting to service e3270ui data requests. Note that a mis-configuration or special site/environmental configuration requirements may lead to operational issues. For example:

Operational issues may arise if a monitoring server running on z/OS is experiencing problems writing to its Historical Persistent Datastore files. Operational issues may occur if a monitoring server is unable to bind to its configured TCP/IP port number.

17

Trouble ScenarioSome background informationComponentsCommunications and data retrievalConfiguratione3270ui log-on profileHub monitoring server settings

Component initialization/startup and operationEnhanced 3270 user interface (e3270ui, or TOM)E3270ui local registryOMEGAMON XE for xxx on z/OS agent(s) and e3270ui DRAsOMEGAMON agent startup processOMEGAMON agent recycleHub Tivoli Enterprise Monitoring Server (hub monitoring server)

Troubleshooting no-data conditionsPossible causes for no data conditionsTroubleshooting the possible causes