New parameters
OMEGAMON for Db2 Performance Expert 5.5.0 introduces new parameters that simplify configuration for Classic Near Term History VSAM and static sequential data sets. In addition, the existing real-time options parameter NTHDB2I is exposed as a formal parameter KD2_OMPE_OPTS_NTHDB2I.
NTH Collector Db2 initialization option
- KD2_OMPE_OPTS_NTHDB2I
Db2 Version 13
- GBL_DSN_DB2_LOADLIB_V13
- GBL_DSN_DB2_RUNLIB_V13
Near Term History Classic VSAM file definition
- Parameters KD2_PFnn_HIS_VSAM_SU and KD2_PFnn_HIS_VSAM_MB are reused accordingly.
- KD2_PFnn_HIS_LOG_NUM replaces KD2_PFnn_HIS_LOG<n>
- KD2_PFnn_HIS_VSAM_SCLAS replaces KD2_PFnn_HIS_VSAM_SCLAS<n>, n = 2...7
- KD2_PFnn_HIS_VSAM_MCLAS replaces KD2_PFnn_HIS_VSAM_MCLAS<n>, n = 2...7
- KD2_PFnn_HIS_VSAM_VOLUME replaces KD2_PFnn_HIS_VSAM_VOLUME<n>, n = 2...7
The Classic Near Term History VSAM low level qualifier (LLQ) in release 5.5.0 changed to accommodate the number of data sets > 99 as per by KD2_PFnn_HIS_LOG_NUM.
- Old VSAM LLQ: RKD2VSxx
- New VSAM LLQ: RKD2Vxxx
The allocation of the 5.5.0 VSAM data sets is entirely done by Configuration Manager (or PARMGEN) using the following pattern:
- [RTE_VSAM_HILEV.RTE_NAME| KD2_OMPE_VSAM_DSHLQ].%DB%. RKD2Vxxx
If parameter KD2_OMPE_VSAM_DSHLQ is set, this parameter is used as the High-Level Qualifier (HLQ) for the VSAM data set. If not set, the default HLQ name is the concatenation of parameter values for HLQ RTE_VSAM_HILEV and RTE_NAME. In all cases the value %DB% is derived from the Db2 monitoring definition parameter KD2_DBxx_DB2_SSID.
Near Term History Classic Static Sequential file definition
- Parameters KD2_PFnn_HIS_SEQ_PRIMARY_CYL and KD2nn_PF_HIS_SEQ_SECONDARY_CYL are reused accordingly.
- KD2_PFnn_HIS_SEQ_LOG_NUM replaces KD2_PFnn_HIS_SEQLOG<n>
- KD2_PFnn_HIS_SEQ_MCLAS replaces KD2_PFnn_HIS_SEQ_MCLAS<n>
- KD2_PFnn_HIS_SEQ_SCLAS replaces KD2_PFnn_HIS_SEQ_SCLAS<n>
- KD2_PFnn_HIS_SEQ_UNIT to KD2_PFnn_HIS_SEQ_UNIT<n>
- KD2_PFnn_HIS_SEQ_VOLUME to KD2_PFnn_HIS_SEQ_VOLUME<n>
For explanations of each parameter, find the parameter in Parameters in the OMEGAMON for Db2 Performance Expert on z/OS User's Guide.
Some of the Classic Thread History settings might need to be manually migrated. For more information about customizing your data set allocations, see How to fully customize your data set allocations.