Allocate data sets and configure maintenance for historical data

To collect historical data for display in either the Tivoli® Enterprise Portal or the OMEGAMON® Enhanced 3270 user interface, you must allocate data sets to store the data. You must configure the persistent datastore (PDS) that manages the collected data.

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.
You can use the defaults or configure any of the following parameters:
  • A high-level qualifier for the historical data sets and a prefix for the PDS maintenance procedures.
  • The number of files to be allocated for historical data storage.
  • For non-SMS managed files, the location where the files are allocated.
  • Disposition of the data in data sets that are being emptied by PDS maintenance.
  • The address space that does the data collection.
  • The number of cylinders to set aside on behalf of each product and the name of the PDS group.
No collection of historical data occurs unless collection is configured through either the Tivoli Enterprise Portal or the OMEGAMON Enhanced 3270 user interface.

For more information about these parameters, see Common parameters.

Procedure

  • Specify a high-level qualifier for the historical data sets and a prefix for the PDS maintenance procedures other than the defaults.
    RTE_PDS_HILEV
    The default for data sets is %RTE_HILEV.%RTE_NAME%.
    RTE_PDS_KPDPROC_PREFIX
    The default is %RTE_STC_PREFIX%.PD (IBMPD, previously KPDPROC).
  • For non-SMS managed files, specify where the files are allocated.
    • RTE_PDS_SMS_VOLUME
    • RTE_PDS_SMS_UNIT
    • RTE_PDS_SMS_STORCLAS
    • RTE_PDS_SMS_MGMTCLAS
  • Configure maintenance for the PDS.
    The PDS periodically empties and reuses the data set with the oldest data. You can configure what is to be done with historical data that is sitting in a data set that is being emptied. The default is to delete the data. Alternatively, you can configure maintenance to back up the data to tape or DASD, export the data to an external program for processing, or extract the data and write it in a viewable format by specifying Y or N for the following parameters. The default for each is N.
    • RTE_PDS_BACKUP_FLAG
    • RTE_PDS_EXPORT_FLAG
    • RTE_PDS_EXTRACT_FLAG
  • Specify the PDS initialization option.

    The PDS initialization process can take place in the running address space so long as BACKUP, EXPORT, and EXTRACT are set to N. The RTE_PDS_BATCHINT_FLAG defaults to N. To run the PDS maintenance as a batch process, set this flag to Y.

  • Specify which address space does data collection.

    Location of data collection is configured on a product-by-product basis. Historical data may be collected by the agent address space or the monitoring server address. Some products (OMEGAMON for z/OS and OMEGAMON for Storage on z/OS) can collect data only at the monitoring server address space (Kpp_PD_HISTCOLL_DATA_IN_TEMS_STC=Y). Other products (OMEGAMON for IMS, OMEGAMON for Db2® PE/PM, and OMEGAMON for CICS®) can collect with either monitoring server or agent address space. Some products can collect data at either, but collecting data in the stand-alone agent address space is preferred.

    • Kpp_PD_HISTCOLL_DATA_IN_AGT_STC
    • Kpp_PD_HISTCOLL_DATA_IN_TEMS_STC
    Or (if no corresponding parameter existed in the previous configurations)
    • Kpp_X_PD_HISTCOLL_DATA_IN_AGT_STC
    • Kpp_X_PD_HISTCOLL_DATA_IN_TEMS_STC
  • Specify the number of cylinders to set aside on behalf of each product and the name of the PDS group.
    • Kpp_PD_CYL
  • Specify the number of files to be allocated (if other than the default).
    Kpp_PDS_FILE_COUNT
    The default is 6 files.

What to do next

To complete configuration of historical data collection, perform the following tasks:
  • Run the jobs that allocate the data sets ($PARSE, KCIPPALO).
  • If not already done during preconfiguration preparation, provide access to the PDS files.
  • Authorize the KPDDSCO module.
  • Verify the PDS configuration.
  • Configure data collection through either the Tivoli Enterprise Portal or the OMEGAMON Enhanced 3270 user interface.
See the configuration information for each monitoring agent for product-specific configuration details. For more information about the persistent datastore, see Persistent data store V1 (PDS V1). For instructions for completing configuration tasks outside the configuration software, see Completing the configuration outside the configuration software.