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


  • Subject: Re: DOU/DOW for READ Loops
  • From: Jim Langston <jlangston@xxxxxxxxxxxxxxxx>
  • Date: Tue, 25 Apr 2000 11:08:33 -0700
  • Organization: Conex Global Logistics Services, Inc.

Oh, yes, I just hate KLists.  And you can't use a data structure in a KList.

This defininately should be changed.  Even in S36 you could use a data
structure for a key field, since the file was internally described.  I guess you
could internally describe the file in RPG IV, but who would want to?

Regards,

Jim Langston

Bald mans lament: Hair today, gone tomorrow.

Gwecnal@aol.com wrote:

> >  Well, Read Until would work, but wouldn't it be much better to do something
> >  like:
> >
> >         DoWhile    Read(ARFile01)
>
> OK, I'll take that.  Maybe a bif like
> %read(FileName:KeyField1,KeyField2,etc.))  Add %reade, %chain, %readp,
> %setll, etc. and we won't need klists anymore.  Which reminds me - if there
> was ever anything that belonged in the d-specs it is a klist, but you still
> can't do that :-(
>
> Lance

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.