×
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.
Hi, Rob:
So long as those RRNs are never stored anywhere else, (e.g. in any other
files, to "point to" records in this file), then what's the harm in
allowing a RGZPFM? I think RGZPFM requires "exclusive" access to the
file, so none of your applications can be actively using this file, when
the RGZPFM takes place; or the RGZPFM will get:
CPF3202 File XXXXXXXXXX in library YYYYYYYYYY in use.
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?
Mark
> rob@xxxxxxxxx wrote:
If one routinely access a file by RRN is there a way to CHGPF or some such
thing to prohibit RGZPFM against that particular file?
Rob Berendt
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.
midrange.com
