View previous topic :: View next topic
|
Author |
Message |
Vishwamurthy
New User
Joined: 11 Mar 2008 Posts: 57 Location: India
|
|
|
|
I get a similar STATUS: -0805 error. Below are the error details:
DBRM OR PACKAGE NAME
DB2SSID..PROGRAM.<HEX> NOT FOUND IN PLAN PROGRAM.
I tried 1. Deleting the test cobol, 2. Re-generating the cobol, 3. External bind but it doesn't help me in any way. Same old error message.
Please help me..
I don't understand "Show your package and plan bind control cards and sysouts". Bind is always successful.. |
|
Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009 Posts: 1788 Location: Bloomington, IL
|
|
|
|
Vishwamurthy wrote: |
I don't understand "Show your package and plan bind control cards and sysouts". Bind is always successful.. |
In that case, you must be only imagining the -805 SQLCODE. I can't help you, as I'm a software developer, not a psychiatrist. |
|
Back to top |
|
|
GuyC
Senior Member
Joined: 11 Aug 2009 Posts: 1281 Location: Belgium
|
|
|
|
Maybe you are running with an old load module ?
or against the wrong subsystem ? |
|
Back to top |
|
|
daveporcelan
Active Member
Joined: 01 Dec 2006 Posts: 792 Location: Pennsylvania
|
|
|
|
From my experience, the number one cause of a -805 is:
The library concatenation used in the Bind (step 3 for you above) does not match the library concatenation used in your Batch Job or CICS region setup.
Show the JCL you used for your external bind and your Batch run. |
|
Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
|
|
|
|
Possibly the online region(s) needs to be refreshed to ensure that the latest version of the load module is loaded. This often happens in IMS MPRs. (I don't speak CICS).
However, the TS hasn't given us any information about the execution environment, so this is just speculation.
I was going to suggest that this question would be more suited to the beginner's forum, but then I remembered that I have known veteran programmers whose solution to every -805 problem was to keep binding the program over and over in the hopes that it would eventually work. |
|
Back to top |
|
|
|