Friday, October 7, 2011

Problems with historical data not showing up in the TEP?

This is an interesting Technote that I read recently. Apparently some Tivoli Portal users who were collecting history were seeing gaps in history collection data, or history data missing altogether. The Technote describes the eyecatchers to look for if this issue is occurring, and then provides a workaround/resolution.

The net is if you are missing data, and you see a long time (in the range of multiple minutes or more) between these messages in RKPDLOG of the z/OS TEMS or TEMA (i.e. the agent task on z/OS), then you may want to check things out. Here are the messages (an init started followed by an init complete message):

yyyy/mm/dd hh:mm:ss KPDINDS: Initialization started for DataStore file DSN:&rhilev.&rte.lowlev

yyyy/mm/dd hh:mm:ss KPDINDS: Initialization complete for DataStore file DSN:&rhilev.&rte.lowlev

The workaround? Go into the KxxPCTL (xx meaning the product code for the agent type) for the task in question, and add the parm BATCHINIT like in the following example:


The BATCHINIT parm indicates that initialization of a datastore file should be done by the batch job instead of being done within the PDS processing of the TEMA or TEMS started task.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.