Re: Migration to New 825

>From a design point and from a Backup and Recovery point, it's a poor idea
to have LF's in different libraries than their PF's.  Also, although access
paths can be saved, they cannot be restored.  (About as exciting as kissing
your sister.)

If from a design perspective, have LF's in a different library than the
PF's, the library should be higher in alphabetic order than the PF's, so
they do restore on a RESTORE option 21, but the access path will have to
rebuild.

If you don't know what you have, there is a TAA Tool to tell you.  See:

http://www.taatool.com/document/L_chkalldbd.htm

A

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com


midrange-l-bounces@xxxxxxxxxxxx wrote on 06/25/2003 07:23:46 PM:

> I just read through Appendix E of the Backup & Recovery guide on
migrating
> to a different server.  I was surprised that I didn't see any mention on
> special steps to restore logical files.  It has always been my experience
to
> take a 2nd pass with a RSTLIB SAVLIB(*ALLUSR) DEV(TAP01) ENDOPT(*UNLOAD)
> OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL) .  Followed by a RSTAUT.  This
> pass catches LFs that are in libraries different that their PFs that
> couldn't restore on pass one.
>
> Don't I need to do this for LFs when doing a restore option #21 (full)?
And
> the RSTAUT was not documented, again not needed?
>
> This will be migrating into a new LPAR partition.
>
> ---
> Doug Hart
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>