× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 10/16/2017 04:08:38
PM:
And one other piece of confusion regarding my current code in
attachment,
when the fetch occurs, on my system, the record does indeed exist...
sqlcode is set to 0, BUT if I look a the joblog, it says 0 records
fetched.

I'm confused... can someone please help me with this piece of a much
bigger
application?


You're still missing your SQLVARs and you are not initializing
SQLDABC. Why did you remove SQLDA from your PREPARE and FETCH statements?

By the way... Note that the term "Dynamic SQL" does NOT refer to
using SQL Descriptors. Dynamic SQL means that your SQL statement is a
character string which you have to PREPARE at execution time. If not
using SQL Descriptors, then your FETCH statement needs the INTO clause to
directly reference host variable(s) where the fetched data is to be stored
-- but those host variables will have to exactly match the expected data
types and lengths of the fetched data.

Since you don't know those, in your case, that is why you have to
use SQL Descriptors -- but, the descriptors still need to point to host
variables where the fetched data is to be stored. In this case, the host
variables have to match the fetched data types but character variables, at
least, can be longer than the fetched data. Packed decimal and binary
numbers will be an issue, though, and require special handling.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.