I came in the middle of this discussion, so I am sorry if I repeating something already stated, that you might need to review.

If you do a SAVE 21 RESTORE 21 IBM supposedly gets everything you need, but if you do selective restore, you can have a problem if LF in different library from PF it is for.

We are on BPCS in which each environment (data base) has PF with SAME NAME as in each other, along with a pile of LF to point at the PF in that data base. LF out of the box from the vendor are in same library as PF, LF that we add are in a library with a different name.

Now when you do a restore of several libraries, they get restored in alphabetical name sequence of the libraries. Let's suppose library with PF is restored first, all well and good, but suppose library with LF is named alphabetically before library with PF they pointed at, basically you lose the LF, and have to know this, so you can restore those LF after you got the PF restored.

Not supposed to happen, but sometimes when we copy files from one environment to another, can end up with LF of one environment pointing at PF in another environment. Use DSPDBR to check what's pointing where, and know naming conventions to see if any messed up.

Assuming you have the source code for the LF, you can always delete the LF and recompile, since the data is in the PF, but then you have to make sure you got all the right members are in which LF. There is a ceiling on how many members can be in an LF like 32, and some of our PF have in excess of 200 members.

Hummm, you started my mind a-thinking when you said that LF created
without PFs can cause the  problem of misdirection.   This I'll have to
check further with my systems programmer.   I can see a by-name object
comparison coming up and more.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.