×
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.
The best reason to avoid LF that are not in the same library as PF is
to prevent ACCPTH rebuilds. When an LF is restored without the PF, the
access path for that LF must be rebuilt; appearing in EDTRBDAP, and the
completion logged as CPF3145 <failure as CPF3146> in QHST. What might
appear to be 47 minutes could actually be several hours from the
perspective of an application which opens the LF. And in the atypical
case, if the LF is for a unique key and an application opens the PF
before the LF is restored, then application dependence on uniqueness via
LF would not be enforced and the application could end up writing
duplicates; or application termination after the restore completes but
the rebuild pends, if improperly written such that a program fails to
handle CPF5190.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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
