[V4R5] File in arrival sequence: Correct way to place pointer at BOF -- RPG400-L

Subject: [V4R5] File in arrival sequence: Correct way to place pointer at BOF
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Mon, 16 Dec 2024 12:50:15 +0100
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: [V4R5] File in arrival sequence: Correct way to place pointer at BOF , Javier Sanchez
RE: [V4R5] File in arrival sequence: Correct way to place pointer at BOF , Jean-Marc DUVAL
RE: [V4R5] File in arrival sequence: Correct way to place pointer at BOF , paultherrien

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.