× 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: RPG Indicators
  • From: "Bale, Dan" <DBale@xxxxxxxx>
  • Date: Mon, 17 Apr 2000 10:49:40 -0400

> Now you've done it, Dan.  Started up the Do Wars again!   :-)
Sheesh!  And, this time, I did it without even trying!

I know I've been beat up enough about using DoU & If vs. DoW.  Even before
we had Iter and Leave, I was doing it this way.  Even if there is an
additional sacrifice of efficiency, it can't possibly be of any significance
on today's AS/400s.  

Like others have said, this is a personal preference.  And, even though my
way is better, it's certainly no reason to start a war over this!  <g>

Thanks for the backup!

- Dan Bale

> -----Original Message-----
> From: Nelson C. Smith [SMTP:ncsmith@gate.net]
> Sent: Friday, April 14, 2000 10:17 PM
> To:   RPG400-L@midrange.com
> Subject:      Re: RPG Indicators
> 
> Now you've done it, Dan.  Started up the Do Wars again!   :-)
> 
> (Although, John Carr and I both agree with you on DOU, you will find it a
> very small cheering section! )
> 
> 
> ----- Original Message -----
> From: "Bale, Dan" <DBale@lear.com>
> To: <RPG400-L@midrange.com>
> Sent: Friday, April 14, 2000 3:07 PM
> Subject: RE: RPG Indicators
> 
> 
> > My preference is to just have one file input operation for the loop,
> i.e.:
> >
> >      c     Key           Setll     FileName
> >      c                   DoU       %EoF( FileName )
> >      c     Key           ReadE     FileName
> >      c                   If        not %EoF( FileName )
> >       ***   do stuff
> >      c                   EndIf
> >      c                   EndDo
> >
> > This has always worked for me.
> >
> > - Dan Bale
> >
> > > -----Original Message-----
> > > From: Andrew Sereda [SMTP:asereda@HU.EEFT.COM]
> > > Sent: Friday, April 14, 2000 12:55 PM
> > > To: 'RPG400-L@midrange.com'
> > > Subject: RE: RPG Indicators
> > >
> > > I found addition inconvenience as for using %found and %eof.
> > > Normaly I use such routine:
> > > Key  chain format         99
> > >      dow   *in99=*off
> > > ...
> > > ...
> > > Key  reade format           99
> > >      enddo
> > >
> > > In case %eof is not working with chain opcode I need to insert
> addition
> > > 'if'.
> > > so I should do:
> > >
> > > Key  chain format
> > >      if    %foun
> > > ...
> > > Key  reade format
> > >      endif
> > >      dow not %eof
> > > ...
> > > Key  reade format
> > >      enddo
> > >
> > > Thanks,
> > >
> > > Andrew
> > > -----Original Message-----
> > > From: McCallion, Martin [ <mailto:MccalliM@Midas-Kapiti.com>]
> > > Sent: Thursday, April 13, 2000 5:37 PM
> > > To: 'RPG400-L@midrange.com'
> > > Subject: RE: RPG Indicators
> > >
> > >
> > > I think that %found doesn't work for READ* opcodes.  You might want to
> > > try %eof instead.  In any case it's better practice to use
> > > %found(filename).  That way it's always clear exactly which condition
> > > you're testing.  Without the file name, %found reflects the result of
> > > the most recent applicable opcode.
> > >
> > > Cheers,
> > >
> > > Martin.
> > >
> > > --
> > > Martin McCallion
> > > Midas-Kapiti International
> > > Work:  mccallim@midas-kapiti.com
> > > Home: martin.mccallion@ukonline.co.uk
+---
| 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 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.