IBM Support

PI20608: DB2 OBJECT COMPARISON TOOL FOR Z/OS, MISCELLANEOUS ENHANCEMENTS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DB2 OBJECT COMPARISON TOOL FOR Z/OS, MISCELLANEOUS ENHANCEMENTS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Object Comparison Tool      *
    *                 for z/OS.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following enhancements              *
    *                      are delivered:                          *
    *                                                              *
    *                      - The DB2 LOAD Utility options          *
    *                      are now supported by Migrate (MIG) on   *
    *                      panel ADB2UTC 'Specify Utility Options  *
    *                      - LOAD':                                *
    *                                                              *
    *                      LOG  . . . .  (Yes/No/NOC - NOCopypend) *
    *                      RESUME . . .  (Yes/No)                  *
    *                      REPLACE  . .  (Yes/No)                  *
    *                                                              *
    *                      - The DB2 LOAD Utility options are now  *
    *                      supported by ALT, Object Compare, and   *
    *                      Change Management (CM), and Migrate     *
    *                      (MIG) on panel ADB2UTC 'Specify Utility *
    *                      Options - LOAD':                        *
    *                                                              *
    *                      ERRDDN . . . .(DD name for error        *
    *                                      processing)             *
    *                      DISCARDDN  . .(DD name for discarded    *
    *                                      records)                *
    *                      DISCARDS . . .(0 to 2147483647)         *
    *                                                              *
    *                      - When a user issues the 'ALT -         *
    *                      Redefine function' line command on      *
    *                      panel ADB21F 'Functions' and attempts   *
    *                      to alter the parameter definition using *
    *                      panel ADB26CFU 'Create Function' , DB2  *
    *                      Admin erroneously allows the AS LOCATOR *
    *                      clause to be specified for parameters   *
    *                      with a non LOB data type.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following enhancements are delivered:
    
    - The DB2 LOAD Utility options are now supported by Migrate
    (MIG) on panel ADB2UTC 'Specify Utility Options - LOAD':
    
    LOG  . . . .  (Yes/No/NOC - NOCopypend)
    RESUME . . .  (Yes/No)
    REPLACE  . .  (Yes/No)
    
    - The DB2 LOAD Utility options are now supported by ALT,
    Object Compare, and Change Management (CM), and Migrate
    (MIG) on panel ADB2UTC 'Specify Utility Options - LOAD':
    
    ERRDDN . . . .(DD name for error
                    processing)
    DISCARDDN  . .(DD name for discarded
                    records)
    DISCARDS . . .(0 to 2147483647)
    
    - The AS LOCATOR clause could not be specified on panel
    ADB26CFU for parameters with LOB data type only.
    

Problem conclusion

Temporary fix

