IBM Support

Missing Sysplex data in the OMEGAMON XE ON Z/OS product

Troubleshooting


Problem

No sysplex data available in the Enhanced 3270UI or Tivoli Enterprise Portal.

Symptom

In the Enhanced 3270UI, workspace KOBSTART displays the following message:
"Sysplex Data Unavailable: Enter 'ZOSLPARS' for LPAR Data"

In the Tivoli Enterprise Portal, the sysplex level reports are all disabled and not selectable.

Cause

One of the main causes of this problem is that no sysplex Plexview collector is assigned, or the Plexview collector is not able to communicate with the HUB Tivoli Enterprise Monitoring Server.  Another possible cause is that no sysplex proxy collector is assigned.

Diagnosing The Problem

Log on to the Enhanced 3270UI and select Tools, H Current Hub Information. On the KOBHUBS workspace, place a T next to the hub item and hit enter. Scroll down to the z/OS Origin Nodes.  There should be one entry with the name SYSPLEX:SYSPLEX:PLEXVIEW.  There should also be at least one entry with the name plexname:MVS:SYSPLEX.  If you are monitoring multiple sysplexes, there should be one for each sysplex name.
If you see the SYSPLEX:SYSPLEX:PLEXVIEW entry, then search that Tivoli Enterprise Monitoring Server RKLVLOG for "km5pir" or HUB connection error messages.  If you do not see the SYSPLEX:SYSPLEX:PLEXVIEW entry, then you need to search the *:MVS:SYSPLEX  Tivoli Enterprise Monitoring Server logs for "km5pir" errors.   

If you do not see the plexname:MVS:SYSPLEX entry, then it could be that another Tivoli Enterprise Monitoring Server that is not reporting to this HUB is acting as the sysplex proxy. That can occur when there are multiple environments such as production and test that use the same XCF group name.

Search the Tivoli Enterprise Monitoring Server RKLVLOG for "KDS_XCFPLEXGROUP=". Using the value that is specified, rearrange the value by placing the last character in the front and issue a z/OS display XCF command.

For example, if the value in the RKLVLOG is KDS_XCFPLEXGROUP=LPAR400Z, issue command
D XCF,GRP,ZLPAR400,ALL
That displays the following output:

IXC333I  16.36.57  DISPLAY XCF 231                    


   INFORMATION FOR GROUP ZLPAR400                      
   MEMBER NAME:        SYSTEM:     JOB ID:    STATUS:  
   M1812               SYSL        M560DSST   ACTIVE  
   M1813               SP23        M550DSST   ACTIVE  
   M1814               SP11        M510DSST   ACTIVE  
   M1815               SP22        M540DSST   ACTIVE  
   M1818               SYSL        M560DSST   ACTIVE  
   M1819               SYSG        M5D0RMTG   ACTIVE  
   M1820               SP12        M520DSST   ACTIVE  
   M1821               SP13        M530DSST   ACTIVE  
   M1822               SP14        M570DSST   ACTIVE  

That shows all the Tivoli Enterprise Monitoring Server tasks that are using that same KDS_XCFPLEXGROUP value.
If you determine that some of these Tivoli Enterprise Monitoring Server tasks should be reporting as one group and some as another, then you need to change the KDS_XCFPLEXGROUP value.  This parameter is specified in the KDSENV member in the RKANPARU data set.

By default the value is set to the actual sysplex name. But you can override that to specify any name that you want in order to differentiate one set of Tivoli Enterprise Monitoring Servers from another. In this example, the actual sysplex name is LPAR400J, as seen in the origin node values displayed on the Hub Topology screen. However, the KDS_XCFPLEXGROUP value was specified as LPAR400Z to put all these Tivoli Enterprise Monitoring Servers into a specific group. There is also an optional KDS_KOS_PLEXNAME variable that can be specified, if you want OMEGAMON to override the sysplex name part of managed system name.  Under most circumstances, these two parameters are set (or default) to the same value.

Resolving The Problem

For HUB connection errors, make sure that the HUB Tivoli Enterprise Monitoring Server is up and running and all the correct communication protocols are enabled. 
For KDS_XCFPLEXGROUP issues, use PARMGEN to set these values.  Refer to the rte member name in your WCONFIG data set and update to the following parameters:
GBL_SYSPLEX_NAME_XCFPLEXGROUP
KM5_SYSPLEX_KDS_KOSPLEXNAME_FLAG

[{"Product":{"code":"SS2JNN","label":"Tivoli OMEGAMON XE on z\/OS"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"5.1.0;5.1.1;5.3.0;4.2.0","Edition":"","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}}]

Document Information

Modified date:
15 May 2020

UID

swg21691204

Page Feedback