Procedure
1. To perform a diagnostic action:
v Open a workspace view that shows real-time data and compare it with the
unexpected data.
v To understand how data is aggregated for various data types, see Tivoli
Management Services Warehouse and Reporting (http://
www.redbooks.ibm.com/abstracts/sg247290.html). This IBM Redbooks
publication describes aggregation methods used by the Summarization and
Pruning Agent.
2. To perform a corrective action:
v Review the documentation for the monitoring agents that are generating the
unexpected values. This clarifies the expected types of values for the
attributes in question.
Resolving persistent data store for z/OS problems
If you encounter a problem with the configuration of the persistent data store on
the Tivoli Enterprise Monitoring Server, you can check the RKPDLOG output to
verify the configuration.
About this task
To resolve persistent data store for z/OS problems, you perform diagnostic and
corrective actions. These actions include verifying that the data store is configured
properly.
Procedure
Diagnostic and corrective actions
1. Is historical data configured to be collected at the agent or the monitoring
server? If the agent is configured in the address space of the monitoring server,
then historical data can be collected only at the monitoring server.
v If historical data is configured to be collected at the monitoring server, see
step 2 below.
v If historical data is configured to be collected at the agent, see step 3 below.
2. To verify that the persistent data store is configured correctly, on the
monitoring server, check the RKPDLOG output, for example:
v
2008/07/28 08:45:41 KPDIFIL: Status of files assigned to group GENHIST:
2008/07/28 08:45:41 -----------------------------------------------------
2008/07/28 08:45:41 &philev.RGENHIS3 Status = Active
2008/07/28 08:45:41 &philev.RGENHIS2 Status = Offline
2008/07/28 08:45:41 &philev.RGENHIS1 Status = Offline
2008/07/28 08:45:41 -----------------------------------------------------
2008/07/28 08:45:41 KPDIFIL: End of group GENHIST status.
3. To verify that the persistent data store is configured correctly at the agent,
check the RKPDLOG of the agent, for example:
v If KM5AGENT (this agent runs on the monitoring server), check the
RKPDLOG of the monitoring server:
2008/07/28 08:48:27 KPDIFIL: Status of files assigned to group PLEXDATA:
2008/07/28 08:48:27 -----------------------------------------------------
2008/07/28 08:48:27 &philev.RKM5PLX3 Status = Active
2008/07/28 08:48:27 &philev.RKM5PLX2 Status = Empty
2008/07/28 08:48:27 &philev.RKM5PLX1 Status = Partially Full
2008/07/28 08:48:27 -----------------------------------------------------
Chapter 3. Common problem solving 23
To Next Page
Loading...
Need help?
General
