IBM Support

PH55450: Admin tool should catch SCHEMA mismatch in DDL for AUX and base tables pre-masking

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If source DDL is missing SET CURRENT SCHEMA statement, Admin
    tool should identify the schema mismatch for the base table in
    the Auxiliary table version file record. The compare should
    error out and a message should be issued regarding the schema
    mismatch. This issue happens if the SCHEMA mask is incorrectly
    used to connect 2 objects that don't have the same schema at the
     time of definition.
    

Local fix

  • Add the correct SET CURRENT SCHEMA statement before the CREATE
    objects
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the Db2 Administration Tool for     *
    *                 z/OS who use SCHEMA masking.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a DDL has unqualified objects and    *
    *                      no SET CURRENT SCHEMA, using a          *
    *                      universal schema mask can cause         *
    *                      compare to incorrectly apply the        *
    *                      masking to objects that are not         *
    *                      correctly linked. This results in wrong *
    *                      WSL for Auxiliary and base tables in    *
    *                      the DDL.                                *
    ****************************************************************
    If the source DDL does not have qualified objects and is also
    missing a SET CURRENT SCHEMA statement, a universal
    SCHEMA mask will improperly try to assume a Auxiliary and
    base table relationship that has not been established during
    DDL processing. This will result in an incorrect WSL. Compare
    should error out instead, so the user can make the needed
    changes to the source DDL to add the SET CURRENT SCHEMA
    statement.
    
    ADB7411E: <SCHEMA>.<NAME> of base table for auxiliary table
    does not match that of the existing base table record.
    
    Search Keywords: SCHEMA masking
    

Problem conclusion

  • The current behavior has been addressed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH55450

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-06-27

  • Closed date

    2023-10-16

  • Last modified date

    2023-11-01

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

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

    UI94028 UI94029

Modules/Macros

  • ADB2CMR  ADB7000
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • RC10 PSY UI94028

       UP23/10/18 P F310

  • RD10 PSY UI94029

       UP23/10/18 P F310

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.1.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 November 2023