× 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.


  1.  Home
  2. RPG400-L
  3. June 2016

Re: i7.3 native rpg reads implemented as SQL

And as I understand it...the low level QDBGETxxxx routines are used by both
RPG and SQL.

At that level, you aren't dealing with RPG or SQL.

Charles

On Mon, Jun 13, 2016 at 1:13 PM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

On 6/13/2016 10:52 AM, Darren Strong wrote:


I noticed, due to a failure issue in SETLL and READ at i7.3, that the
failing call stack entries were related to SQL. Then, through testing, I
tried to read from one logical, and I saw that my RPG program was reading
from a different logical using native READ operations. Does RPG implement
reads as SQL cursors now, and when did that start?


Just a guess ... was the call stack entry QDBGETSQ? If so, that stands for
"Get Sequential", nothing to do with SQL.

RPG's native access doesn't use SQL cursors.

--
Barbara


--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


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.