• Subject: Re: Logicals over a physical in a different library
  • From: "Al Barsa, Jr." <barsa2@xxxxxxx>
  • Date: Tue, 12 Oct 1999 15:04:26 -0700

At 07:34 AM 10/11/1999 -0500, you wrote:
I'm putting together some updated information for our Disaster Recovery
restore procedures.
Has anyone got a utility or a method of determining which physical files
have a logical over them that is stored in a different library?   Other than
checking each one! ;-)


There's a command in TAA Tools called Check Database Dependances (CHKDBD).

Obviously, the logicals won't restore if the physical isn't there.....
A good rule of thumb is to *NEVER put a logical into a different library, however if you must (sometimes there are business reasons), then to put the logical in a library higher in alphabetical order than the library of the physical.  In this case, the logical will restore, but the access path will have to be rebuilt (if there was one, which there typically is), even if you saved with ACCPTH(*YES).

BTW, you should never *ALWAYS save access paths by specifying ACCPTH(*YES) on the SAVLIB, SAVOBJ and SAVCHGOBJ command unless you are *SURE that the access path(s) won't restore (i.e.: physicals and logicals in different libraries).

Al




+--------------------------------------------------+
| Please do not send private mail to this address. |
| Private mail should go to barsa@ibm.net.         |
+--------------------------------------------------+

Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:          914-251-1234
Fax:            914-251-9406
http://www.barsaconsulting.com
http://www.taatool.com

This thread ...

Replies:

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

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