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



Patrick, even with implicit OPEN, since RPG does that, you always are at
the beginning of the file, and no matter if it has a key or not, it will be
at BOF.
So, issuing a READ will get the first record. RRN works even with a CHAIN,
and only if it's not keyed:

CHAIN 1 MYFILE;

should work too.

JS


El lun, 16 dic 2024 a las 5:50, Patrik Schindler (<poc@xxxxxxxxxx>)
escribió:

Hello,

I have a PF that is used as temporary storage for a cpyfrmimpf. It has no
keys whatsoever and is truncated before each run (rmvm, addpfm). I
reference that file in RPGLE without the K flag, because it has no keys.

What is the correct way to place the file pointer at BOF?

Neither setll *START, nor *LOVAL work: The compiler complains that these
are invalid. Setting it to 1 makes the program compile. But this is now
based on the assumption that there is always a RRN 1 in the file.

Did some Googling but did not find enlightenment. Hints are welcome!

:wq! PoC

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



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