|
1) Quit using CLRPFM - it's designed only to be used when you can
guarantee exclusive access to a file. That's hard to do now-a-days
and if you're allowing the file to be queried at any time you simply
can't make the guarantee CLRPFM requires. I created a CLRPFMSQL
command that uses SQL DELETE to delete all records in a file. At
v5r2(?) and higher the SQL DELETE usually performs just as fast as
CLRPFM as it will do a clear if possible, or a change file, or as a
last resort individually delete the rows.
As an Amazon Associate we earn from qualifying purchases.
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.