IBM Support

Near Term History - RMF DDS report failed

Troubleshooting


Problem

Near term history data is not available for OMEGAMON XE ON Z/OS in the Enhanced 3270UI.

Cause

Possible issues are:

1) The Tivoli Management Server (tems) task is not authorized to get data from the RMF DDS (Distributed Data Server) GPMSERVE.
2) RMF is not defined with enough storage or a high enough dispatching priority.
3) The Tivoli Management Server (tems) is not authorized to use Unix system services, needed for tcp/ip communications.
4) The RMF DDS task has been renamed to something other than the default GPMSERVE.

Resolving The Problem

For Symptom #1
Make sure that the Tivoli Management Server (tems)  has been configured to communicate with the RMF DDS (GPMSERVE) task.  See documentation links below. 
Make sure that the userid associated with the Tivoli Management Server (tems) started task is defined as a valid RACF userid WITH a password.
When using ACF2, the subsystem userid needs to have the STC bit turned off. Then set a switch in the Global Systems Options (GSO) to allow the ID to run as an STC and also logon.
If your site requires started tasks to be defined as protected without a password, then refer to this document for an alternate configuration option using AT-TLS..
AT-TLS RMF DDS setup_2.pdf
Under z/OS 2.4, AT-TLS is the default.   If you do not use AT-TLS, then you need to set the GPMSRVNN parameter HTTPS(NO).


Make sure that OMEGAMON is connecting to the correct GPMSERVE task. The following message in the subsystem SYSPRINT file shows the IP address being used. View the GPMSERVE task to make sure that is the correct address.
KM5RM0049I: RMF DDS connection now established at nnn.n.nn.n:nnnn

For Symptom #2
Make sure that the RMF started task has a REGION size of at least 128M.
Verify that the RMF and RMFGAT started tasks are defined with the second-highest priority in the system, next to the system address spaces. Use the WLM application to put RMF and RMFGAT in service class SYSSTC to ensure that its dispatching priority will always be above any installation-defined service class.

For Symptom #3
Define an OMVS segment for the Tivoli Management Server (tems) task to enable it to use Unix System Services.
https://www.ibm.com/support/knowledgecenter/en/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/zcommonconfig/complete_e3270_unixid_cpcg.htm

For Symptom #4
The following is only needed if the RMF DDS started task is NOT named GPMSERVE. Otherwise, verify all the items in the links below have been accomplished. If the problem persists, gather the documentation described at the bottom of this technote.
Update the RKANPARU KDSENV member to add the following parameter where xxxxxx is the name of the gpmserve started task:
KM5_PTAPPL=xxxxxxxx
Make sure the applicable PTF to support this keyword is applied:
V550 - UA93106
V530 - UA92789

The following links to the V550 documentation describe all the RACF and GPMSERVE requirements for RMF DDS collection:
https://www.ibm.com/support/knowledgecenter/SS2JNN_5.5.0/com.ibm.omegamon_xezos.doc_5.5.0/configuration/complete_enable_rmf_omxezos_pcg.html
https://www.ibm.com/support/knowledgecenter/SS2JNN_5.5.0/com.ibm.omegamon_xezos.doc_5.5.0/configuration/plan_rmf_omxezos_pcg.html

The following link describes how to configure the OMEGAMON XE on z/OS agent to use RMF data:
https://www.ibm.com/support/knowledgecenter/SS2JNN_5.5.0/com.ibm.omegamon_xezos.doc_5.5.0/configuration/cfg_parmlib_omxe_rmf_omxezos.html

If you want to disable RMF collection until all the above configuration is complete, you can specify KM5_NTH=N in your RKANPARU(KDSENV) member. Via PARMGEN, you would specify N for the RTE_KM5_NTH parameter.


If the instructions in the above links have been verified and completed and the problem persists, then the following tracing should be enabled and sent to IBM support for problem diagnosis.

1) Specify DEBUG_LEVEL(3) in the GPMSRVnn member in the system parmlib dataset used by the GPMSERVE task.
2) Change any DUMMY DD statements in the GPMSERVE proc to an appropriate SYSOUT= value so that the trace output will be generated and saved.
3) Recycle GPMSERVE and issue the following z/OS modify command /F GPMSERVE,TRACEON
4) Restart the Tivoli Management Server (tems), and send in the complete started task output from the tems and GPMSERVE tasks.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGHN2","label":"IBM OMEGAMON for z\/OS"},"ARM Category":[{"code":"a8m0z00000008lQAAQ","label":"OMEGAMON for zOS"},{"code":"a8m0z00000008mYAAQ","label":"OMEGAMON for zOS-\u003ETroubleshooting"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Type":"MASTER"}]

Document Information

Modified date:
18 April 2022

UID

swg21697224