×
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.
The only valid use I would see for SetGt *end would be if it was followed
by a ReadP, to get the most recently added record in arrival sequence.
Of course, if you re-use deleted records, this wouldn't work anyway.
Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we. Futile is resistance, assimilated will you be.
-----
Ron Power <RPower@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
06/12/2007 12:55
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Re: SETGT *End/*Start
Just to add 2 cents here but logically speaking, SETGT doesn't seem to fit
anyway. To me SETGT *START would position to the 2nd record just after
the start of the file. To me this would serve no real purpose. The SETGT
*END would position to the EOF one would think? This is of course if
these were valid options on SETGT. So it makes sense to me that those
special values aren't used with SETGT.
Ron Power
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
