RE: Externalizing I/O was RPG read loops

["Joel Fritz" <JFritz@xxxxxxxxxxxxxxxx>]

We used to have a segmented customer master file and associated
transaction history files created when the amount of data was too large
to fit in one file.  We used programs to hide the nasty details of going
from one file to another.  Because RPG file names and record formats
can't be referred to by variables, I don't think that I/O routines give
you very much except in cases where the I/O is more complicated than
just using the standard opcodes. 

IFS file access is a different story.      

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, February 02, 2005 8:11 AM
To: RPG programming on the AS400 / iSeries
Subject: Externalizing I/O was RPG read loops

Paul,

I think you're the first person that I heard of, that wasn't the person
in charge of writing the access programs, that actually liked this
scenario.
Why an end developer would like to replace

chain(e) myfile;
// now actually do some real work with the fields

with
getFilename();
MyWorkField1=GetField(field1);
MyWorkField2=GetField(field2);
...
// now actually do some real work with the fields

rather escapes me.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com






*****************************
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise 
recorded by
The Sharper Image corporate e-mail system and is subject to archival, 
monitoring,
and review by and/or disclosure to Sharper Image security and other management.
This message is intended only for the use of the addressee and may contain 
information
that is privileged and confidential.

The contents of this message may contain personal views which are not the views 
of The Sharper Image.
If you are not the intended recipient, dissemination of this communication is 
prohibited.
*****************************