PH70723: VALIDATION ERROR WAS DISPLAYED ON THE SUBSYSTEM REGISTRATION PAGE DURING DATA SHARING GROUP REGISTRATION.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A data mapping and validation issue was identified in how system
  identifiers were handled for Db2 Data Sharing Groups. The
  identifier was incorrectly derived from the Data Sharing Group
  name instead of the individual member attach names, resulting in
  invalid values being used.
  In addition, this issue was not consistently detected because
  identifier validation was conditionally enforced based on the
  deployment mode. As a result, errors were allowed to pass in CI
  environments but were blocked in CD environments.
  Based on feedback from SMEs, the logic has been updated to
  ensure accuracy and consistency. The system identifier is now
  sourced from the correct member-level attach name for Data
  Sharing Groups, and validation is applied uniformly across all
  deployment types without conditional exceptions.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the IBM Unified Management Server   *
  *                 for z/OS and the following experiences:      *
  *                 - Db2 DevOps Experience for z/OS             *
  *                 - Db2 Administration Foundation for z/OS     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Can't add or update subsystems after    *
  *                                                              *
  *                      upgrade                                 *
  ****************************************************************
  A data mapping and validation issue was identified
  
  in how system identifiers were handled for Db2 Data Sharing
  Groups. The identifier was incorrectly derived from the
  Data Sharing Group name instead of the individual member attach
  names, resulting in invalid values  being used.
  In addition, this issue was not consistently detected because
  identifier validation was conditionally enforced based on the
  deployment mode. As a result, errors were allowed to pass in CI
  environments but were blocked in CD environments.
  

Problem conclusion

• Apply the PTF provided by this APAR
  

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:

  UO08139

Modules/Macros

• IZPDB2SD IZPDISCP IZPHLOSD IZPIMSSD IZPMNFST IZPSERVE IZPSYSSD
  IZPUI
  

Fix information

• Fixed component name

  UNIFIED MGMT SV

• Fixed component ID

  5698UM100

Applicable component levels

• R120 PSY UO08139

     UP26/06/09 I 1000

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.