View previous topic :: View next topic
|
Author |
Message |
padma_prakasam
New User
Joined: 06 Oct 2005 Posts: 31
|
|
|
|
Hi,
I tried running JCL having a SELECT query with DSNTIAUL. I got 818 timestamp error as below,
THE PRECOMPILER-GENERATED TIMESTAMP 17ED6C2F00B764D3 IN THE LOAD MODULE IS DIFFERENT FROM THE BIND TIMESTAMP 17E4A1381B4D0A19 BUILT FROM THE DBRM DSNTIAUL
The select query is as below,
DSN SYSTEM(DB2)
RUN PROGRAM(DSNTIAUL) PARM('SQL') -
PLAN(DSNTIAUL) LIB('DSN710.RUNLIB.LOAD')
//SYSIN DD *
SELECT EMPLOYEEID FROM
FROM AY.AYTBEMP
WHERE EMPLOYEEID > '000006000000'
AND EMPLOYEEID < '000006000200'
WITH UR;
Can anyone tell how to overcome this error??
Thanks
Padma |
|
Back to top |
|
|
Rajen
New User
Joined: 05 May 2005 Posts: 61
|
|
|
|
Hi padma_prakasam,
Have you guys upgraded DB2 version recently.
we are not using this utility but i am sure -818 would occur only if you compile the load and not bind properly.
As you are using utility which part Db2 that should not be the case of compiling and not binding properly.
Please check with your DBA and ask about any version ugradation.
Let me know if it worked or not.
Thanks,
Rajen Patel. |
|
Back to top |
|
|
satyender
New User
Joined: 05 Jan 2008 Posts: 50 Location: Olympia, WA, USA
|
|
|
|
Comment out the STEPLIB statement in the job. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
are You using the right db2 libraries ??? ask You support
Quote: |
DSN710.RUNLIB.LOAD |
it' s a pretty old db2 release there, did a migration take place in the meanwhile ??? |
|
Back to top |
|
|
n_sri_vas
New User
Joined: 17 Nov 2006 Posts: 6
|
|
|
|
HI,
the load module & plan are out of SYNC ..that's why the TimeStamps are different... you need to point to the right DBRMLIB to come out of -818. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
It sounds like you have put together your own jcl to run this.
If this is the case, i suggest you talk with your database or system support to confirm that you are using the correct jcl for your environment. |
|
Back to top |
|
|
|