PDS V2 parameters and members
This topic lists the parameters and RKANPARU members related to persistent data store V2.
PDS V2 parameters
Runtime environment, monitoring server, and agent-specific parameters can be used to control the activation of PDS V2 and to define PDS V2 data set allocation settings. These parameters are supported by Configuration Manager and PARMGEN.
- Runtime environment (RTE)
-
The following runtime environment parameters control PDS V2 settings for an individual runtime environment and provide default settings for the OMEGAMON monitoring agents and the monitoring server configured in that environment. These parameters control whether PDS V2 is activated for the runtime environment and define default data set allocation settings.
- Monitoring server (KDS)
-
The following parameters provide PDS V2 settings for the Tivoli Enterprise Monitoring Server (monitoring server). These parameters control whether PDS V2 is activated for the monitoring server and define data set allocation settings.
- Monitoring agents (Kpp)
-
The following parameters provide agent-specific settings for PDS V2. These parameters control whether PDS V2 is activated for the agent and define data set allocation settings.
Note: The data set management mode (whether to manage the data sets by space or by time) depends on
the Extent Constraint Removal (ECR) attribute of the SMS data class used when allocating the data
sets. For more information, see Data set management modes.
PDS V2 members
PDS V2 uses the following members in &rhilev.RKANPARU.
Important: These members are generated by Configuration Manager or PARMGEN and should not be
modified manually as they would be overwritten by the next GENERATE or
$PARSE run.
- KPQHINIT
- Runtime environment settings for PDS V2 parameters, like the high-level qualifier for the data sets allocated by PDS V2 (for example, RTE_PDS2_HILEV)
- KPDKPQIN
- Member for the Tivoli Enterprise Monitoring Server (monitoring server) that allows you to tailor parameters like PDS V2 file counts (for example, KDS_PDS2_FILE_COUNT).
- KppKPQIN
- Agent-specific member (for example, KD5KPQIN for OMEGAMON for Db2), that allows you to tailor agent-specific parameters like PDS V2 file counts (for example, Kpp_PDS2_FILE_COUNT).