OA68134: CONFIGURATION MANAGER / PARMGEN JULY 2025 BUGFIX RELEASE

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Configuration Manager / PARMGEN July 2025 bugfix release
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the Tivoli Management Services  *
  *                 on z/OS Configuration Software               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Bug fixes in IBM Z Monitoring           *
  *                      Configuration Manager                   *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  (1) In E3270UI started task JCL, XKAN* data sets are incorrectly
    specified under TKAN* DD names which causes some panels to
    disappear.
  (2) System variables specified in RTE_NAME may cause a false
    negative error in the data set length validation when
    OMEGAMON for CICS is configured. When RTE_NAME is resolved,
    the total length would fit into the limit.
  (3) PACKAGE action writes incorrect parameters into the PACKMD
    metadata data set if the number of RTE_VSAM_HILEV data set
    qualifiers is different on target and local systems.
    With incorrect parameters passed to ADRDSSU, it does not
    perform a rename when it is required during the extraction of
    the archived RTE in the DEPLOY action.
  (4) CREATE action, when used with a flag KFJ_USE_EMBEDS Y, is
    overwriting members KCI$XW2R and KQI$XML in the EMBEDS library
    which may already contain user edits. User edits must be
    preserved.
  (5) PACKAGE action uses a parameter RTE_SMS_VSAM_UNIT which does
    not exist. It causes errors in the DEPLOY when the system
    cannot allocate VSAM data sets on the correct unit.
  (6) PACKAGE action does not pack PDS V1 data sets if
    RTE_PDS_HILEV uses a custom value and if local parameter
    KFJ_LOCAL_PDS_HILEV is not used.
  (7) When using KFJ_LOCAL_* parameters that differ from the
    target system parameters, Configuration Manager stages
    performing the (re)link and security exit processing are
    referencing RTE_PLIB_HILEV (target system) parameter instead
    of the local one.
  (8) KS3JPUSU template causes KCIPARSE warnings. There is a
     parameter KS3_APP_ZFS_DIR in KS3JPUSU that is resolved to
     its value which causes the line to go beyond column 72.
  (9) It is possible to specify different RTE_PLIB_HILEV values in
    KCIVARS and RTEDEF, but length validation is performed only
    once. It should check allowed lengths for both RTE_PLIB_HILEV
    values.
  (10) Previous release OA67992/UJ97474 changed OMEGAMON for IMS
    ATF parameters into table parameters. If RTE is refreshed
    without having followed the HOLD ACTION instructions, ATF
    will no longer be enabled because the old parameters will be
    ignored, and configuration will not automatically pick up the
    new defaults due to them being commented out.
  

Problem conclusion

• (1) XKAN* data sets have been moved to a correct location under
    RKAN* DD names in E3270UI started task JCL.
  (2) RTE_NAME is now resolved fully before being checked for
    length. This resolution step is only done during length
    validation and does not disable the system variable in
    further processing.
  (3) Variables in the PACKAGE script causing the issue were
    renamed to reference the correct value.
  (4) User modifications in EMBEDS members KCI$XW2R and KQI$XML ar
    no longer overwritten by Configuration Manager.
  (5) PACKAGE workflow script was updated to use the RTE_SMS_UNIT
    parameter for the VSAM data set allocation on the
    remote system.
  (6) Workflow scripts have been changed to properly handle PDS V1
    data set names in the PACKAGE action.
  (7) Instead of the RTE_PLIB_HILEV, the internal parameter is now
    used in the scripts, that will map to a KFJ_LOCAL_* parameter,
    if it was used.
  (8) KS3_APP_ZFS_DIR symbolic name is no longer resolved.
  (9) Additional length validation steps have been added.
  (10) To reduce the impact for the users and to enable backwards
    compatibility, old parameters have been restored:
     KI2_CLASSIC_ATFI2            N
     KI2_CLASSIC_ATF_SANDBOX      OFF
     KI2_CLASSIC_ATF_AUTORESTART  YES
     KI2_CLASSIC_ATF_ATFBUFF      512
    Also, parameter defaults are now being set for table values:
     KI2_I101_CLASSIC_ATFI2            N
     KI2_I101_CLASSIC_ATF_SANDBOX      OFF
     KI2_I101_CLASSIC_ATF_AUTORSTRT    YES
     KI2_I101_CLASSIC_ATF_ATFBUFF      512
    If you had KI2_CLASSIC_ATF* values customized in RTEDEF,
    configuration will continue to use them until the user is
    ready to move to the new table parameters
    KI2_I1nn_CLASSIC_ATF*.
    This change is only applicable to Configuration Manager users.
    Please refer to various maintenance scenarios in HOLD ACTION.
  
    If you use PARMGEN, there is no update from the OA67992/UJ9747
    changes. Old parameters have not been re-added. Please refer t
    OA67992/UJ97474 HOLD ACTION.
  
    Additionally, new ATF table parameters are not added to RTEDEF
    during DISCOVERY action.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ97760

Modules/Macros

• KCIDPNEW KCIJPVER KCIPQPGW KFJALIAS KFJOMEGA KFJSC2WC KFJSEMBC
  KFJSIDEF KFJSLNK  KFJSMIGD KFJSMSGS KFJSSEC  KFJWGEN  KFJWPACK
  KFUIAGTC KFUIMLVL KFUIROWP KFUODISC KOBPRMLB KS3JSUSU KS3PRMLB
  

Fix information

• Fixed component name

  PARMGEN ICAT CO

• Fixed component ID

  5608A41CC

Applicable component levels

• R310 PSY UJ97760

     UP25/07/31 P F507  

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.