(Optional) Enable maintenance of the historical data store

If you intend to enable historical data collection and have allocated the historical data set and configured maintenance for data store, you must perform two additional tasks to enable the maintenance.

About this task

Important: The content in this section was created for and applies to the original persistent data store, referred to as PDS V1. A new PDS version (referred to as PDS V2) now exists. PDS V1 will eventually be deprecated.

The KPDPROC1 maintenance procedure that is used to maintain the physical files must have the required authority to read, write, and update the files.

The KPDPROCC REXX procedure runs in a TSO environment and must be enabled to run as an authorized program under TSO. To authorize the KPDPROCC procedure, you must authorize the KPDDSCO module.

If you are upgrading an existing monitoring server, you must also refresh the KPDPROC1 maintenance procedure in your system procedure library.

Procedure

Ensure that KPDPROC1 procedure has the necessary authority to read, write, and update the persistent data store files.
Authorize the KPDDSCO module by adding KPDDSCO to the system PARMGEN(IKJTSOnn) under the AUTHPGM section and refresh the IKJTSOnn member by issuing the set command (T IKJTSO=nn).
You might request that authorized system programmers perform this step so it can be scheduled with the LPAR change control processes.
Verify that the configuration and authorization has been successful:
1. Bring up the started task (for monitoring server or monitoring agent) that will collect historical data into the product's persistent data store libraries. In the RKPDLOG DDNAME started task, find any persistent data store libraries in a non-Offline status (for example, Partial or Full status).
2. From a z/OS® operator console, issue the following z/OS MODIFY command:
```
/F stcname,KPDCMD RECOVER FILE=DSN:pds_data set
```
  where stcname is the name of the started task performing the persistent data store collection, and pds_data set is the persistent data store data set.
  For example, issue the following MODIFY command for the monitoring server:
```
/F CIDSST,KPDCMD RECOVER FILE=+ 
 DSN:rhilev.rte.RGENHIS1
```
3. Wait 5 minutes.
4. In the RKPDLOG DDNAME started task, find the following Command: and KPDDSTR: references as shown in the following monitoring server RKPDLOG DDNAME example:
```
Command: RESUME FILE=DSN:rhilev.rte.RGENHIS1
KPDDSTR: CONNECT processing started for DataStore file
DSN:rhilev.rte.RGENHIS1
KPDDSTR: CONNECT processing ended for DataStore file
DSN:rhilev.rte.RGENHIS1
```
5. If these references are not found, view the KPDPROC1 started task in SDSF and look for any obvious errors.

What to do next

Even though the historical data store is allocated and configured, no historical data is collected until collection is enabled using the Tivoli Enterprise Portal.