PDS data set names

Edit online

This topic lists the data set names for both PDS V1 and PDS V2.

The naming conventions for the persistent data store (PDS) data sets are different between PDS V1 and PDS V2. The following tables provide the PDS V1 and PDS V2 file naming conventions for collections running in the Tivoli Enterprise Monitoring Server address space (see Table 1) and in the Tivoli Enterprise Monitoring Agent address space (see Table 2).

Table 1. PDS data set names for the monitoring server
Product or component Earliest version supports PDS V2 PDS V1 data set name PDS V2 data set name
IBM Tivoli Monitoring on z/OS 6.3.0
Data sets used for collection on the monitoring server:
  • RppSGRPn
  • RPDSGRPn
  • RGENHISn
where:
  • pp is the two-character OMEGAMON product or component code
  • n is a sequential identifier number (0-9, A-Z). The default values set by PARMGEN are 1-6.
Data sets used for collection on the monitoring server:
  • Gppmnnnn (for monitoring agent collection running in the monitoring server address space)
  • HPDmnnnn
where:
  • pp is the two-character OMEGAMON product or component code
  • m is the granularity level (0-4). This information is for internal use.
  • nnnn is a sequential, rotating number (0-9, A-Z), or CONF for the configuration file
Table 2. PDS data set names for monitoring agents
Product or component Earliest version supports PDS V2 PDS V1 data set name PDS V2 data set name
For reference: PDS data set naming conventions for monitoring agents
Data sets used for collection in the monitoring agent address space:
  • RKppaaan
where:
  • pp is the two-character OMEGAMON product or component code
  • aaa varies by product
  • n is a sequential identifier number (0-9, A-Z). The default values set by PARMGEN are 1-6.
Data sets used for collection in the monitoring agent address space:
  • Hppmnnnn
where:
  • pp is the two-character OMEGAMON product or component code
  • m is the granularity level (0-4). This information is for internal use.
  • nnnn is a sequential, rotating number (0-9, A-Z), or CONF for the configuration file
IBM Z® OMEGAMON® for CICS® 5.5.0 RKC5HISn (collection running in agent address space)

RKGWHISn (collection running in agent address space)

RKCPHISn (collection running in monitoring server address space)

Note: KCSHIST files for are CICS task history and are not part of the persistent data store.
 HC5mnnnn

HGWmnnnn
IBM Tivoli OMEGAMON® XE for Db2 Performance Expert on z/OS 5.4.0 RKD5HISn (collection running in agent address space)

RKDPHISn (collection running in monitoring server address space)

 HDPmnnnn
IBM OMEGAMON for IMS on z/OS 5.5.0 RKI5HISn (collection running in agent address space)

RKIPHISn (collection running in monitoring server address space)

 HI5mnnnn
IBM Z OMEGAMON AI for JVM 5.5.0 RKJJHISn HJJmnnnn
IBM OMEGAMON for Messaging on z/OS 7.3.0 RKMQPDSn

RKQIPDSn

 HMQmnnnn

HQImnnnn
IBM Z OMEGAMON AI for Networks 5.5.0 RKN3HISn HN3mnnnn
IBM OMEGAMON for Storage on z/OS 5.5.0 RKDFDSAn

RKDFDSBn

RKS3DSAn

Note: PDS V1 is no longer supported for IBM OMEGAMON for Storage on z/OS.
 HDFmnnnn

HS3mnnnn
IBM Z OMEGAMON AI for z/OS 5.5.0 RKM5LPRn

RKM5PLXn

 HM5mnnnn
IBM Z NetView Enterprise Management Agent 6.4.0 RKNAHISn HNAmnnnn
IBM Tivoli Advanced Allocation Management for z/OS 3.3.0 RKRJHISn HRJmnnnn
IBM Tivoli Advanced Audit for DFSMShsm 2.6.0 RKRGHISn HRGmnnnn
IBM Tivoli Advanced Backup and Recovery for z/OS 2.4.0 RKRVHISn HRVmnnnn
IBM Tivoli Advanced Catalog Management for z/OS 2.6.0 RKRNHISn HRNmnnnn
IBM Tivoli Advanced Reporting and Management for DFSMShsm 2.6.0 RKRHHISn HRHmnnnn
IBM Tivoli Automated Tape Allocation Manager for z/OS 3.3.0 RKRKHISn HRKmnnnn
IBM Tivoli Composite Application Manager (ITCAM) for Application Diagnostics Agent 7.1.1 RKYNPDSn HYNmnnnn
Note: After you have switched to PDS V2, PDS V1 data sets are no longer needed and can be deleted. For more information, see Removing PDS V1 data sets.