PH72561: COMPARE OBJECTS BETWEEN SEPARATED ENVIRONMENTS USING VERSION FILES

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Customer uses Admin Tool and CM batch extensively when migrating
  object changes from one environment to another. In most cases it
  works well to do it using DDF or generating the DDL from source
  and compare that to target. They have one case though where it
  does not work as good as should.
  
  Their development and production environments are strictly
  separated.  They cannot connect between them in any way and have
  separate installations of Admin Tool in them. The only way for
  them is to use FTP. That means that when they migrate a change
  from the QA Db2 to Prod Db2 they have to do this in several
  steps:
  
  Generate the DDL from source in Dev
  FTP the output DDL to Prod
  Do the compare in Prod using CM batch
  Perform the change using CM batch
  This problem will be fixed by allowing user to compare Version
  Files created in each environment and perform the change from
  that compare.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 Administration Tool for z/OS    *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR adds support for version      *
  *                      file-to-version file comparisons in     *
  *                      Change Management (CM) batch.           *
  ****************************************************************
  New options were added for the SOURCE_TYPE and TARGET_TYPE CM
  batch parameters to support version file-to-version file or
  version file-to-catalog comparisons.
  
  The following value is added for the SOURCE_TYPE CM batch
  parameter:
   VF    The source is a Db2 Admin Tool version file.  To
  specify the data set that contains the version file, use the
  compare source input file (SRCIN DD) or the SOURCE_DSN
  parameter. If the SOURCE_DSN parameter is not specified, the
  compare source input file (SRCIN DD) must be preallocated.
  
  The following new value is added for the TARGET_TYPE CM batch
  parameter:
  VF    The target is a Db2 Admin Tool version file. To specify
  the data set that contains the version file, use the compare
  target input file (TGTIN DD) or the TARGET_DSN parameter. If
  the TARGET_DSN parameter is not specified, the compare target
  input file (TGTIN DD) must be preallocated.
  Attention: If the target version file objects that are
  specified do not match the DDL in the Db2 database catalog,
  problems might occur when running the resultant change.
  Therefore, consider using this option only when comparing
  VF/DDL to VF/DDL (TARGET_TYPE='VF' or 'DDL' and
  SOURCE_TYPE='VF' or 'DDL').
  
  The following new error message is issued when the data set
  specified as a version file does not have the version file
  data set attributes:
    ADB9979E The data set 'source.dsn' does not have the correct
  LRECL, RECFM or DSORG for a version file.
  Version files require LRECL of 16384, RECFM=VB and DSORG=PS.
  Dataset type: 'dataset type'
  

Problem conclusion

Temporary fix

Comments

• The enhancement has been delivered.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UO08896

Modules/Macros

• ADB9000  ADBCCM   ADBEAPI0
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RD10 PSY UO08896

     UP26/08/07 I 1000  

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.