Consistency token in load module

santsark · New User Joined: 08 Aug 2008 Posts: 9 Location: Kolkata

Where can i exactly find the consistency token in the load module?

I'm getting a -805 with reason code 003. As per the explanation this is due to consistency token mismatch. I see 3 entries in syspackage table for the package but how do i verify the consistency token mismatch.

Thanks
Santanu

dbzTHEdinosauer · Posted: Thu Aug 14, 2008 1:33 pm

if you don't know enough to know about the consistancy token, why don't you just rebind (or bind it properly).

reason that I say that is because what use do you have of finding the consistancy tokens? So that you can prove to yourself that db2 has not made a mistake.

you could be invoking a module from a loadlib that has not been bound.

believe me, db2 is pretty good about being accurate with this type of thing.

If you are intent on beating a dead horse, read the manuals. somewhere, someplace the consistancy toke is explained. besides, the 'token' in the load module and the 'token' in the plan do not look the same. db2 manipulates the data in one or the other before it make the compare and tells you that you did not bother to follow the proper procedures.

yes, someone could have deleted the bindplan in the db2 tables thus causing you to suffer from an -805, but since it isn't there, you can't prove it anyway.

dbzTHEdinosauer · Posted: Thu Aug 14, 2008 2:30 pm

Santanu,

sort of a half baked apology for my tone in my previous post:

at my shop, the endevor support people have provided us with jcl
(that we must use)
that only gives >0 return codes for pre-compiler and compiler errors.
a bind error would return 0 return-code.
that means we always have to look at the output of the bind steps to
insure that there was a successful bind - otherwise we receive -805's.

That could be your problem.

wanderer · Posted: Sat Aug 16, 2008 6:19 am

Santanu,

Goto SYSPACKAGE and display the column CONTOKEN in hex. Of the 16 characters displayed, take the first 8 from left and do a find in your load module for those 8 in hex e.g. f x'A5E678CF'. Then do the same for the other half of 8 from syspackage contoken. In both cases you should find a match. If not then load differs from DBRM.