The consistency token between your application program and DB2 does not match.
Consistency Token in COBOL programs
Consistency token maybe found just prior to the PROCEDURE DIVISION. Data name for the two part token are SQL-TIMESTAMP-1 and SQL-TIMESTAMP-2. You may use the Quikjob in
D9747.DBA.JCLLIB(DB2TOKEN) to convert the binary timestamp to hex format.
Example 01 SQL-PLIST6. 05 SQL-PLIST-CON PIC S9(9) COMP-4 VALUE +2621440. 05 SQL-CALLTYPE PIC S9(4) COMP-4 VALUE +50. 05 SQL-PROG-NAME PIC X(8) VALUE 'G88DB2 ' 05 SQL-TIMESTAMP-1 PIC S9(9) COMP-4 VALUE +368085974. 05 SQL-TIMESTAMP-2 PIC S9(9) COMP-4 VALUE +109166632. 05 SQL-SECTION PIC S9(4) COMP-4 VALUE +1. 05 SQL-CODEPTR PIC S9(9) COMP-4. 05 SQL-VPARMPTR PIC S9(9) COMP-4 VALUE +0. 05 SQL-APARMPTR PIC S9(9) COMP-4 VALUE +0. 05 SQL-STMT-NUM PIC S9(4) COMP-4 VALUE +134. 05 SQL-STMT-TYPE PIC S9(4) COMP-4 VALUE +3.
Consistency Token in the DBRM
Consistency token maybe found at position 25 thru 32 of the first record
The first four bytes is SQL-TIMESTAMP-1 and the last four bytes is SQL-TIMESTAMP-2.
Example:
--------------------------------------------------------------------------------
(---+---10----+---20----+---30----+---40----+---50----+---60----+---70----+---80
--------------------------------------------------------------------------------
DBRM µXB3GDH G88DB2 0»O a{ 2
1 0 F
CCDD000AECFCCC44CFFCCF441F8D08C200F000000000000000000000000000000000000000F0080C
42940000723748007884220050B66108602002000000000000000000000000000000000000100006
--------------------------------------------------------------------------------
Consistency Token in DB2 Package:
Consistency token maybe obtained by running the following query:
SELECT CONTOKEN FROM SYSIBM.SYSPACKAGE WHERE NAME ='xxxxxxxx'
xxxxxxxx = package name
Be sure to display the results in hex format