You are on page 1of 17

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

..............................................................................................5 Configuration...............................................................................................................................................................6 Hub monitoring server settings.........Table of Contents Trouble Scenario...............................................................................................................4 Some background information.....4 Components......................................................................................................................................................................7 OMEGAMON XE for xxx on z/OS agent(s) and e3270ui DRAs...................................................................................................8 2 ..................................................................................................7 OMEGAMON agent recycle...........................7 Troubleshooting no-data conditions.......................................................7 Hub Tivoli Enterprise Monitoring Server (hub monitoring server)...........................................................7 Possible causes for no data conditions..................................................................................................................................4 Communications and data retrieval...8 Troubleshooting the possible causes.........................................................................6 Enhanced 3270 user interface (e3270ui...........7 OMEGAMON agent startup process.. or TOM).................................6 Component initialization/startup and operation.......................................................................................................6 e3270ui log-on profile............................................6 E3270ui local registry..........................................

...................................9 Illustration 4: Current hub settings............................5 Illustration 2: No data in initial workspace.....................................................8 Illustration 3: TEMS information panel with no settings specified.................................................................................13 Illustration 8: Sample Display Local Registry Managed Systems Lists...............................................15 Index of Tables Table 1: Product Managed Systems Naming Conventions.............................................................16 3 ...........................................Illustration Index Illustration 1: OMEGAMON configuration with enhanced 3270 interface components..11 Illustration 7: Sample Display Local Registry Managed Systems..............................9 Illustration 5: Panel with corrected server name.........................10 Illustration 6: Sample Display Local Registry List of available data sources.................................................................14 Table 2: Product Managed Systems Lists Naming Conventions....................................................15 Table 3: e3270ui Data Retrieval Request Time-out Parameters.................................................

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. It communicates with monitoring agents. with the OMEGAMON enhanced 3270 user interface. The e3270ui address space.1.0.1. The master monitoring server is called the hub monitoring server. The hub monitoring server acts as the focal point for data collection and distribution. new in V5. Components The following OMEGAMON components facilitate the display of data in the e3270ui: • • Tivoli® OMEGAMON XE Agents (TEMAs).2.0 monitoring agents.0 component runs in any z/OS monitoring server or TEMA address space. • OMEGAMON Enhanced 3270 user interface data retrieval agent (KOBAGENT or DRA).0 agent data. but the interface is displaying an empty workspace. One or more e3270uis may be deployed in a given z/OS Sysplex. Monitoring servers are part of the Tivoli Management Services on z/OS infrastructure shared by the OMEGAMON XE agents.1. provides data retrieval and user interface 3270 interaction functions.1.3 (5698-A79) or later.1. The e3270ui address space is started and users are able to log on. Hub Tivoli Enterprise Monitoring Server (hub monitoring server). The hub monitoring must be seeded with OMEGAMON XE V5. 4 . For example: What can I do to investigate the cause of this no-data condition? Some background information Let'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.Trouble Scenario The new OMEGAMON® enhanced 3270 user interface (e3270ui) has been installed and configured. • OMEGAMON Enhanced 3270 User Interface (e3270ui or TOM) address space. The DRA receives data requests from the e3270ui and connects to the hub monitoring server to drive data collection by OMEGAMON V5. The hub monitoring server receives data requests from the e3270ui data retrieval agent and drives OMEGAMON agents for data collection and retrieval. The e3270ui requires Tivoli Management Services on z/OS V6. and with other Tivoli Management Services components. The OMEGAMON XE V5. This new V5. 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 monitoring agents register with the hub monitoring server as part of their startup process. • The DRA uses TCP/IP services to communicate with the hub monitoring server. hub or remote monitoring servers and agents) are running to enable e3270ui data retrieval and display.0 monitoring agent to the hub monitoring server must be performed to enable successful rendering of OMEGAMON agent data on the e3270ui. The e3270ui employs VTAM® services to enable users to log on and communicate with the e3270ui. The e3270ui must also run in the same Sysplex as the DRA. It uses TCP/IP services to communicate with DRAs. • 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 . These components must be installed. The DRA employs WLM Services to register/publish their existence within its Sysplex.1. Users log on to the e3270ui via a VTAM Appl ID that is opened during e3270ui startup. started.There must be at least one DRA deployed and running in the Sysplex where components of a given configuration (that is. The OMEGAMON agent configuration step of adding support for the V5. configured. and running to enable successful rendering of OMEGAMON agent data on the e3270ui. • OMEGAMON XE monitoring agents employ TCP/IP or SNA services to communicate with monitoring servers. Communications and data retrieval • The e3270ui employs WLM Services to discover DRAs that are running in its Sysplex.

