TEP Workspaces not showing data or gaps of historical data

z/OS TEMS and agents only.

From the RKPDLOG, check for the following messages:

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

If the time difference between "initialization started" to "initialization complete" is in minutes, this may be causing data not to show up in the TEP workspaces or gaps in the historical data collection.

From the agent or TEMS started task (depending on what application is having the above issue), look for the //RKPDIN ddname and obtain the dataset name. Edit the dataset, usually &rhilev.&rte.RKANPARU, and edit member (KppPCTL). It will look similar to the following:

MAINTPRC PROC=KPDPROC1 GENPROC
LOADMOD RKANMODL
EXEC DSN:&rhilev.&rte.RKANPARU(KPDPGpp)
EXEC DSN:&rhilev.&rte.RKANPARU(KppDEFIN)
EXEC DSN:&rhilev.&rte.RKANPARU(KppPG)

Note: 1) Where pp is the product code, for example if your MQ data is not being returned in your workspace, pp will be MQ. 2) The above example is from an agent address space, RKPDIN from a TEMS address space will look similar.

Modify KppPCTL by adding BATCHINIT to the first line as follows:

MAINTPRC PROC=KPDPROC1 GENPROC BATCHINIT
LOADMOD RKANMODL
EXEC DSN:&rhilev.&rte.RKANPARU(KPDPGpp)
EXEC DSN:&rhilev.&rte.RKANPARU(KppDEFIN)
EXEC DSN:&rhilev.&rte.RKANPARU(KppPG)

Recycle the address space.

Note: BATCHINIT indicates that initialization of a datastore file should be done by the batch job instead of being done within the PDS. Without BATCHINIT specified, the initialization was always done in the maintenance procedures.