Restoring to a new LPAR: QUSRSYS QGPL -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Restoring to a new LPAR: QUSRSYS QGPL
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 5 Apr 2018 13:16:50 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Oh, the tangled webs we weave.

1. Created new 7.1 LPAR
2. PTF'ed it to last *CUMPKG
3. Now want to do RSTLIB *NONSYS

Am I going to mess up the new LPAR if the LPAR I'm restoring from was
backlevel on PTFs?

I think I know the answer to this ...

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Restoring to a new LPAR: QUSRSYS QGPL , Musselman, Paul

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.