×
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.
Hello Vern,
Am 17.03.2023 um 00:33 schrieb Vern Hamberg via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx>:
I believe that SETLL never points _*at*_ a record, it always points to something "between" records - this goes back to Bob Cozzi's books on RPG, they show this behavior in a diagram, as I recall.
Setll is said to position just before a record so the next read reads the expected record. In fact, you can't physically read before the first record, or after the last one (in case of setgt). I assert, setll and setgt just set a flag so the next read(e) behaves as described.
To me, it sounds like some kind of a "children's lie" — to have an easily comprehensible explanation for the given behavior. :-) It's good enough to explain what's going on for most of the use cases, though.
Maybe that helps with the behavior you are seeing. I admit things feel kind of wonky, though.
Indeed. :-)
:wq! PoC
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
