×
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.
It was QDBGETSQ and also referenced DbDsiCursor. That's why I assumed. I
could have sworn I saw it diverting from one logical to another without an
override, but that may have either been a flaw in my testing, or a result
of the defect I was encountering.
Thank you for the response.
From: Barbara Morris <bmorris@xxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Date: 06/13/2016 01:14 PM
Subject: Re: i7.3 native rpg reads implemented as SQL
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
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.
midrange.com
