IBM Support

IT29967: DB2LK390.BND IS BOUND ON Z/OS WITH THE SAME PACKAGE NAME BUT DIFFERENT CONTOKENS FOR DIFFERENT DB2 CLIENT LEVELS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a remote db2look is used to generate DDL from DB2 on Z/OS,
    it requires db2lk390.bnd to be bound on Z/OS.
    
    
    For some different DB2 Clients Levels the same Package Name is
    used but the Consistency Token is different, eg :
    
    db2lk390.bnd       COLLID NAME        CONTOKEN
    ---------------       -------   ----------   ----------------
    V11.1.3.3_37416 NULLID  DB2L1O03 5F33373431360000
    V11.1.4.4            NULLID  DB2L1O03 3039313430300000
    V11.1.4.4_38115 NULLID  DB2L1O03 5F33383131350000
    V11.1.4.4_38513 NULLID  DB2L1O03 5F33383531330000
    
    
    Since the Package Name is unique the package has to be
    regenerated if one of these Clients at a different level wants
    to run the remote db2look and this can cause conflicts.
    
    CONTOKEN should stay the same across builds.
    When the source file changes the SQL within, both the NAME and
    the LEVEL should be updated in sync.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29967

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-12

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020