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

The following parameter controls the behavior of the NTH collection task during startup:
  • KD2_OMPE_OPTS_NTHDB2I

Db2 Version 13

If you want to configure a Db2 13 subsystem, specify the data set in which the Db2 version 13 LOADLIB and RUNLIB modules reside.
  • GBL_DSN_DB2_LOADLIB_V13
  • GBL_DSN_DB2_RUNLIB_V13

Near Term History Classic VSAM file definition

You do not need to manually specify the first seven VSAM data sets in the configuration or add data sets using an embed member. Beginning with 5.5.0, you can specify the number of VSAM data sets to allocate using KD2_PFnn_HIS_LOG_NUM in the respective monitoring profile. If you need to customize allocation attributes, use the OMEGAMON for Db2 Performance Expert new 5.5.0 parameters to configure customizations for all allocated data sets, and remove the replaced parameters from your 5.5.0 environment.
  • 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

You do not need to manually specify the static sequential data sets. Beginning with 5.5.0, you can specify the number of static sequential data sets to use using parameter KD_PFnn_HIS_SEQ_LOG_NUM in the monitoring profile. If you need to customize allocation attributes, use the following parameters to configure customizations for all allocated data sets:
  • 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.