Re: RPGLE native I/O and SQL Tables/Views/Indexes

[Brian Parkins <goodprophet.bp@xxxxxxxxx>]

A Table = non-keyed, Physical File
A View = non-keyed, single-format, Logical File
An Index = a keyed, non-join, single format, Logical File

RPG IV operations can be used in exactly the same manner as with the 
"native" (DDS + CRTxx) defined objects.

To complicate matters, don't forget you CAN use CHAIN, SETLL etc. on a 
View - if processing by relative record number, (i.e. non-keyed processing).

HTH,
Brian.

On 27/09/2021 17:23, Alan Campin wrote:
> it's not that simple. A physical file created with DDS and a table created
> with SQL are the same thing to RPG. If the table has an index, you can do
> operations like Chain and Setll just like a DDS defined table.
>
> Views are more complex. Views don't have indexes so the only thing that you
> could do with a view in an RPG program is read it sequentially or write to
> it.
>
> An SQL index looks like a logical file to an RPG program so you could use
> it like a logical file. That's not normally how you would do it. You would
> define an SQL index and then define a logical and it should share the
> access path (Index) and it is just another logical to RPG.
>
>
>
> On Mon, Sep 27, 2021 at 9:11 AM K Crawford <kscx3ksc@xxxxxxxxx> wrote:
>
> > I am trying to help someone and clarify for me the following.  I don't
> > think I am typing in my searches correctly.  What I am looking for is:
> > What native RPGLE I/O can you do over a SQL Table?
> > What native RPGLE I/O can you do over a SQL View?
> > What native RPGLE I/O can you do over a SQL Index?
> > A chart something like:
> > I/O     Table    View    Index
> > Read    Yes      Yes     Yes
> > Reade   No       No      Yes
> > Readp   x        x       x
> > Readpe  x        x       x
> > Chain   x        x       x
> > SetLL   x        x       x
> > SetGT   x        x       x
> > Delete  x        x       x
> > Write    x        x       x
> >
> > --
> > KCrawford