PH46970: OBJECTS ARE GETTING CREATED IN MAINFRAME EVEN THOUGH PULL REQUEST IS STILL IN OPENED STATE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Objects are getting created in mainframe even though Pull
  request is still in opened state. These objects got created on
  the click of apply changes, even before the merge button was
  clicked. The problem was a result of renaming the database and
  schemas to name which was unknown to the instance.
   The problem affects all users of IBM Db2 DevOps experience.
  This affects users of all products that depend on UMS (Unified
  Management Server), such as Db2 Administration Foundation and
  Db2 DevOps Experience. Release: Current: UMS 1.1.0.9 Future:
  UMS1.1.0.10
  

Local fix

• BYPASS/CIRCUMVENTION:
  NA
  

Problem summary

• ****************************************************************
  * PROBLEM DESCRIPTION: In DevOps Experience, objects are       *
  *                      getting created in database even        *
  *                      though  pull request is still in        *
  *                      opened state                            *
  *                                                              *
  *                                                              *
  *                      Objects are getting created in          *
  *                      mainframe even though Pull request      *
  *                      is still in opened state.               *
  *                                                              *
  *                                                              *
  *                      After applying PTF11 the job name for   *
  *                      subsystem registration job does not     *
  *                      start with the jobPrefix specified in   *
  *                      the configuration.yaml file. It gets    *
  *                      defaulted to the ssid value of the      *
  *                      target subsystem. possibly resulting    *
  *                      in difficulty finding the job output    *
  *                      and possibly also resulting in          *
  *                      permission problems. For example, you   *
  *                      may see a SECURITY_ERROR related to     *
  *                      Registration in the Status messages.    *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  The following fixes are included with this APAR FIX.
  Objects are getting created in mainframe even though Pull
  request is still in opened state. These objects got created
  on the click of apply changes, even before the merge button
  was clicked. The problem was a result of renaming the database
  and schemas to name which was unknown to the instance which is
  now fixed.
  
  
  Support for the Sequence Alias (SA type)
  in DevOps Application/Instance/Pull Request Management
  
  
  We updated the JCL templates to restore the original behavior
  of the job card so that the job prefix is being picked up from
  the configuration files in PARMLIB.
  

Problem conclusion

• Apply the PTF
  

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:

  UI81166

Modules/Macros

• IZPPTF12 IZPSERVE IZPUI
  

Fix information

• Fixed component name

  UNIFIED MGMT SV

• Fixed component ID

  5698UM100

Applicable component levels

• R110 PSY UI81166

     UP22/06/28 P F206

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.