PH67589: COLLECTION ID SET DURING SUBSYSTEM REGISTRATION IN UMS IS NOT APPLIED WHEN ESTABLISHING THE CONNECTION.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• While registering a subsystem in UMS, the Collection ID for JDBC
  packages is successfully updated. However, during connection
  creation using the IDAA Admin Services API, this update is not
  passed. As a result, the Collection ID for JDBC packages is not
  set during the connection setup, which is a required
  configuration for some customer environments.
  
  Additional keywords and symptoms:
  **********************************
  IDAAV7R5/K IDAAV8R1/K
  Admin Services
  case: TS019290985
  

Local fix

• Delete the existing connection from swagger UI via:
  https://<host>:<port>/swagger-ui/index.html?configUrl=/v3/api-d
  ocs/swagger-config#/Db2zConnection/delete
  
  Re-add the connection using the updated connection payload,
  including the additionalProperties with currentPackageSet:
  
  https://<host>:<port>/swagger-ui/index.html?configUrl=/v3/api-d
  ocs/swagger-config#/Db2zConnection/add
  and add:
  
  "additionalProperties": {
   "connectionTimeout": "1000",
   "currentPackageSet": "MYCOLLID"
  }
  
  This would result in a JDBC URL like:
  
  jdbc:db2://host.ibm.com:8010/DDFLOC:currentPackageSet=MYCOLLID;
  connectionTimeout=1000;
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the Db2 Administration Foundation   *
  *                 for z/OS and IDAA features                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Collection ID for JDBC packages     *
  *                      configured in UMS is not propagated     *
  *                      from UMS wrapper during DB2 connection  *
  *                      creation via the IDAA Admin Services    *
  *                      API.                                    *
  ****************************************************************
  While registering a subsystem in UMS, the Collection ID for JDBC
  packages is successfully updated. However, during connection
  creation using the IDAA Admin Services API, this update is not
  propagated. As a result, the Collection ID for JDBC packages is
  not set during the connection setup, which is a required
  configuration for some 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:

Modules/Macros

• IZPSERVE IZPUI
  

Fix information

• Fixed component name

  UNIFIED MGMT SV

• Fixed component ID

  5698UM100

Applicable component levels

• R120 PSY UO04520

     UP25/08/20 P F508

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.