RE: Copying File Structures - LF crtdupobj and *LIBL

To Chuck's point below, out testing did not show any sensitivity to the
library list on a DUPOBJ. If the PF referenced by the LF is in the same
library, that reference is moved. LF's referencing other libraries
retain those references. In both cases, the library being duped into
was not in the library list at all. In our environment, the
cross-library logicals are all built in our custom libraries so we do
have the DDS and can modify and recompile. Not the most elegant way to
handle it, but manageable for us at least.

Regards,

Jim Reinardy
Badger Meter, Inc.
Milwaukee, WI

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, May 29, 2008 6:30 AM
To: Midrange Systems Technical Discussion
Subject: RE: Copying File Structures - LF crtdupobj and *LIBL

What does matter from my experiences is the order in which the files are
replicated. For example, if the LF is replicated prior to the PF, the
LF will point to the original PF; it will not re-point to the replicated
PF when it is copied.

More complicated are LF replications that point to PF(s) in other
libraries. When we did Y2K remediations, we had a customer with this
characteristic. I forget the solution, but I do remember that it was a
pain in the butt.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, May 28, 2008 7:05 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Copying File Structures - LF crtdupobj and *LIBL

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 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.