The value specified in the profile setting statements must match the case of the configured value.22 HUBPORTNUMBER=55555 where is the configured name of the hub monitoring server.e.UKOBDATF dataset. Note: The setting must be an TCP/IP address as shown in the preceding example. Linux. These profiles specify the settings for the hub monitoring server from which data is to be collected.TKOBDATF or runtime rte. locate. e. 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.g.UKOBDATF dataset. HUBPORTNUMBER is the TCP/IP port number of the configured hub monitoring server (by default. By default. HUBIPADDRESS is the TCP/IP address of the host system where the hub monitoring server runs. The RKOBPROF DD statement in the e3270ui started task JCL procedure specifies the dataset that contain site and user log-on profile settings.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. the e3270ui should probably be the last component in the startup sequence. When a user logs on. HUBNAME Component initialization/startup and operation Enhanced 3270 user interface (e3270ui.44. Note: Often a hub monitoring server configured to run on distributed systems employs a mixed-case or all lower-case name. 1918).44. 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. the DRA and the hub and/or 6 . Customized site or user profiles are stored as members of the rte. un-comment the following statements (i. This is because the interface requires that all other components in its environment (the OMEGAMON monitoring agents.. The monitoring server may be configured to run on z/OS or a distributed system. For example: HUBNAME=HUB1:CMS HUBIPADDRESS=::ffff:9. Establish a site or user_id named log-on profile member by copying (and renaming) the productprovided profile member KOBCUA from the target thilev. do not specify a TCP/IP Host name.TKOBDATF dataset to the runtime rte. remove the leading /* and move the setting statements to begin in column one). or TOM) Although startup of the e3270ui address space is relatively fast. Hub monitoring server settings The settings for the hub monitoring server settings are specified in the log-on profile member.

that is. The product agent registers with the hub monitoring server. listening on the configured TCP/IP port • Have connected/on-line OMEGAMON for xxx on z/OS V5.3 or later • Seeded with OMEGAMON for xxx on z/OS v510 agent data • Started and connectable via TCP/IP. The DRA employs WLM services to publish its existence (register).minute interval.. Hub Tivoli Enterprise Monitoring Server (hub monitoring server) To enable e3270ui data retrieval.1. the registry is refreshed on a five.e. OMEGAMON agent startup process There may be cases where an OMEGAMON agent startup process requires up to 10 minutes to complete startup and registration. 7 . by default. As a result. Note that some OMEGAMON agents.remote monitoring servers) be initialized and running before it is able to retrieve data.g. in a multi-LPAR configuration another agent will assume “proxy-agent” role. These registration processes facilitate e3270ui discovery of OMEGAMON agents. OMEGAMON agent recycle Similar to the previous agent startup case. in some cases the agent is performing the role of a “proxy agent”. run under a remote z/OS monitoring server. managed systems names (MSNs) and managed system lists (MSLs). the e3270ui will not be able to retrieve data for that agent during this period. 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. such as OMEGAMON XE on z/OS. the e3270ui DRA also runs under remote z/OS monitoring servers. LPAR shutdown). the e3270ui will not be able to retrieve data for that agent until the off-line agent condition is resolved. for example. that is. After startup. 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 hub monitoring server must be: • Running Tivoli Management Services version 6.2.0 agents Troubleshooting no-data conditions Illustration 2 is an example e3270ui workspace display depicting a case of no-data after initial logon. As a result. i. there may be cases where an OMEGAMON agent address space is terminated (e. goes off-line and.

not started. 8 . 8.Illustration 2: No data in initial workspace By default. 4. The hub monitoring server is off-line. a. From the e3270ui.g. Enterprise Summary (KOBSTART) is the initial e3270ui workspace. No custom log-on profiles have been created or the hub monitoring server settings have not been configured in the e3270ui log-on profile. The OMEGAMON XE for xxx on z/OS agent is off-line. The hub monitoring server settings in the e3270ui log-on profile do not match the hub monitoring server configured values. 1. (The initial workspace parameter setting is specified in the log-on profile using the FIRSTWS parameter. etc. The troubleshooting information provided in the following items corresponds to possible causes listed in the previous section. not started. Verify that the site and/or user_ID-named log-on profile members have been created. is not able to connect to the hub monitoring server. 5.) Possible causes for no data conditions The above KOBSTART example could occur as a result of a one or more possible conditions. e. has not completed startup. The e3270ui local registry has not yet obtained information about recently started OMEGAMON agents. has not completed startup. then select 2 (Hub Information) to display e3270ui hub monitoring server settings.g. e. for example: 1. etc.. 2. Data retrieval delays due to say network or system workload conditions leading to request time-outs and e3270ui no-data conditions. select the View menu. is not able to establish TCP/IP communications. 3. Troubleshooting the possible causes Investigation of the root cause can be started with capability provided by the e3270ui interface. The hub monitoring server has not been seeded with OMEGAMON for xxx on z/OS version 510 agent product provided seed information.. 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. 7. 6.

b.CMS HUBIPADDRESS=::ffff:9. b. for example). as necessary. For example: HUBNAME=RTE1. Ensure that a site (CUASITE) or user_ID-named data set member exists in rte.42. but the no-data condition persists.46. log-off the e3270ui and log-on to pickup the profile changes. Complete steps a.22 HUBPORTNUMBER=21618 d. continue to step 2. If the panel indicates that the hub settings have been specified in the current log-on profile (see Illustration 4. you should see the hub settings you have specified: Illustration 4: Current hub settings 2. either no site and/or user ID-named log-on profile has been created. If necessary.UKOBDATF. If you repeat step a. 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. and c to create a custom profile and/or specify the settings. indicating that no values are assigned.UKOBDATF profile members have specified the configured hub 9 . After you customize the log-on profile member. as described in the section on Configuration. create the member.Illustration 3: TEMS information panel with no settings specified If you see a panel similar to Illustration 3. Verify that rte. or the profile in effect for this session has not been customized to specify hub monitoring server settings. c.

then log off and back on to the e3270ui to pickup the profile changes. The KOBLOGON workspace is displayed. listing all available DRAs and their associated hubs. By default. 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.monitoring server settings and that these settings match the hub monitoring server configured values.CMS (with a period. In the e3270ui. For example. the panel in Illustration 4 shows that the server name is set to RTE1. in which the hub monitoring settings are correctly specified. If you have verified the existence of a custom profile. However. the e3270ui no-data condition persists. the actual configured hub monitoring server name is “RTE1:CMS” with a colon. The Current Hub TEMS Information panel should now display the correct settings: Illustration 5: Panel with corrected server name 3. 10 . The e3270ui startup process discovers WLM-registered DRAs and connects to the DRAs to retrieve hub monitoring server information about OMEGAMON agent data sources. However. Inspect the profile in effect for the current session to determine if the specified settings match the configured hub monitoring server settings. the next step is to very that there are registered DRAs. the registry information is refreshed every five minutes. This information is stored in the e3270ui local registry. Corrected the settings in the profile menu. Verify that there are registered e3270ui DRAs online. select the View menu then select 3 (Data Retrieval Agents) from the dropdown menu. but the no-data condition persists.

.0040-D51B5EB3:kobdrag.52."BSS1_GetEnv") KOB_HUB_NAME="configured TEMS name" .+0005 ip host name Host Address is ip host address . c) The DRA was not able to connect to the Hub TEMS.(000D-D51B5EB3:kbbssge.. Assuming that there are no problems with agent data collection. the KOBLOGON workspace will either be empty or. DRA startup failures may be caused by one or more of the following conditions: a) A configuration issue. b) The DRA was not able to establish a TCP/IP connection (e.. 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.. If there are no DRAs registered for a given hub monitoring server.Illustration 6: Sample Display Local Registry List of available data sources The three rows shown in Illustration 6 list the hub monitoring server RTE1:CMS.52. This is an indication that there are three registered DRAs running in the same Sysplex as the e3270ui address space. the e3270ui should be able to connect to any one of these DRAs to retrieve OMEGAMON data from a V5.626. The messages shown below.c. if there are multiple hub monitoring servers configured.52. There is also a possibility that the DRA (KOBAGENT) initialization has failed.."BSS1_GetEnv") KOB_HUB_IPADDR="TEMS IP address" ."kobipsrv") Host Name is .. bind failure). 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.. If the KOBLOGON list does not contain the hub monitoring server that is specified in the e3270ui log-on profile.g. ..g.. it may contain DRA rows for other monitoring servers running in the Sysplex.648."kobipsrv") Port assigned is nnnnn .c. 11 .(0009-D51B5EB3:kbbssge.1."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....(000B-D51B5EB3:kbbssge.(0005-D51B5EB3:kobdrag.0 monitoring agent that is connected to the RTE1:CMS hub monitoring server. e. the TEMS or TEMA was upgraded but not reconfigured.c.

the monitoring server is not properly configured. the monitoring server was not able to bind to its configured TCP/IP port. . select 4 (Managed Systems). KDSMA001 started.3fp1/trouble/itm _troubleshoot.doc_6. Start by examining the content of the local registry.2...ibm. Tivoli Enterprise Monitoring Server (TEMS) data collection server .itm. see “Installing application support on Tivoli Enterprise Monitoring Server”: http://pic. The resulting display should be similar to the example shown below: 12 .. Verify that version 5.dhe. and prepared to receive data requests (that is.g.dhe. There are multiple methods that can be employed to investigate the online status of an OMEGAMON agent. • There are unexpected error messages in the monitoring server log Refer to the IBM Tivoli Monitoring Troubleshooting Guide for more information: http://pic. 6.2. e.htm 5.ibm.2...com/infocenter/tivihelp/v15r1/topic/com.. the e3270ui may be missing data for one or more OMEGAMON products.doc_6.ibm.dhe. a.0 product application support (seed data) has been added to the hub monitoring server If this configuration step was not completed. initialized. see “Adding application support to a monitor server on z/OS”: http://pic.com/infocenter/tivihelp/v15r1/topic/com. For a hub on z/OS. From the e3270ui View menu.htm?path=3_0_3_0_6_3_5_2_0#agsupp_ms Also refer to step 7.ibm.1.doc_6. Verify that the OMEGAMON XE for xxx on z/OS monitoring agent is started and online.itm. The following monitoring server log messages are a good indication regarding the hub monitoring server operations health: .itm.ibm. Verify that the monitoring server has been started and has successfully completed initialization. If you cannot find these messages in the hub monitoring server log..ibm.4.com/infocenter/tivihelp/v15r1/topic/com.3fp1/itm623fp1_ zconfigtems74.htm?path=3_0_3_2_6_1#install_support For a hub on a distributed operating system. For example: • The monitoring server startup is in progress and initialization has not completed.3fp1/itm623FP1_ install208. Verify that the hub monitoring server is started. • The monitoring server initialization failed. The hub monitoring server may be running on either a z/OS LPAR or on a distributed system. examine the log for indications of potential problem. “Review reasonableness of e3270ui local registry content”. etc. listening on the configured TCP/IP port). KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.

in the sample display. As a result. The following table lists the conventions used by individual OMEGAMON products to compose managed system names. 13 . 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.Illustration 7: Sample Display Local Registry Managed Systems The various OMEGAMON monitoring agents employ unique conventions to identify agents and managed systems. For example. the e3270ui should be able to retrieve data for that product.

select 5 (Managed Systems Lists).Product name Managed System naming conventions OMEGAMON XE for CICS on z/OS cics_region_name:lpar_smfID:CPIRA cics_region_name:lpar_smfID:CEIRA cics_tg_ID:lpar_smfID:CICSTG cics_tg_ID:lpar_smfid:GWIRA cicsplex_name::CICSPLEX lpar_smfid:. Review the reasonableness of e3270ui local registry content. at five-minute intervals. Use the e3270ui menu bar options to examine the local registry. Having allowed for these startup considerations. In some cases. if examination of the KOBMSNS workspace content indicates no online agents for a given product.g. Given startup considerations for OMEGAMON monitoring components and monitored systems/subsystem. ◦ Verify the existence of OMEGAMON agent's Managed Systems Lists: From the e3270ui View menu.. then select 3 (Data Retrieval Agents) from the dropdown menu. by default. the agent address space should be examined to verify that that it has been started and it has successfully initialized. The e3270ui workspace KOBLOGON must contain a minimum of one DRA row to enable e3270ui data retrieval. it may be necessary to verify that the corresponding monitored systems or subsystems (e. You should see a list of online managed systems lists: 14 . it is possible for the e3270ui local registry content to take up to 10 minutes to be stabilized. the e3270ui local registry can be examined for content reasonableness. assuming a fairly stable configuration. Following are some things to look for: ◦ Verify the existence of online registered e3270ui data retrieval agents: Select the View menu. 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. CICS regions) are also running. 7.cics_region_name OMEGAMON XE for DB2 PE DB2plex:DB2plex:Plexview db2_ID:lpar_smfid:DB2 XEDB2:lpar_smfid OMEGAMON XE for IMS on z/OS IMSplex:IMSplex:Plexview ims_ID:lpar_smfid:CONNECT ims_ID:sysplex_name:SQGROUP ims_ID:lpar_smfid:IMS XEIMS: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:PLEXVIEW sysplex_name:MVS:SYSPLEX sysplex_name:lpar_smfID:MVSSYS Table 1: Product Managed Systems Naming Conventions Again.

Illustration 8: Sample Display Local Registry Managed Systems Lists 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_IMSPLEX KIP_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 15 .

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 timeout QUERYTIMEOUT= Default is 10 seconds. For example. “Verify that the OMEGAMON XE for xxx on z/OS agent is started and on-line. heavy system workload.View. this may be a symptom of delay/time-out conditions. review the e3270ui log file. more than a few seconds) to render and/or if the workspace is rendered with partial or no data. By default. rc = -1. Table 3: e3270ui Data Retrieval Request Time-out Parameters These parameter defaults have been established for reasonable/normal operational conditions. where the composition of data requests anticipates an elongated response. there is no attempt to provide comprehensive information for methods of investigation. 8. Elongated response times when interacting with the e3270ui may be a symptom of time-out conditions. DRA ping/health-check (endpoint ping) timeout PNG_TIMEOUT Default is 2 seconds. Given that investigation of these may be complex. The information provided may serve as hints for further investigation. DRA data request (socket) time-out SO_TIMEOUT Default is 15 seconds.. Managed Systems..." message is written to the e3270ui SYSPRINT log files when request time-outs occur. KOBMSNS. under-capacity system) and is being delayed when attempting to service e3270ui data requests. microseconds = 60971935 The items listed below identify most common causes for delay/time-out conditions. following is a sample message: 2012/08/22 14:58:35 00000048_02E8A810+ KOBCM0010E: conduit manager Recv Error. For data retrieval delays leading to time-out conditions.g. 16 . 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. There may be unique operational conditions where the defaults are not optimal. the availability and priority of the system resources provided to the hub monitoring server should be examined. The rendered e3270ui workspace. select 4.. Logs are written to the address space SYSPRINT DD statement.”.g. if during e3270ui log-on the initial (KOBSTART) workspace takes a significant amount of time (e. • The hub monitoring server is running under degraded system conditions (e.. e. DIS_TIMEOUT Default is 2 seconds. In this case.RKANPARU(KOBENV) referenced by the e3270ui address space RKANPAR DD statement. should list rows with Managed System names such as those described in step 6.g. Registry refresh (discovery data request) time-out Note: Some e3270ui workspace queries are delivered with an time-out override. Note: The "KOBCM0010E: Conduit Manager Recv Error..

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