×
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.
First, I should say this is just my opinion, but I have been fairly dissatisfied with externalized file i/o. IBM has given us a VERY efficient means of processing file i/o, whereas most implementations of externalized i/o I have seen seem to simulate IBM's opcodes... Replacing CHAIN with a procedure performing the CHAIN does not seem particularly efficient to me...
Personally, I'd rather focus on writing procedures that encapsulate business logic, and make use of whatever native file i/o operation (chain, read, SQL, etc.) are suited to the problem at hand.
The only reason I can see to abstract low-level file i/o into procedures is if you intend to port your application to another language or platform.
jmo,
Eric DeLong
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of David FOXWELL
Sent: Wednesday, May 28, 2008 2:34 AM
To: RPG programming on the AS400 / iSeries
Subject: i/o module
Hi,
Does anyone have some code that they could post for externalizing file i/o operations ?
I've had my first go at this and although it works I'm not fully happy with it.
To replace an RPG CHAIN operation, my program does something like IF NOT ReadFile ( ), and the function ReadFile will do a CHAIN.
However in replacing a loop like
SETLL File
DOU %eof
READ File
ENDDO
I use another function that uses an SQL cursor. I realise that this last function could also do the same as the ReadFile ( ) , but should I replace a simple CHAIN by SQL?
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.