Re: CRTDUPOBJ logical file with shared access path

Dave,

CRTDUPOBJ has always worked this way, IIRC. 

See:
    https://www.ibm.com/docs/en/i/7.3?topic=ssw_ibm_i_73/cl/crtdupobj.html ;

and in particular, page down to read this section:

=========================================================
When a logical file is copied into another library, two cases determine the basing for the file:

    1. If both the logical file and its based-on physical file are originally in the same library, a duplicate of the physical file must be created in the new library before a duplicate of the logical file is created. After these two duplicates are created, the new logical file is based on the new physical file.

    2. If the logical file and its based-on physical file are originally in different libraries, it is not necessary to duplicate the physical file before duplicating the logical file. In this case, the duplicated logical file is based on the same physical file as was the original logical file. Unlike the first case, even if the physical file is copied into the new library before the logical file is copied, the duplicated logical file is based on the original physical file, not on the duplicated physical file.
=========================================================

You can correct this situation after the fact by using RMVM to remove the logical file member, then re-add it with the ADDLFM command.  (ADDLFM requires the actual library name for any dependent physical file members, for each member involved.)

I hope this helps,

Mark S. Waterbury

On Wednesday, January 31, 2024 at 12:30:52 PM EST, Dave <dfx1@xxxxxxxxxxxxxx> wrote:

A colleague had this problem setting up a test with a logical file :
    Physical file copied into the test library from production
    Logical file object from production copied in the same library after
having set the test library at the top of the list

The logical file created in the test library indexed the physical file in
the production library. After some searching, it was noted that the logical
file shares an access path with another logical file.

Questions :
What is the technical explanation for this? Normally the logical file is
recreated and indexes  the new physical file in the test library. This
would suggest the copy of the logical file was not recreated.

How can you get the name of the files with which the access path is shared?
I got it by checking the job after issuing an interactive SQL request

Thanks