|
He, also, teaches the techniques involved at COMMON (and, I'm guessing, the System i Developer seminars).
* Jerry C. Adams *IBM System i5/iSeries Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.995.7024 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Johan Vangilbergen wrote:
Hi,I work on an application that has a history of more than 15 years. Originally this application was written in RPG400 and somewhat 5-6 years ago, the whole bunch was converted to RPG IV using the CVTRPGSRC. Since then most of the programs are being created with the CRTBNDRPG command.Since a few months I've did some trials to create modules and bind them together in real ILE-programs. With, all together, reasonable success.Now I want to go a step further on the ILE-way and want to start externalizing file I/O's. However, I'm having some difficulties insetting up a workable organization for this.I was thinking of creating two modules for each file in the database : the first one would contain procedures to update, add or delete records in the file, the second would contain procedures to get information from the specified file (input only). Finally, I thought of binding these two modules in a service program. So, I would have one service program for all I/O's per file.Is this a workable method ? Does anyone has any suggestions, or can you point me to some literature and/or examples of how to handle this ?Another question to this is : do I need to have a different name for each procedure. For example : I have customer-file and a supplier-file. If I want to read a record, does the name of the two procedures to read a record have to be different (e.g. ReadCust and ReadSup) ? Or is there a way to name it both for example Readrecord ?Any suggestions will be welcome, as well as tips for further reading.Johan VangilbergenYUSE Phone : +32 16 74 50 80 Fax : +32 16 74 50 89Email : jvg@xxxxxxx <mailto:jvg@xxxxxxx> Web : WWW.Yuse.be <http://www.Yuse.be>Address : Bondgenotenlaan 138, B-3000 Leuven, Belgium
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.