Re: Database I/O Modernization

Nathan

If I may, I think that you use RLA as a term differently from what I do -
I think of RLA as native IO in RPG (the only language in which I use access
to data - I do know about the C++ functions, however).

Thanks for the feedback. When RPG I/O opcodes are used, the compiler binds
to service program QRNXIO, which contains the RLA procedures that are
invoked.

As far as I know, RPG is the only interface that binds to service program
QRNXIO. I agree that the SQE doesn't use those procedures.

It sounds as if you refer to the DB component of the system when you use

the term - this is probably causing some of the controversy here - talking
at different levels.

The phrase "the DB component of the system" is ambiguous. But I kind of get
your meaning.

Both SQL and native I/O use the same low-level SLIC functionality - these
are exposed in the various higher-level calls - the GETM, GETK, GET, etc.,
kinds of things.

Yes, but there is a layer of procedures that are run above the machine
interface that are exposed through service programs such as QRNXIO, QC2IO,
and QDBXIO. The procedures have names like open(), close(), read(),
write(), update(), delete(), etc. That's what I'm referring to.

The SQE may receive a statement like "select * from mytable" that gets
interpreted and processed as open(), read(), and other logic that
ultimately provides an appropriate response to the query.

I suspect several of us are agreeing violently!

Thanks.