×
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.
On 19-Nov-2013 11:13 -0800, Jeff Crosby wrote:
Heh.
ALWCANCEL(*NO) means 1 journal entry for the reorg.
ALWCANCEL(*YES) means journal entries for every record moved.
Never knew that. Learn something new every day.
The /traditional/ reorganize, RGZPFM ALWCANCEL(*NO), was also what
was called a /showstopper/ with regard to Apply Journaled Changes
(APYJRNCHG); i.e. a member-level versus row-level request that can not
be applied, per error msg CPF7049. The file.mbr should have been
backed-up at that point, to avoid that restriction... or the RGZPFM
would have to be performed outside the apply-processing, and
apply-processing requested to restart after the F-RG entry. However
with the /online reorganize/ invocation, RGZPFM ALWCANCEL(*YES), there
is no such restriction because its processing is implemented entirely
with normal [even if considered obscure] I/O operations, for which
applying those row-level changes is fully supported; thus conspicuously,
why its effects as log\jrn entries being visible for each row I/O operation.
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.
midrange.com
