Re: Database I/O Modernization

[Alan Campin <alan0307d@xxxxxxxxx>]

Pretty easy answer. None. Use SQL. IBM has spent unknown millions of
dollars developing SQL which does the same times a thousand. Record I/O is
obsolete. Let it go.

On Sep 8, 2017 2:40 PM, "Nathan Andelin" <nandelin@xxxxxxxxx> wrote:

> The following link shows the RPG for a service program that encapsulates
> database I/O.
>
> It's essentially a template provided by Tembo Technologies as part of their
> road-map and approach to application modernization. Tembo has promised an
> open-source license.
>
> https://rd.radile.com/rdweb/temp/cusmstio.txt
>
> The interface is a single procedure call wherein the following parameters
> may be passed:
>
> Action code (e.g. I=Insert, U=Update, D=Delete, R=Read, etc.).
> Buffer pointer (a reference to an externally defined data structure located
> in the calling program).
> Key Data Structure (contains the record key(s)).
>
> Tembo's road-map calls for using this interface for RLA access for every
> table and logical view in Db2 for i.
>
> Questions:
>
> Is this type of interface familiar to you?
> What are the pros and cons of replacing existing I/O op codes with such
> procedure calls?
> Is this as an effective form of application modernization?
> Would you recommend a different type of interface?
>
> Thanks,
>
> Nathan Andelin.
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD