Even though IBM has created/developed the DRID, which would handle the restore of the LF, the access paths were probably not saved because they didn't meet the save rules.

The system saves access paths that logical files own, and that are not used for referential constraints if all of the following are true:

You specify ACCPTH(*YES) on the save command for the physical files.
All based-on physical files under the logical file are in the same library, contain data, and are being saved at the same time on the same save command.
The logical file is MAINT(*IMMED) or MAINT(*DLY).

We have some x-lib LF.
So for the large LF, my save process moves the LF to the same library of the PF, for the save, then after the save it gets moved back.
This way the LF and access paths are save, thus restore time is quicker when needed.


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, October 21, 2021 1:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Logical files not in same library as physical files

If you don't have to, then don't.
The argument comes down to understanding why you would ever want to. I'd argue there are a few cases for this. This is not one of my "don't ever do!" items.
When you restore IBM i can 'defer' the restore of the logical files until the physical file is restored (with currently supported versions of the OS).

If you have two disparate vendors with their own data libraries and you want to build a logical joining them, you may end up with a cross library logical.

Rob Berendt
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Richard Reeve
Sent: Thursday, October 21, 2021 11:11 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Logical files not in same library as physical files

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


I know that we can create logical files in different libraries than
the physical files, but I don't like that idea. What are your thoughts as
to the advantages/drawbacks of the multi library approach?

All the best,

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

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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.