PTF UJ98753 for APAR OA68536 (4Q25)

Edit online

PTF UJ98753 for APAR OA68536 (4Q25) provides Configuration Manager enhancements by introducing checking for undefined symbols during parameter validation and improving the data set allocation process for agents. New parameters are introduced for situation status streaming, controlling the session timeout value for OMEGAMON 3270 Classic interface, and other product-specific settings.

Configuration Manager-only updates

The following updates have been made:
  • The GENERATE action and the GENERATE action with OPTION VALIDATE now check that any symbol used in a parameter value is properly defined. If an undefined symbol is encountered, new message KFJ00253E is issued for each undefined symbol.

    Previously, if you had system variables enabled in your runtime environment (that is, parameter RTE_SYSV_SYSVAR_FLAG set to Y), and used a symbol for one of your parameter values, Configuration Manager did not verify if the symbol was defined.

    Now, when the validation process encounters a symbol as a parameter value, it checks for the definition where the symbols are defined, as follows:
    • System symbols defined (as either dynamic or static) in the PARMLIB library
    • System symbols defined in member RTEDEF(SYS@lpar)
    • User variables defined in members RTEDEF(VAR$GLOB) or RTEDEF(VAR$lpar)
    If the symbol definition is not found, the GENERATE action issues message KFJ00253E, and the system action depends on the RTE_VALIDATION_LEVEL parameter setting, as follows:
    • If parameter RTE_VALIDATION_LEVEL is set to W (Warning) or E (Error), the GENERATE action stops with a return code of 8. You must correct the parameter value or symbol definition.
    • If parameter RTE_VALIDATION_LEVEL is set to I (Informational), processing continues, allowing you to use the undefined symbol in your parameter settings. This behavior is acceptable in the following scenarios:
      • You have an undefined symbol that becomes defined when the agent starts, as the symbol can be defined in the PARMLIB library and added dynamically.
      • Your runtime environment is being packaged for deployment to another system; during the GENERATE action, the validation process does not have access to the remote system symbols.
        Tip: Optionally, you can discover the system symbols on the target system and send the results back the configuration system for validation.
  • Configuration Manager no longer attempts to allocate data sets in the data set allocation stage for an agent if the data sets already exist. This avoids RACF violations if special privileges are needed for updating data set RKANMODU.

Product-specific updates

Tivoli Enterprise Monitoring Server
New parameter KDS_STREAM_SITUATION_STATUS controls if situation status streaming from the monitoring server to IBM Z OMEGAMON Data Provider is enabled. The default value is N.
OMEGAMON 3270 Classic interface
New parameter Kpp_CLASSIC_TIMEOUT (where pp is C2, D2, I2, or M2) allows you to control the idle session timeout value for the OMEGAMON 3270 Classic interface for the respective product.
Note: New parameter KI2_CLASSIC_TIMEOUT for OMEGAMON for IMS has the default value of 0. This default value is different from the previously hardcoded value of 30 that was defined in member RKANPARU(KOIVTM*). If this member is not excluded, the timeout value is updated with the new default.
IBM Z OMEGAMON AI for z/OS 6.1
New parameter KM5_BPX_SUPERUSER allows you to bypass SAF or RACF privilege checks when the monitoring server needs superuser authority to perform certain operations. The default value is N.

If KM5_BPXSUPERUSER exists in your embeds data set, remove the parameter; Configuration Manager adds it automatically. Otherwise, there will be duplicate definitions.

OMEGAMON for JVM 6.1.0
New parameter KJJ_IMSREQ_LATENCY specifies the startup delay between the IMS transaction initialization and the z/OS Connect API request invocation. The value is in seconds, and the default value is 2.