|
Problem IT29967
|
Status: Closed |
DB2LK390.BND IS BOUND ON Z/OS WITH THE SAME PACKAGE NAME BUT DIFFERENT CONTOKENS FOR DIFFERENT DB2 CLIENT LEVELS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem 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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.08.2019
16.01.2020
16.01.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
