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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Database I/O Modernization
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Fri, 15 Sep 2017 19:47:02 -0400
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Fri, Sep 15, 2017 at 4:58 PM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

Is RLA portable to other languages and platforms? Can I copy and paste the RLA code from an RPG program into say a Java, C#, Python, etc program? No.

Well, it's a special case, but you CAN use RLA in (iSeries)Python.
Obviously you can't just cut and paste, but you can translate fairly
straightforwardly:

http://iseriespython.blogspot.ca/2014/05/record-level-access-in-iseriespython.html

I do agree that SQL is significantly more portable, though.

John Y.

As an Amazon Associate we earn from qualifying purchases.

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.