Re: confusion with logical files and crtdupobj

On Fri, Sep 28, 2012 at 3:13 PM, <hack400@xxxxxxxxxxxx> wrote:

What you are seeing is expected behavior. CRTDUPOBJ does not use the library
list for LF's (ever).

This is expressed rather confusingly, given that the MYFILELF
duplicate worked the way the OP wanted (i.e. the duplicate picked up
the PF in the current library rather than the original PF).

MYFILEL1 will always end up based on the PRODUCTION
version of the file because it is not in the same library as the PF is it
based on. You'll have to recreate MYFILEL1...

So there is the "special" case where the original LF and original PF
are in the same library, in which a duplicate LF will pick up a new PF
if available. But when the original LF and original PF are in
different libraries, then a duplicate LF will always pick up the
original PF. Clear as mud. (And I put "special" in quotes because on
our system, the LF is in the same library as its PF something like
99.999% of the time.)

If it were up to me, I would make CRTDUPOBJ on a LF always, always,
always pick up the original PF, no matter what, under any
circumstances whatsoever.

John