Jim Essinger wrote:

Going from memory, as I am not at my work computer. 99% sure that the
following is true.

Declare the cursor with the select statement listed earlier,
I open the cursor, which has an SQLSTATE and SQLCODE of 00000
I then fetch using the cursor name, that is when I get the error with no


[x-posted to COBOL400-L, I hope; please reply there]

When you have it available, can you show the FETCH? Since the error occurs at that time, perhaps that's worth seeing. (And if you found the problem already, can we hear the resolution?)

Part of the problem seems related to "Ran the statement in iNav scripts" although I'm not clear how iNav handles DECLARE CURSOR. When you use embedded FETCH for the noted SELECT, you necessarily add the complexity of host variables.

Tom Liotta

On 8/20/07, Tom Liotta <qsrvbas-VsqqI1RANlHk1uMJSBkQmQ@xxxxxxxxxxxxxxxx> wrote:
Jim Essinger wrote:

Ran the statement in iNav scripts - no error, returned the data I
As a work around I used the statement to create a file using STRSQL,
put the code in a QMQry as an insert, and insert the records into a
temp table with a CL wrapper. I then open the temp file with the
COBOL program to process. That's the long way around! The temp file
does not show any data problems.

You've shown the DECLARE CURSOR, but I don't recall seeing what you
actually _do_ with the CURSOR in your COBOL program... ?

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.