| View previous topic :: View next topic |
| Author |
Message |
THRIVIKRAM
Beginner
Joined: 03 Oct 2005
Posts: 70
Topics: 34
|
 Posted: Sat Jun 24, 2006 2:40 am Post subject: S000 U4094=>SQl -805 |
 |
|
Hi all,
I got the SQL -805 error while running a DB2 program.I searched the links
http://mvsforums.com/helpboards/viewtopic.php?t=368&highlight=sql+805 and also http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DSNMCH11/2.1.6.378?SHELF=&DT=20010718150520 as KOLUSU suggested. But Could not figure out the problem.
The SYSOUT message was:
PROGRAM F5938UPT COMPILED ON 06/11/0411.45.16 VERSION 001
ERROR ON CURRENT DATE
PROGRAM IS TERMINATING DUE TO ERROR : -805
SQLERRLC:GRNPROD..F5938UPT.176B4FD118668FF0 F5938BRP 03
CEE3250C The system or user abend U4094 R=NULL was issued.
1)This program was moved into production on 14thJuly2006.This program is already present in the production.But we made few changes to it and again moved into production. But the COMPILED ON date is not matching the production move date.
2)We bind the element to a Package instead of PLAN and pass the package name to the runjcl through a PARM(This is the regular procedure that we follow).
Typically,
The Bind Parm looks like,
BIND PACKAGE(F5938_PB_PROV)
OWNER(F5938#1)
QUALIFIER(F5938DB)
MEMBER(F5938UPT)
VALIDATE(BIND)
ISOLATION(CS)
RELEASE(COMMIT)
ACTION(REPLACE) RETAIN
ENABLE(*)
EXPLAIN(YES)
FLAG(I)
CURRENTDATA(NO)
SQLERROR(NOPACKAGE)
The LinkParm looks like,
MODE AMODE(31),RMODE(ANY)
INCLUDE SYSLIB(DSNALI)
NAME F5938UPT(R)
The Parm that we pass to runjcl is(Package name)
DB2G F5938BRP
The above package name is same for all the DB2 programs.
3)Based on the SYSOUT and following the link http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DSNMCH11/2.1.6.378?SHELF=&DT=20010718150520,
I got the following results on executing the SQL querries(Problem Determination) in thes specified sequence
a)
PLCREATOR PLNAME NAME VERSION
--------- -------- -------- ------------------------------
F5938#1 F5938UPT F5938UPT 2004-06-11-15.45.15.082303
b)No row selected
c)NAME CURRENTSERVER
-------- ----------------
F5938UPT
d)No row selected
e)No row selected
I used dbrm-name as F5938UPT
Plan name as F5938UPT(Though Iam not sure)
Consistency token as 176B4FD118668FF0 F5938BRP 03
Please help in solving this problem.
Thanks,
Thrivikram. |
|
| Back to top |
|
 |
shekar123
Advanced
Joined: 22 Jul 2005
Posts: 528
Topics: 90
Location: Bangalore India
|
| Posted: Sat Jun 24, 2006 10:34 pm Post subject: |
|
|
THRIVIKRAM,
I have some info about SQL CODE -805.Try out the User Responses and hope it helps:
| Code: |
REASON:
PROGRAM NAME location name.collection id.program name.consistency token NOT FOUND IN PLAN plan name
DESCRIPTION:
An attempt was made to execute the application program 'location name.collection id.program name.consistency token' (this token can be 'location name..program name.consistency token' if the current package set special register is blank for the local program execution) that has not been found due to one or more or the following reasons: * The program 'program name' has not been bound as the member part of the application plan 'plan name' or * The 'collection id' in the PKLIST was not correct when the application plan 'plan name' was bound or * The current package set special register was not set correctly or * The 'location name' in the CURRENTSERVER was not correct when the application plan 'plan name' was bound, or * The application was not connected to the proper location or * The location id in the package list was not correct when the application 'plan name' was bound or * The DBRM of the version of the application program being executed was not bound.
SYSTEM ACTION:
The statement cannot be executed.
USER RESPONSE:
Based on the above reasons, the programmer can perform the following operations to correct the error. * Bind the program 'program name' as the member part of the application plan 'plan name' or * Correct the collection id in the PKLIST and bind the application plan 'plan name' or * Set the current package set special register correctly or * Put the correct 'location name' in the CURRENTSERVER of the BIND command and bind the application plan 'plan name' or * Connect to the correct RDB name or * Correct the location id in the PKLIST and bind the application plan 'plan name' or * Bind the DBRM of the version of the application program to be executed
|
_________________
Shekar
Grow Technically |
|
| Back to top |
|
|
THRIVIKRAM
Beginner
Joined: 03 Oct 2005
Posts: 70
Topics: 34
|
| Posted: Tue Jun 27, 2006 5:08 am Post subject: |
|
|
| I did see the same thing in the HELP. But sorry to say, I could not understand the crux. |
|
| Back to top |
|
|
ramesh161
Beginner
Joined: 09 May 2006
Posts: 5
Topics: 0
|
| Posted: Tue Jul 04, 2006 6:22 am Post subject: |
|
|
| If the package is not bounded properly, then it will give this error. So once again the bind package needs to be done using the valid user id. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
