PK52932: GOC5 GENERATE APPLY JOBS = NO GIVES INCORRECT OUTPUT WHEN USED AS A DELTA AND IMPORTED TO NEW SYSTEM DOCUMENTATION CONFUSING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When using Object Compare and specifying ' No ' to the option in
  GOC5 of 'generate apply jobs ', the results were confusing.
  User tried to use output as a delta file and 'mported it to a
  new system. Results were not what was expected.
  When user specified ' YES ' to the option 'generate apply jobs '
  in the GOC5 panel and registered the change in CM ( Change
  Management ) and then used the delta files and imported to the
  new system, results were as expected.
  The help screens and documentation in the manuals need to warn
  and educate the user regarding the NO option.
  The correct way to build the delta for importing is to use the
  YES option for 'generate APPLY jobs.
  

Local fix

• Please apply ptf when available and review help screens after
  ptf is applied.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Object Compare.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Object Compare help panel GOC5H lacks   *
  *                      clarification when Generate Apply       *
  *                      Jobs=NO option is used.                 *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  The following clarification has been added to help panel GOC5H
  regarding the usage of the Generate Apply Jobs=YES/NO option
  from panel GOC5:
  
  Generate Apply Jobs=Yes - Will generate jobs to apply the
  changes found during compare to the target.  Change Management
  (if enabled) will be prompted/applied.
  
  Generate Apply Jobs=No  - Will not generate apply jobs.  Change
  Management (if enabled) will not be applied since there are no
  registered changes.
  
  Note:
  There is a difference in creating a change directly from an OC
  Run as opposed to Importing an OC CHANGES File: In an OC Run
  (running OC generated apply jobs), the changes to the object
  structure are registered as change statements in a change. Only
  when the change is analyzed, the WSL to apply the change is
  generated. The WSL contains special ADMIN commands to unload and
  reload data. Essentially,  no DROPs take place with this
  approach which otherwise would drop the data. When the NO option
  is used to not generate apply jobs, a user may later attempt to
  Import an OC CHANGES File as a change. Take caution with this
  approach as it will NOT necessarily yield the same result as
  that of the OC Run. The file is processed by import in the way
  that DDL is passed through and registered in the change and
  everything else is discarded (e.g. the UNLOAD info).  The main
  difference when running this change is that DROP statements
  really means DROP so the object plus all child objects
  (including data) are dropped just as if processed by SPUFI.
  So, after the DROP, there is no data to reload.
  

Problem conclusion

• Incident is now resolved.
  

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

•    GOC5H
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK37995

     UP08/07/17 P F807

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.