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



OK, it wasn't me writing this program, so I had a closer look at it myself
and (in a momentary lapse) my colleague had neglected to put a 'K' in the
F-spec.

'Pleased but disappointed' was how he described his feelings when I pointed
this out to him.

Thanks anyway


Martin

-----Original Message-----
From: JJW [mailto:rpgilejjw@xxxxxxxxxxx]
Sent: 22 March 2003 21:38
To: RPG programming on the AS400 / iSeries
Subject: Re: FEOD followed by Setll


Try *start instead of *hival


----- Original Message -----
From: "alan" <steelville@xxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Saturday, March 22, 2003 1:13 PM
Subject: Re: FEOD followed by Setll


> <snip>
> Write file
> FEOD
> *hival Setll file
> Read file
> %eof is set immediately.
> </end snip>
>
> Martin,
>
> I would suspect that the FEOD does indeed set the %eof
> indicator, but that the SETLL does not. This makes sense to
> me, and sounds to me like it *should* work this way. For
> example in the following scenario (in a "normal"
> ascending-order-keyed file):
>
> keyfield setgt FileA
>
> At this point, the program *should not* know whether it is
> at the end of the file yet or not. But at the next attempt
> at input in this scenario, the status of the file will be
> set at %EOF.
>
> It does make you do a double-take though.
>
> But curiosity drives me to ask, Why do an FEOD and then
> re-position the file?
>
> - Alan
>
> +++++++++++++++++++++
> ----- Original Message -----
> From: "Saunders, Martin P" <martin.saunders@xxxxxxxx>
>
> | Hi Booth,
> |
> | I read that bit in the manual ('you must reposition the
> file'), I thought
> | that is what the SETLL would do.
> |
> | BTW: to the other people who replied: thanks for the
> suggestion but the
> | reason I am using *HIVAL is because the file is keyed
> descending.  Reading
> | the file in this way in a separate program works fine.
> |
> | Thanks
> |
> | Martin
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


********************************************************************************************
" This message contains information that may be privileged or confidential and 
is the property of the Cap Gemini Ernst & Young Group. It is intended only for 
the person to whom it is addressed. If you are not the intended recipient, you 
are not authorized to read, print, retain, copy, disseminate, distribute, or 
use 
this message or any part thereof. If you receive this message in error, please 
notify the sender immediately and delete all copies of this message ".
********************************************************************************************


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.