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

Subject: Re: [V4R5] File in arrival sequence: Correct way to place pointer at BOF
From: Patrik Schindler <poc@xxxxxxxxxx>
Date: Mon, 16 Dec 2024 20:19:03 +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 Jim,

Am 16.12.2024 um 18:38 schrieb Jim Franz <franz9000@xxxxxxxxx>:

i always used (when no setll) that READ would start at the beginning of an
non-keyed file.
Has the OP (or any others) any evidence this is not true?

I had some surprising experiences with applications staying activated and hence retaining the file pointer between calls. To be on the safe side, I thought it might be easy to just setll to BOF. Problem solved.

Apparently there is no way to set the file pointer in non-keyed files to explicitly BOF or EOF.

: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 , Patrik Schindler

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.