Consistency token is a unique identifier stored in the SQL package at
program/package creation time. When you move that SQL package to the remote
box and subsequently use remote connection, DB2 checks that consistency
token at the local & remote box are identical. If they're different, DB2
interprets it as something has dramatically changed on the local box
potentially causing rebuild of access plans. Since it thinks access plans
are different, it forces you to update the remote box as well.

Bottom line, just copy the SQL package from the local box.

Here is a link on the topic:

http://tinyurl.com/3da8no

OR

http://search400.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid3_gci
1271065,00.html

HTH, Elvis.

Mike Cain - DB2 for i5/OS Temporary Indexes - The Good, The Bad, The Ugly
October 16
2007 System i Fall Technical Conference | Orlando | November 4-7
Celebrating 10-Years of SQL Performance Excellence on IBM System i, eServer
iSeries and the server affectionately known as the AS/400

-----Original Message-----
Subject: SQL0818-Consistency tokens do not match.

I have a development lpar Mimixed over to a backup development lpar on a
different box.
I have a SQLRPGLE program. It has it's accompanying *SQLPKG
Object Type Library Attribute
GDSSYS001 *PGM ROUTINES RPGLE
GDSSYS001 *SQLPKG ROUTINES PACKAGE
It does a lot of "CONNECT TO". When it tries connecting to the
development lpar I am getting:
SQL0818
Message . . . . : Consistency tokens do not match.
Cause . . . . . : Package GDSSYS001 in ROUTINES on application server
GDISYS2 cannot be run with the current application program because
either
the application program has been recompiled without rebuilding the
package
or the package has been restored from a back level version.
Recovery . . . : Rebuild the package by using the CRTSQLPKG command or
by
using a CRTSQLxxx command specifying the correct relational database.
Otherwise, restore the package from a version which matches the
application
program being run.
From program . . . . . . . . . : QSQROUTE
From library . . . . . . . . : QSYS
From module . . . . . . . . : QSQROUTE
From procedure . . . . . . . : NORMEXIT
From statement . . . . . . . : 18116
To program . . . . . . . . . . : QSQROUTE
To library . . . . . . . . . : QSYS
To module . . . . . . . . . : QSQROUTE
To procedure . . . . . . . . : NORMEXIT
To statement . . . . . . . . : 18116

It communicates to other lpar's with no problem.

Rob Berendt



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].