|
Isn't that what I said? " target library of the physical is first"
Sharon Wintermute
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crispin Bates
Sent: Thursday, May 21, 2009 1:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: Copying logical files from one library to another
Horses for courses, but I'm pretty sure that the target library being in
the
library list (at all) is an urban legend, and has no impact...the real
decider being if the physical in in the target library...
----- Original Message ----- From: "Wintermute, Sharon" <Sharon.Wintermute@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, May 21, 2009 2:23 PM
Subject: RE: Copying logical files from one library to another
James,how;
Here is what I do.
Make sure the target library of the physical is first in the library
list. (or Current).
CRTDUPOBJ DATA(*NO)
Sharon Wintermute
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H.
Lampert
Sent: Thursday, May 21, 2009 1:07 PM
To: Midrange Systems Technical Discussion
Subject: Copying logical files from one library to another
I've seen this done; I've done it myself. But I can never remember
neither does the usual RTFM shed a whole lot of light on it:(FOO)
Given two libraries FOO and BAR, with physical BAZ in both libraries,
and logical QUX on BAZ in FOO, but not in BAR:
I can never remember how to copy a logical (QUX) from one library
to another (BAR), so that it picks up the corresponding based-onthe
physical in the target library (BAR/BAZ) instead of pointing back to
original one in the source library (FOO/BAZ).
Is it a CPYF or a CRTDUPOBJ?
And what are the required conditions for it to behave as desired?
--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.