PTF UJ97474 for APAR OA67992 (2Q25)

Edit online

PTF UJ97474 for APAR OA67992 (2Q25) provides Configuration Manager enhancements that allow you to omit security exit and assemble-and-link processing during the GENERATE action. Additionally, new parameters allow you now to allocate your PDS V2 history data sets on different volumes for the monitoring server and for each monitoring agent. Updates have also been made to the OMEGAMON for IMS ATF parameters.

Configuration Manager-only updates

The GENERATE action provides the following new action options:

NOSECEXITS: When OPTION NOSECEXITS is specified, the GENERATE action does not perform configuration processing for security exits. You can use this option on the initial run of the GENERATE action for a new runtime environment, as well as on subsequent runs. You can abbreviate this keyword to NS.
NORELINK: When OPTION NORELINK is specified, the GENERATE action does not assemble and link the IBM Z OMEGAMON AI for Networks (KN3) or OMEGAMON enhanced 3270 user interface (KOB) modules, even if a relink is required. You can use this option on the initial run of the GENERATE action for a new runtime environment, as well as on subsequent runs. You can abbreviate this keyword to NL.

Options NOSECEXITS and NORELINK do not update the RKANMODU load library, a data set that might require more restrictive authorization for updating. You can use these options together while performing the other GENERATE configuration steps that do not require additional access.

For more information, see GENERATE options.

Configuration Manager and PARMGEN updates

The following persistent data store V2 (PDS V2) parameters have been introduced:

Common agent parameter Kpp_PDS2_VOLUME allows PDS V2 history data sets in each monitoring agent to use a different volume for allocation. If a value is not specified, parameter Kpp_PDS2_VOLUME uses the value from parameter RTE_PDS2_VOLUME.
Parameter KDS_PDS2_VOLUME allows PDS V2 history data sets in the monitoring server to use a custom volume for allocation. If a value is not specified, parameter KDS_PDS2_VOLUME uses the value from parameter RTE_PDS2_VOLUME.

Product-specific updates

OMEGAMON for IMS

New parameters for the Application Trace Facility (ATF) have been introduced that allow you to individually customize each IMS subsystem. The new parameters replace former parameters as described in the following table:

Table 1. Updated OMEGAMON for IMS ATF parameters
Former parameter name	New parameter name	New default value
KI2_CLASSIC_ATFI2	KI2_I1nn_CLASSIC_ATFI2	N
KI2_CLASSIC_ATF_SANDBOX	KI2_I1nn_CLASSIC_ATF_SANDBOX	OFF
KI2_CLASSIC_ATF_AUTORESTART	KI2_I1nn_CLASSIC_ATF_AUTORSTRT	YES
KI2_CLASSIC_ATF_ATFBUFF	KI2_I1nn_CLASSIC_ATF_ATFBUFF	512

The new parameters must be added between table markers and in the correct row, for example:

KI2_I1 BEGIN
KI2_I101_ROW                      01
KI2_I101_CLASSIC_ATFI2            N
KI2_I101_CLASSIC_ATF_SANDBOX      OFF
KI2_I101_CLASSIC_ATF_AUTORSTRT    YES
KI2_I101_CLASSIC_ATF_ATFBUFF      512
...
KI2_I1 END

Note: For more information about parameter tables in Configuration Manager, see Sparse parameter tables: The first row sets the default values for subsequent rows.

Attention: After applying this maintenance, the former parameters will no longer be used for configuration and in some cases might be lost. Before updating your configuration, make sure to back up the former parameters. See the PTF HOLD TEXT for detailed instructions.