IV91613: OBJECT MIGRATION COMPARE FEATURE NOT WORKING WHEN SELECTED IN BACKGROUND OPTION

APAR status

• Closed as fixed if next.

Error description

• Unable run compare on Object Migration log file on 3.5.1
  platform when selected in background option
  We you try to run a compare after loading OM package on 3.5.1
  version and it repeats the same rows into the object migration
  log file.
  It appears it kept re-running the compare (about 1 hour per
  run) multiple times and it does not work or present results.
  The problem happens when the background comparison result is
  run, and the OM package contains UX Metadata.
  

Local fix

• The workaround is to click the wait link to run the comparison
  report, instead of the background comparison report.
  Another workaround is to run the background comparison report,
  and then run the following sql to prevent the comparison to
  continuously run. (Note, in the sql replace YOUR_PACKAGE_NAME
  with the name of the OM package you ran the comparison report
  on. Also note, you will likely need to stop the Object
  Migration Agent before running this sql).
  update OM_PKG_HEADER set OM_PKG_STATUS = 12 where OM_PKG_NAME =
  'YOUR_PACKAGE_NAME'
  

Problem summary

• The issue was that UX Metadata compare has logic to grab the
  package from the session. OM logic will add the package to the
  session, if it is not already there when getPackageFromSession
  is called. This was causing a conflict when the context was
  being finalized in the compare notification logic, thus causing
  the status to continuously be set to compare in progress. The
  fix is to clean the session of the OM package if necessary
  prior to notification logic being called.
  

Problem conclusion

• Object Migration Comparison Report now works if background
  comparison is selected. Before, the comparison process would
  continuously run and never be completed.
  This is targeted to the 1h2017 release.
  

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

• 999
  

Fix information

Applicable component levels

• R352 PSY

     UP