Comments

  • Enhancements delivered.
    
    Previously, the Migrate function only supported the RESUME
    YES option in the target system LOAD job. The user was not
    able to choose between options REPLACE and RESUME YES.
    This APAR enhances this functionality. The user is now
    able to determine how the data is loaded into the target system
    by customizing the value of the LOAD Utility options RESUME
    and REPLACE using the 'UO - Customize utility options' command
    and setting the option 'Use customized utility options' to YES
    on panel ADB28M 'Migrate Parameters'.
    
    The following rules determines which option is used:
    
    1. Migrate will attempt to use the customized REPLACE
    and RESUME LOAD Utility options if specified by the user.
    
    2. DB2 does not allow using LOAD REPLACE on certain
    types of tables. When LOAD REPLACE is not allowed but
    is specified, the REPLACE option is converted to RESUME
    YES. Warning message ADB7001W will be issued in the
    LOAD statements conversion step with job return code 4.
    
    3. If not all the tables under a multi-table table space are
    selected for migration on the source system, the REPLACE
    option for LOAD utility, if specified, is converted to
    RESUME YES. Warning message ADB7001W will be issued in the
    LOAD statements conversion step with job return code 4.
    
    4. If all the tables under a multi-table table space are
    selected for migration on the source system, the REPLACE
    option for LOAD utility, if specified, is used. Any
    additional tables under the table space on the target
    system remain empty after migration. Warning message
    ADB7002W will be issued in the LOAD statements conversion
    step with job return code 4.
    
    5. If customized utility options for RESUME and REPLACE
    are not used, Migrate will use the RESUME/REPLACE
    option in the LOAD control statement generated by the
    DB2 UNLOAD Utility or HPU.
    
    New messages:
    
    ADB7001W  The REPLACE keyword in the LOAD control
    statement for table table_name is converted to RESUME YES.
    Reason reason_code.
    
    Explanation: DB2 restrictions on LOAD REPLACE require
    a change to the LOAD control statement. The reason code
    indicates the source of the error:
    
    01. The table to be loaded is a system-period temporal table
          with data versioning define.
    02. The table to be loaded is an archive-enabled table.
    03. The table is under a multi-table table space and not all
          the tables under the table space are migrated.
    
    System action: Processing continues.
    
    User action: Review the the LOAD control statement for the
    specified table, particularly the REPLACE keyword. Correct
    the statement, if necessary, and try again.
    
    ADB7002W The LOAD REPLACE option is applied to the
    multi-table table space ts_name. Any additional tables in
    the target table space are left empty after migration.
    
    The LOAD REPLACE option is applied to the multi-table
    table space  ts_name. Any additional tables in the target
    table space are left empty after migration.
    
    Explanation: The LOAD REPLACE option is applied to the table
    space as specified in the LOAD Utility options because all the
    tables under the table space are selected for migration on the
    source system. Any additional tables in the table space on the
    target system are left empty after migration because the LOAD
    REPLACE option is used.
    
    System action: Processing continues.
    
    User action: Confirm that it is appropriate to use the LOAD
    REPLACE option before submitting the target jobs.
    
    User's Guide updates:
    
    Updates to the DB2 Administration Tool for z/OS Version 11,
    Release 1 User's Guide and Reference, under Section 'Step 2.
    Generate batch  jobs' of Chapter - 'Migrating DB2 objects,
    data, views, and catalog statistics' can be found via
    the following link:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg27041314
    
    - Since REPLACE and RESUME YES are mutually exclusive option,
    a user specified option overrides PUNCHDDN settings at run-time
    for each load statement.
    
    The REPLACE option is converted to RESUME YES when the table is
    version-enabled temporal and archive table.
    
    If there is a table space that contains multiple tables, the
    REPLACE option is disabled and RESUME YES is added at run time.
    DB2 Object Compare unloads and loads the table data when the
    table is dropped and recreate. When all tables in a table space
    are dropped and recreated, the table space becoming empty is
    equivalent to applying the REPLACE option.
    
    The following warning message will be displayed to inform the
    user of this behavior:
    
    ADB5262W
    The REPLACE keyword in the LOAD control statement for table
    tbname is converted to RESUME YES. Reason reason_code
    
    Explanation: The REPLACE keyword in the LOAD control statement
    is converted to RESUME YES. Reason reason_code.
    
    01. The table to be loaded is a system-period temporal table
        with data versioning.
    02. The table to be loaded is an archive-enabled table.
    03. The table is in a multi-table table space.
    

APAR Information

  • APAR number

    PI20608

  • Reported component name

    DB2 OBJECT COMP

  • Reported component ID

    5697G6400

  • Reported release

    B10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-24

  • Closed date

    2014-07-16

  • Last modified date

    2014-08-04

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

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

Modules/Macros

  •    GOCGCMP
    

Fix information

  • Fixed component name

    DB2 OBJECT COMP

  • Fixed component ID

    5697G6400

Applicable component levels

  • RB10 PSY UI19667

       UP14/07/21 P F407

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUVH","label":"IBM Db2 Object Comparison Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 February 2021