Error calling Stored Procedure from VB6.0 (1 viewing) (1) Guest
Favoured: 0
|
|
|
TOPIC: Error calling Stored Procedure from VB6.0
|
|
|
|
Error calling Stored Procedure from VB6.0 1 Year, 9 Months ago
|
Karma: 0
|
|
This is a good page from IBM on the error code: <p><a href="http://www-1.ibm.com/support/docview.wss?uid=nas1c6a0327eda40dc60862566550054fa9e">http://www-1.ibm.com/support/docview.wss?uid=nas1c6a0327eda40dc60862566550054fa9e</a> <p> It indicates a more specific code should be found in the job log ahead of it. If you are able to press F10 to get the job log it should be there. <p> Sounds like from the IBM doc possibly some missing files that VB6 uses that weren't rebuilt after an OS upgrade. <p> hope that helps some. <p> rd
|
|
|
|
|
|
|
The administrator has disabled public write access.
|
|
|
|
Error calling Stored Procedure from VB6.0 1 Year, 9 Months ago
|
|
|
We spent some time with IBM Tech Support and they determined that the VB6 developer was using a 10 year old version of the Client Access ODBC driver. They upgraded to the v5r3 version and it is now working correctly.
|
|
|
|
|
|
|
The administrator has disabled public write access.
|
|
|
|
Error calling Stored Procedure from VB6.0 1 Year, 9 Months ago
|
|
|
One of our VB6.0 programmers is receiving an error when calling an RPG iSeries Stored Procedure. We are able to call the SP from VB.net and iSeries Navigator so we are pretty sure that the SP is functioning correctly. <p>The error we are seeing is in the QZDASOINIT job joblog. The error is as follows: <p>Code: PWS0005 <p>Message: Error occurred in the OS/400 database server code. <p>Cause: An error occurred in the OS/400 database server code which caused the function to not be completed. <p>Recovery: Use F10 (if available) or the Display Joblog (DSPJOBLOG) command to see the messages in the joblog for a more complete description of what caused the error. If possible, correct the error. Try the function again. If the error continues, contact your service representative. <p>We appreciate any thoughts that someone might have on how we can correct this issue. <BR>
Thanks
|
|
|
|
|
|
|
The administrator has disabled public write access.
|
|
|
|
|