PH66519: UPDATE THE INSTANCE MANIFEST WHEN "ADD OBJCT"/"APPLY" JOB FAILS TO RUN A DB2 UTILITY BUT THE CHANGES WERE ACTUALLY APPLIED TO DB

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Instance manifest and objects DDLs in DOE GIT repo does not get
  updated when "add object"/"apply" job fails to run a Db2 utility
  but the changes were actually applied to Db2 catalog. The only
  way to get them added/updated in DOE after that is to use the
  option "add existing object from target" because the second run
  of the same job after fixing the problems does not pick up the
  changes.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users for Db2 DevOps Experience for z/OS     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Update the instance/application         *
  *                      manifest in case if the job has failed  *
  *                      but the changes were actually applied   *
  ****************************************************************
  User to get the application/instance manifest updated even if
  the CMBATCH job has failed due to error that does not affect the
   actual object changes. In this case the changes were actually
   applied to the objects in the catalog.
  

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

• DOEOPPAX DOEVRPAX
  

Fix information

• Fixed component name

  DB2 DEVOPS EXPR

• Fixed component ID

  5698DEX00

Applicable component levels

• R130 PSY UO05308

     UP25/10/18 P F510

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.