PTF UJ94312 for APAR OA65216 (4Q23)

PTF UJ94312 for APAR OA65216 (4Q23) changes PDS V2 activation for the monitoring server to be enabled by default. In addition, Configuration Manager has been updated to provide enhanced PDS V2 status messaging, improved parameter support for SAF class configuration for product-specific Take Action commands, the ability to override the default binder program, and new Db2-related data set allocation control for remote deployment.

Configuration Manager and PARMGEN updates

With this PTF, activation of the persistent data store V2 (PDS V2) for the Tivoli Enterprise Monitoring Server (monitoring server) is now enabled by default. Previously, the KDS_PDS2_ACTIVATION parameter had the default setting of N; now, the default setting is Y. This change impacts new runtime environments created using either PARMGEN or Configuration Manager.

This change also impacts existing Configuration Manager configurations where the KDS_PDS2_ACTIVATION parameter is not explicitly defined in the RTEDEF library. If there are no other settings preventing PDS V1 from being disabled, the GENERATE action will cause the runtime environment to fully switch to using PDS V2, which will occur when you run a full GENERATE or a GENERATE with options NOUSS or QUICKCONFIG.

Configuration Manager-only updates

The following updates have been made:
  • New informational messages KFJ00223I and KFJ00224I have been added. These messages appear in KCIPRINT to inform you about the global status of PDS V1 and PDS V2 in the runtime environment. If PDS V1 is still enabled, more messages will follow that provide details about the PDS V2 status of individual agents.
  • To simplify System Authorization Facility (SAF) class configuration of product-specific Take Action commands, the RTE_SECURITY_CLASS parameter value is now automatically propagated to the following product parameters as the default value:
  • New parameter GBL_UTIL_BINDER is now available. You can use this parameter to override the default binder program IEWL.
    Note: GBL_UTIL_BINDER is incorrectly documented as KFJ_UTIL_BINDER in the APAR text. The correct name for this parameter is GBL_UTIL_BINDER.
  • New parameter KFJ_LOCAL_KD5_RUN_ALLOC is now available. This parameter controls if the job for Db2-related data set allocation is submitted. This parameter is used for remote deployment scenarios.