Escolar Documentos
Profissional Documentos
Cultura Documentos
Table of Contents
Trouble 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
Illustration Index
Illustration 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 Tables
Table 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
Trouble Scenario
The 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:
Components
The following OMEGAMON components facilitate the display of data in the e3270ui:
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.
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.
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.
Configuration
The following minimal configuration considerations must be addressed to enable the e3270ui to
select and connect to a hub monitoring server.
HUBNAME=HUB1:CMS
HUBIPADDRESS=::ffff:9.44.44.22
HUBPORTNUMBER=55555
where
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).
HUBNAME
remote monitoring servers) be initialized and running before it is able to retrieve data.
Started and connectable via TCP/IP; that is, listening on the configured TCP/IP port
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.
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.
8
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.22
HUBPORTNUMBER=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:
Verify that rte.UKOBDATF profile members have specified the configured hub
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:
10
ip host name
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
started.
...
KO4SRV032
...
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.
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 online.
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
13
Product name
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:.cics_region_name
DB2plex:DB2plex:Plexview
db2_ID:lpar_smfid:DB2
XEDB2:lpar_smfid
IMSplex:IMSplex:Plexview
ims_ID:lpar_smfid:CONNECT
ims_ID:sysplex_name:SQGROUP
ims_ID:lpar_smfid:IMS
XEIMS:lpar_smfid:MVS
agent_jobname:lpar_smfid:KN3AGENT
tcpip_ID:lpar_smfid
vtam_ID:lpar_smfid
mq_ID:lpar_smfid:MQESA
agent_jobname:lpar_smfid:STORAGE
OMEGAMON XE on z/OS
SYSPLEX:SYSPLEX:PLEXVIEW
sysplex_name:MVS:SYSPLEX
sysplex_name:lpar_smfID:MVSSYS
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
Product name
*CPIRA_MGR
*GWIRA_MGR
*IBM_CICSplexes
*IBM_CICSplex
*MVS_CICSTG
*MVS_CICS
KCP_CICSplex_plex_name
*MVS_DB2
*MVS_IMSPLEX
KIP_ims_system_IMS
*OMEGAMONXE_MAINFRAME_NTWK_TCP
*OMEGAMONXE_MAINFRAME_NTWK_VTAM
*OMEGAMONXE_MAINFRAME_NTWK
mq_ID:lpar_smfid:MQESA
agent_jobname:lpar_smfid:STORAGE
OMEGAMON XE on z/OS
*MVS_SYSPLEX
*MVS_SYSTEM
Verify the existence of online OMEGAMON agents' Managed Systems: From the e3270ui
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
User Interface
workspace query timeout
QUERYTIMEOUT=
Default is 10 seconds.
DRA ping/health-check
(endpoint ping) timeout
PNG_TIMEOUT
Default is 2 seconds.
SO_TIMEOUT
Default is 15 seconds.
Registry refresh
(discovery data
request) time-out
DIS_TIMEOUT
Default is 2 seconds.
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.
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 misconfiguration or special site/environmental configuration requirements may lead to
operational issues. For example:
Operational issues may occur if a monitoring server is unable to bind to its configured
TCP/IP port number.
17