So long as the application does not close the file,
and "hang onto" any RRNs,
and then re-OPEN the file and expect the records
to still be there in the same place, you should be okay.
Or, am I missing something?
It matters if the RPG program(s) that processes the file(s) are treating it
as a 'Direct' file...
My first exposure to the System/38 was in a shop that was running System/34
(RPGII) MAPICS code.
S/34 MAPICS used 'linked lists';
For example, the Item Master record had a field that contained the RRN of
the first record in the Bill Of Material (BOM) for the item, and the BOM
file had fields that contained the RRN of the previous and next BOM records.
To chase through the bill of materials, you had to keep chaining to the BOM
file with the 'next BOM record' field to get the next BOM record.
When you hit a value of all 9's in the 'next BOM record' field, that meant
you were at the end of the list of BOM records.
Needless to say, in the case of deleted records an RGZPFM on the BOM file
could play havoc with the linked list values...
This thread ...
Re: Prohibit RGZPFM because of RRN access., (continued)
This mailing list archive is Copyright 1997-2019 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