Re: Database I/O Modernization -- MIDRANGE-L

Subject: Re: Database I/O Modernization
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Fri, 8 Sep 2017 16:45:45 -0600
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Fri, Sep 8, 2017 at 4:02 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

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.

Alan, if I understand correctly, you object specifically to the use of RPG
op codes. But what about the procedure interface implemented in the service
program?

If the RPG op codes were replaced with SQL, would the procedure interface
meet with your approval?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Database I/O Modernization , Alan Campin
Re: Database I/O Modernization , Roger Harman

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.