Even though a view (any view) can be specified within the F-speca and read
with the READ Op-Code, it must be considered a view does not (never?) have
In this way positioning it is only possible reading a view from the very
first row to the last one.
And the sequence in which the rows are read depends on the access plan used,
which may change depending on the data composition (statistics information).
In this way using embedded SQL in composition by selecting the desired rows
and returning them in the desired sequence through a cursor might be the
BTW SQL indexes cannot be specified within SQL statements, but can be
specified in the F-Specs and accessed with native I/O like any keyed logical
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von John
Gesendet: Tuesday, 02.9 2014 19:59
An: Midrange Systems Technical Discussion
Betreff: Re: Embedded SQL question
On Tue, Sep 2, 2014 at 11:28 AM, <rob@xxxxxxxxx> wrote:
I strongly suggest querying the SYSCOLUMNS a few times. If for no
other reason than to know that there are other ways to get field
I wholeheartedly second this, but would also like to add, in case it was not
clear, that "querying SYSCOLUMNS" does not have to be done with SQL. For
those who aren't already using SQL and needing to take baby steps, I believe
the SYSCOLUMNS logical file may be read using whatever means you would use
for any other logical.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l