|
View previous topic :: View next topic
|
| Author |
Message |
mfhelp
Warnings : 1
New User
Joined: 29 Jun 2006
Posts: 33
|
|
|
|
| What is the difference between -805 and -818 SQL code........can we really face -818 in real projects?? |
|
| Back to top |
|
 |
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
| What does your manual say? |
|
| Back to top |
|
|
UmeySan
Active Member
Joined: 22 Aug 2006
Posts: 771
Location: Germany
|
|
|
|
Hi !
First: nothing found in Plan.
Second: Found in Plan but TS is different.
And as gnanas said: RTMF
Regards, UmeySan |
|
| Back to top |
|
|
zero
New User
Joined: 01 Dec 2007
Posts: 21
Location: Hyderabad
|
|
|
|
The descriptions for -805 and -818 are :
SQLCODE -805 : DBRM OR PACKAGE NAME NOT FOUND IN PLAN
SQLCODE -818 : THE PRECOMPILER-GENERATED TIMESTAMP IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP BUILT FROM THE DBRM.
As you know, all the SQL statements that are written in a program will be moved to DBRM (Data Base Request Module) and will be binded and then stored in a Package/Plan.
if a DB2 Program is not compiled properly, and if we try to run it -805 will be generated.
now, coming to SQLCODE : -818. As you know, when a DB2 Program is compiled, two entities will be created at the end of compilation.
1. Load module which contains just the source language statements.
2. Plan/Package that contains all the SQL statements in executable
format that are coded in the program. (When a DBRM is binded, the
executable form Of the SQL statements will be created and stored in
Plan/Package.
To make sure that the program calls the correct SQL statements, we
use an identifier in both the Load module and Plan/Package. Generally,
a timestamp is used for this purpose. this is the default. |
|
| Back to top |
|
|
|
|
