|
View previous topic :: View next topic
|
| Author |
Message |
chandrupegasus
Warnings : 1
New User
Joined: 16 Jan 2007
Posts: 11
Location: Bangalore
|
|
|
|
| Quote: |
if you are modifying the program and if you are not binding it, you will get a timestamp mismatch error.
Thanks,
Anu |
Ur comment is fine about If anything changed in the modified source code, without rebind , We'll get timestamo mismatch, but one more part is pending in the question, Without changing anything in the code, If I rebind , Will I get timestamp mismatch error? Pls clarify. |
|
| Back to top |
|
 |
nabarundas
New User
Joined: 21 Jun 2007
Posts: 28
Location: pune
|
|
|
|
hi chandrupegasus,
Plz try to understand the compilation procedure of a COBOL-DB2 program. When you compile your program the precompiler will replace the SQL code with COBOL Call statement where it provides a timestamp to identify the SQL statements later on.
So If you compile your program even without making any changes in your code you need to BIND it again as the precompiler has put different Timestamp over there.
If you haven't compiled it then the timestamp in the DBRM and the program will always be the same. Hence no need of bind it again.
Regards,
Nabarun |
|
| Back to top |
|
|
rakhi asthana
New User
Joined: 24 Oct 2007
Posts: 1
Location: pune
|
|
|
|
| thanks for your information!! |
|
| Back to top |
|
|
Anurag Paul
New User
Joined: 12 Feb 2011
Posts: 1
Location: Chennai
|
|
|
|
But what about the time stamp error in DB2 when we are using it in a cics program????
I am putting breakpoints in the module and giving values for a particular timestamp for a record in DB2 , but its showing a -180 sqlcode.... whenever its matching with the record |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
Why do you believe your problem is related to this topic? It is not. . .
Did you look up the -180 sql code? I suppose not. . .
From the manual:
| Quote: |
-180 THE DATE, TIME, OR TIMESTAMP VALUE value IS INVALID
Explanation: The length or string representation of a DATE, TIME, or TIMESTAMP value does not conform to any valid format. |
Suggest you give proper values rather than invalid values. |
|
| Back to top |
|
|
|
|
