PI72728: DB2 OBJECT COMPARISON TOOL FOR Z/OS FOLLOW-ON PTF.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 OBJECT COMPARISON TOOL FOR Z/OS FOLLOW-ON PTF.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When analyzing a change there is an     *
  *                      option to generate a recover change     *
  *                      which will reload either the original   *
  *                      or existing data. The option to         *
  *                      generate both types of recover jobs     *
  *                      to accommodate an unplanned scenario    *
  *                      has been added.  Also, an option to     *
  *                      recover DDL only without recovering     *
  *                      the data is added.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Enhance recover of a change by providing an option
  during Analyze to generate a recover change which will
  reload either the original or existing data, or DDL
  only.
  

Problem conclusion

• New options of recovering a change have been added
  to the analyze change process.   Both the panels and
  CM batch have been updated to allow two new recover
  change options,  'B' for both original and existing
  data and 'N' for no data recover - DDL only recovery.
  Also a new option is added recover_withDDL, that
  will also allow DDL only recovery alongside the data
  recovery.
  
  For the CM Panels Path
  ------------------------------
  Possibility to specify 'B or Both' or 'N or None' for the
  existing analyze panel option  'Data to recover' on
  panel ADB2C11A 'Generate Analyze Job':
  
  Data to recover . .  O  (Original, Existing, Both or None )
  
  The combinations will generate 0 or more jobs:
  O - with Original Data
  E - with Existing Data (default)
  B - Two jobs one for Original and one for Existing data
  N - No recover jobs dealing with data option.
  
  New input field for 'Recover with DDL only' option on panel
  ADB2C11A:
  
  Generate a recover change . YES      (Yes/No)
    Data to recover . . . . . O        (Original, Existing,
                                        Both or None )
    Recover with DDL only . . Y        (Y/N)
  
  This will generate a recover job that can only recover the DDL
  without dealing with data.  This recover job will be in
  addition to the recover jobs generated by the Data to recover
  options O, E, or B.
  
  Help panel ADBHC11A has been updated for the data to recover
  option and the new recover with DDL only option.  The
  updates are below:
  
  Data to recover      The data that the recover
                       change recovers:
  
        Both     - Allow the possibility to recover with
                   the 'Original' or 'Existing' data at
                   the time of recovering the change.
  
        None     - Do not recover the data at the time of
                   recovering the change.
  
  Recover with DDL only      Recover the DDL
                             and do not recover the data.
  
        If tables are dropped and recreated during recover
        process, existing data will be unloaded into a
        data set, however data will not be loaded back
        into the tables if the job generated with this
        option is used when recovering a change.
  
  During CM recover, after typing 'RC' next to the
  change that is to be recovered on panel ADB2C11
  'Changes', a popup confirmation panel will appear
  if a recover choice is required.
  
  The options allowed will be shown on the panel
  and the user needs to pick one of the options.
  This popup panel will be shown if the change
  had recover options 'Data_to_recover = B' and/or
  if recover with DDL only was set to 'Y - yes'.
  
  For the CM batch Mode
  _____________________
  
  Existing parameter, 'data_to_recover', will be updated
  to allow 4 different recover scenarios.  The 4 choices
  for this parameter are:
  
  'O' -   Existing option,  set up recover with original data
  'E' -   Existing option,  set up recover with existing data
  'B' -   New option,  set up recover for both original data
          and existing data
  'N' -   New option,  do not set up recover for any data
          options ( this option would go with a 'Y' option for
          new parameter,  recover_withddl  )
  
  Also, the story adds the ability to recover the DDL only and
  not worry about the data ( user would load their own data
  after recovery).  This new option will use a new CM batch
  parameter,  'recover_withDDL'.
  
  This parameter has two options:
  
  'Y'  allow customer to recover the DDL only
  'N'  no recover DDL only allowed
       NOTE:  this option can not be combined with
       option data_to_recover = N (an error, ADB9751E,
       will be issued when it is combined).
  
  Another new CM batch parameter,  Recover_option, that is only
  allowed if recover_withDDL is 'Y' or if data_to_recover = 'B'
  or 'N'.  It has the following options:
  
  'O'  -  recover using the original data
  'E'  -  recover using the existing data
  'D'  -  recover DDL only
  
  When using CM batch to perform an analyze,  parameters
  'data_to_recover' and 'recover_withDDL' can be used.
  
  When using CM batch to perform a recovery,  parameter
  'Recover_option' can be used.   If it isn't used and
  'data_to_recover' was 'B' or 'N',  then error ADB9752E
  will be issued, otherwise,  the recover set up (either 'O'
  or 'E' ) will be used.  If recover_option is a choice that
  was not used during recovery job generation time,  an error
  will be issued.
  
  There are four new options for 'Admin_dataset_type'
  CM batch parameter to allow a user to pass their own
  dataset template for CHG and IFF datasets used when
  DATA_TO_RECOVER = 'B'.
  
  The options are 'IFF_RO, IFF_RE, CHG_RO, CHG_RE'.
  The user can specify these types in the CM batch JCL to tell
  DB2 ADMIN to use these data sets instead of the ones the
  DB2 ADMIN would create for CHG and IFF files.
  
  CM batch parameter changes below:
  
  data_to_recover
  
  The data_to_recover parameter specifies the type of
  data that the recover change recovers.
  Values:
  O
  Recover using the original data. The original data is
  the data that is unloaded when the original change is
  run. If you use the original data during a recovery
  operation, you might consider whether related tables
  that were not affected by the recover also must be
  restored to the same point to avoid inconsistencies.
  This option applies only to tables that were dropped
  in the original change and created in the recover change.
  E
  Recover using the existing data. If a table is dropped
  without being re-created in the original change, no data
  is loaded after the table is created in the recover change.
  B
  Set up recover to allow the option to recover either 'O' or 'E'
  at the time of recover.   Both options will be saved in the
  recover change so they can be used at recover time.
  N
  Do not use any data to do recover.   This option will allow
  ddl only recover.
  
  Default:
  E
  
  recover_withddl
  
  The recover_with_ddl_only parameter specifies whether
  recover change can recover using ddl only and no data.
  Values:
  Y
  Recover change can recover using ddl only and ignore data.
  N
  Recover change can not recover using ddl only.
  Default:
  N
  
  recover_option
  The recover_option  parameter specifies the type of recover
  that the recover change process will do.
  Values:
  O
  Recover using the original data. The original data is the
  data that is unloaded when the original change is run. If
  you use the original data during a recovery operation, you
  might consider whether related tables that were not affected
  by the recover also must be restored to the same point to
  avoid inconsistencies. This option applies only to tables that
  were dropped in the original change and created in the
  recover change.
  E
  Recover using the existing data. If a table is dropped without
  being re-created in the original change, no data is loaded
  after the table is created in the recover change.
  D
    Recover with DDL only and ignore data.
  
  Default:
  blank     Recover using the option specified during set up of
  recover change.   This is not valid if the recover change was
  set up with data_to_recover = 'B'.
  
  New messages created are
  
  ADB9751E
  Message:The data_to_recover parameter name is set to N and
  the recover_withddl parameter name is set to N.  Both of these
  values can not be N.
  User action:  If data_to_recover is set to N, then
  recover_withddl should be set to Y.
  System action:  Processing stops.
  
  ADB9752E
  Message:The data_to_recover parameter name is set to B
  and the recover_option parameter name is not given.
  User action:  If data_to_recover is set to B, then a
  recover_option of O, E, or N needs to be given.
  System action:  Processing stops.
  

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:

  UI43765

Modules/Macros

•    GOCGCMP
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• RC10 PSY UI43765

     UP17/01/18 P F701

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.