More than likely what was clobbered were the IBM libraries that were already
there. IE: QGPL, QUSRSYS, SYSIBM, .....

I have successfully moved partitions in the way you are suggesting but you
need to treat the IBM supplied libraries differently.

With QUSRSYS and QGPL only restore *NEW objects, that way you'll get
everything that has been stuffed in those to libraries without overwriting
the existing IBM objects. If you modified the IBM supplied subsystem
definitions then you will have to manually make those changes. (Hint:
Always make a copy of a subsystem into your own library, modify it and use
that one, not the IBM Supplied subsystems)

Networking and work management changes need to be done manually.

Never restore IBM supplied user profiles. (Q******)

Avoid restoring in to the other IBM supplied libraries, they are mostly
maintained by system level functions anyway.

Above all make sure you start and stay in a restricted state until all the
restores are done, and you run RSTAUT.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Mitchell, Dana
Sent: Thursday, December 04, 2014 10:53 AM
To: Midrange Systems Technical Discussion
Subject: Opinions sought moving LPARs to new CEC

We are moving 8 IBM i 7.1 lpars from a P7 to a new P8 machine. According to
IBM, the process to use is SAVE 21 and restore as described in Appendix D
'Recovering your system to a different system' in the 'Recovering your
System' manual.

My question relates to the fact that the existing lpars are at TR4 and thus
won't run on P8 without at least TR8 applied. I was hoping to avoid having
to apply maintenance to all 8 LPARs before moving them. I tried doing an
install of 7.1 and all maintenance on the new hardware, then just a Restore
23 userdata but that broke things that was messy to clean up afterwards.

Has anyone attempted anything similar and found an easier way?


Attention: This electronic document and associated attachments (if any) may
contain confidential information of the sender (SHAZAM Network) and is
intended solely for use by the addressee(s). Review by unintended
individuals is prohibited. If you are not the intended recipient: (i) do not
read, transmit, copy, disclose, store, or utilize this communication in any
manner; (ii) please reply to the sender immediately, state that you received
it in error and permanently delete this message and any attachment(s) from
your computer and destroy the material in its entirety if in hard copy
format. If you are the intended recipient, please use discretion in any
email reply to ensure that you do not send confidential information as we
cannot secure it through this medium. By responding to us through internet
e-mail, you agree to hold SHAZAM, Inc. and all affiliated companies harmless
for any unintentional dissemination of information contained in your
message. Thank you.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

This thread ...


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

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