Re: CRTDUPOBJ logical file with shared access path

Hi Mark, sure but this is a test env, rigth? When we do such kind of
process in a production env the path is diffrent.

By the way, on our systems LF and PF are always in the same Library.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno gio 1 feb 2024 alle ore 22:45 mlazarus <mlazarus@xxxxxxxxxxxx> ha
scritto:

Marco,

Note that if the job ends abnormally after the delete and before the
restore, you'll likely lose those objects in the target library, since
the *SAVF in QTEMP will have disappeared.

-mark

On 2/1/2024 1:42 PM, Marco Facchinetti wrote:

Hi Dave, up to me the safest way to do this kind of things is:
- Create a SAVF in qtemp
- Save all what you need using SAVOBJ
- Delete the objects in the target library
- Restore in the target library using RSTOBJ
- Grant aut's on the new objects.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno mer 31 gen 2024 alle ore 18:30 Dave<dfx1@xxxxxxxxxxxxxx> ha
scritto:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.