|
View previous topic :: View next topic
|
| Author |
Message |
Steve Little
New User
Joined: 11 Sep 2008
Posts: 2
Location: Tampa
|
|
|
|
Not sure if it's called the timestamp but this is the field following the member name field in the DBRM. To verify that a DBRM and LOAD match to prevent 805’s in the field we verify that the TS in the 8 byte field following the 8 byte name field in the precompiled DBRM can be found in the LOADLIB and MATCHES before shipping it out. After going to R7 if we take that HEX timestamp and search for it in the LOAD we don’t find a match. Even when searching for only 4 bytes we don’t find a match.
BSSPS36 F ý
CEEDEFF4151C0218
222723608F96966D
The above might not have lined up correctly. Sorry.
If I then go to the LOAD and turn HEX on and do the find command F x’185F19C6’ no HEX string like that is found. Prior to R7 it was found.
Anyone have any idea if maybe compile parms need to be changed or even if IBM has changed how we can verify a DBRM matches the LOAD that went through the IBMZPLI compiler? Thanks!!! |
|
| Back to top |
|
 |
Steve Little
New User
Joined: 11 Sep 2008
Posts: 2
Location: Tampa
|
|
|
|
| I found out the field I called the timestamp is actually the "consistency token" which starts in column 25. Hope that helps get me an answer. Thanks. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello Steve and welcome to the forums,
You might look at this previous topic (the last entry) and see if it helps:
ibmmainframes.com/viewtopic.php?t=33400
If you use the forum SEARCH in the db2 part of the forum, there are several topics that mention the consistency token. |
|
| Back to top |
|
|
|
|
