×
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.
An oft stated warning, but on what basis? The algorithm establishes
either, a new reference to the same-name file which exists in the target
library, or maintains the reference to the original library/file. There
is never an attempt to look for the same-name file in *LIBL [looks in no
other library than the target] for creating a duplicate LF; same rules
apply for a restore.
If anyone ever finds a case where the Library List applies to a
CRTDUPOBJ of a Logical File, please do tell. Until there is an actual
example given, where a change to the Library List of the job performing
CRTDUPOBJ can effect a difference in which [based-on] file will be
accessed by the duplicated LF, please /assume/ that a Library List will
not affect the request in any way [at least with regard to which PF the
LF references].
Regards, Chuck
Nick_Radich@xxxxxxxxxxxxxx wrote:
You need to have NEWLIB in the library list above OLDLIB. Otherwise the
LFs being duplicated into NEWLIB will still point to the PF in OLDLIB.
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
