Re: IBM i "Open I/O" Architecture

[Michael Ryan <michaelrtr@xxxxxxxxx>]

XFOOT = SUM

Shake and Bake, and I helped!

On Thu, Oct 22, 2009 at 12:11 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

> From: Jon Paris
> > Nice summary Nathan.
> > I think you have hit it square on.
>
> Well, thanks.  But let's not view my comment as a concluding summary.
>
> Scott Klement, for example, has already done some interesting work on
> RPG-JDBC procedures that might benefit by the type of familiar, streamlined,
> and consistent interface that Open I/O might provide.
>
> Say an RPG /F spec automatically triggers a file "open" which evokes an
> Open I/O handler.  Say the file name, open mode, and device type were passed
> as parameters.  The device type might be a key to a predefined IBM i object
> which tells the Open I/O handler which remote SQL database to connect with,
> and whatever else may be needed to make the connection. Right there, you've
> given an RPG programmer an advantage over other programmers who may write a
> paragraph or two - just to establish a connection to a remote database,
> generate an initial cursor, and do default error handling.
>
> Now, if 3rd parties can come up with ways to map other RPGopcodes to SQL
> equivalents ...
>
> Nathan.
>
>
>
>
> --
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.