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.
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.