| View previous topic :: View next topic |
| Author |
Message |
avin
Beginner
Joined: 31 Aug 2006
Posts: 2
Topics: 1
|
 Posted: Mon Feb 05, 2007 8:54 am Post subject: Sqlcode -924 |
 |
|
Hi,
I have a COBOL program that calls the stored procedure. When I try to run the program, SQLCODE=-924 and SQLSTATE=58006 is generated.
ERROR: DB2 CONNECTION INTERNAL ERROR
Please can some one help me to solve this error.
Thanks in advance,
Avin
_________________
avin |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12382
Topics: 75
Location: San Jose
|
| Posted: Mon Feb 05, 2007 10:53 pm Post subject: |
|
|
avin,
what is the reason code associated with the abend?
Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
avin
Beginner
Joined: 31 Aug 2006
Posts: 2
Topics: 1
|
| Posted: Tue Feb 06, 2007 3:40 am Post subject: |
|
|
Kolusu,
The reason code is 00F30016
Avin
_________________
avin |
|
| Back to top |
|
|
dbzTHEdinosauer
Supermod
Joined: 20 Oct 2006
Posts: 1411
Topics: 26
Location: germany
|
| Posted: Tue Feb 06, 2007 4:28 am Post subject: |
|
|
reason code is 00F30016 refers to the validity of the plan name. Documentation suggests blank or spaces for plan name. This occurred during the ATTACH, not your call to the SP. You need to insure that however you are performing your connect to DB2, you have the correct plan name.
_________________
Dick Brenholtz
American living in Varel, Germany |
|
| Back to top |
|
|
dbzTHEdinosauer
Supermod
Joined: 20 Oct 2006
Posts: 1411
Topics: 26
Location: germany
|
| Posted: Tue Feb 06, 2007 6:21 am Post subject: |
|
|
| dbzTHEdinosauer wrote: | | reason code is 00F30016 refers to the validity of the plan name. Documentation suggests blank or spaces for plan name. This occurred during the ATTACH, not your call to the SP. You need to insure that however you are performing your connect to DB2, you have the correct plan name. |
SHOULD HAVE BEEN:
Documentation suggests that the user 'has provided a name plan consisting of spaces or blanks'.
The ATTACH to DB2 was made but the plan name provided was not that of the PLAN name of the SQL invoked.
Possibly the SP has not been properly assembled/bound - etc....
The plan name you gave, if it was not spaces, was either incorrectly entered in your parameters to the ATTACH or the SP has not been properly registered with DB2.
_________________
Dick Brenholtz
American living in Varel, Germany |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
