RE: RPG enhancement suggestion

If this is a real performance issue for you, create a logical file with a
new record format holding only the fields you need.  This can give you the
shorter record length so you can block more records at a time.  If you don't
want to maintain a LF, build a PF with the necessary fields and no data
members.  Then use its record format on an opnqryf statement.  Your RPGs
will be compiled against this work file.  However I don't think this will
make enough difference unless you are processing millions of records..

Christopher K. Bipes            mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst          mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                http://www.cross-check.com
6119 State Farm Drive           Phone: 707 586-0551 x 1102
Rohnert Park  CA  94928         Fax: 707 586-1884



-----Original Message-----
From: Colin Williams [mailto:Williamsc@technocrats.co.uk]
Sent: Monday, June 21, 1999 8:15 AM
To: 'RPG400-L@midrange.com'
Subject: RPG enhancement suggestion



I have been writing an extract program, to bring in data from a file on
an external system. During this, a question occurred.

Would file processing in RPG be a lot quicker if we could drop fields
that we weren't using, similar to the way it works when you internally
describe
a file, but without actually decribing the file internally.

eg: if I have a typical input file with 50 fields on it, but I only
actually use 1 field on it in the program, I would like a keyword that
allows me to
drop all the other fields from the file.

There must be 1000's of RPG programs out there that use only very few
fields from files, but read in every field on the file every time a
record 
is read
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *