Good news - the new version of OMEGAMON Db2 agent went live and Configuration Manager not only provided the configuration support with PTF UJ98473, but also made some significant configuration changes. I'd like to make sure that you don't miss those new simplification options! Note: I say "options" because you are not required to make updates to your Configuration Manager RTE definition right away, as they are fully backwards compatible, but they will make it easier to configure IBM Z OMEGAMON AI for Db2 6.1.0.
Performance Warehouse parameter simplification
To configure Performance Warehouse default storage groups, 4K buffer pools, and 32K buffer pools, we support full customization for each entry. However, we recognize that you might want to use one value for each. So we introduced three new parameters in Configuration Manager with the following defaults:
KD2_DB_PWH_DEFAULT_STG SYSDEFLT
KD2_DB_PWH_DEFAULT_BP4K BP0
KD2_DB_PWH_DEFAULT_BP32K BP32K
You can use them interchangeably with the old KD2_DB_PWH_D2PW* parameters, depending on your customization needs. But now it is fully possible to just use these 3 new parameters, and delete the rest. They are still DB table parameters, so each Db2 system can have different defaults set.
Don't forget that Configuration Manager has a model row concept, where values set in model row number one - DB01 - would be cascaded down to all subsequent rows. Due to backwards compatibility requirements, if both old and new parameters are set, the new ones are ignored until the old ones are deleted.
Also note that the GRANT runtime member was also simplified and does not duplicate the statements where storage group and buffer pools are set to the same value.
Near-Term History parameter simplification
We have introduced two new parameters that fit in better with the naming standard for NTH sequential data sets:
KD2_PF_HIS_SEQ_DSNAME
KD2_PF_HIS_SEQ_GDG_LIM
KD2_PF_HIS_SEQ_DSNAME can be used to configure dynamic and generation data group data set names. Static sequential data sets are still automatically named by the configuration tool, this behavior has not changed.
And then there are six existing parameters that had their sphere of influence extended:
KD2_PF_HIS_SEQ_PRIMARY_CYL
KD2_PF_HIS_SEQ_SECONDARY_CYL
KD2_PF_HIS_SEQ_VOLUME
KD2_PF_HIS_SEQ_UNIT
KD2_PF_HIS_SEQ_MCLAS
KD2_PF_HIS_SEQ_SCLAS
You do not have to worry anymore about looking up which parameters are used for D, which are used for S, and which are used for G types. They all work the same way.
As they are table parameters as well, the model row and backward compatibility rules are the same as in PWH parameters.
Just keep in mind: this simplification was brought only in Configuration Manager, and only in IBM Z OMEGAMON AI for Db2 version 6.1.0.
#IBMZ #OMEGAMON #AIOpsonZ