Correct, if I recall the rule is actually documented somewhere as:

1) Dup a PF into a new lib
2) Dup a LF built over that PF into the same new lib

IF the LF was in the same library as the PF then relink the LF to the new PF
but IF the LF was in a different library than the PF then leave the LF
pointed to the original PF.

As long as you remember the rule it's not bad. You'd have to do a
RMVM/ADDLFM to correct the linkage.

I hope RCLSTG wouldn't fix this. I don't consider this broken. Al, are you
saying RCLSTG would change my LF to point to the PF in the same library?

-Walden

------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Friday, January 04, 2002 10:15
To: midrange-l@midrange.com
Subject: RE: Does RCLSTG also do a RCLLIB and RCLDLO


The biggest issue I've run into comes with duplicating the files.  When a
logical is created in the same library as the physical, some sort of
metaphysical link exists between the two, and when you duplicate both into a
new library, the logical is automatically attached to the physical.  This
will not happen when the logical and physical reside in separate libraries.

<snip>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.