× 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/13/2017 03:33:12
PM:
1.) what do i need to do to avoid the -822?
2.) what are the correct sql steps to process the sql statement string
to
begin pulling out values from the fetched row? and from where?

You avoid -822 by providing addresses for the data areas where SQL
is to store the fetched data and indicators. However, I do hope you're
aware that the default SQLDA only provides space for up to 20 columns of
information (SQLVARs). If you need more than that then you need to create
your own descriptor data structure and use LIKEDS against the default
SQLDA and SQLVAR definitions. Otherwise, the steps are:

1. define enough data areas to provide storage for the number of columns
of data and indicators you will be fetching at one time
2. clear the descriptor data structure
3. set the number of SQLVAR areas in SQLN that you are expecting
4. issue a describe for your table/view/cursor
5. check SQLD to see the number of columns that were available to make
sure you're covered
6. loop through the descriptor data structure and, based on column data
type and length, provide addresses to your data areas from #1, above
7. fetch data using the descriptor data structure

At this point the fetched data and descriptors will be in your provided
data areas.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.