× 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.



As a novice when it comes to configuring a new system, I have some questions.

I'm assuming that the Hypervisor is what is really running at the lowest level of the system hardware, and the HMC is controlling the configuration of the LPARs, with the cooperation of the Hypervisor.

Since that's the case, is it valid to say that any LPAR is hosting the other 3? Isn't it really the Hypervisor?

Memory is fluid-- and can be (re-)allocated on-the-fly, as can processor resources. So they're not really allocated unless the HMC gets involved.

I know you can have certain hardware hard-wired to certain LPARs, and shared to the other LPARs, but changing these 'allocations' (sometimes) requires a power-down of the whole thing and re-arranging cards.

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, November 01, 2018 3:18 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: P7 V7R3 to P9 V7R3 migration recommendations / suggestions
...

I'd like to make a suggestion. Instead of Production being your owning
LPAR make your DSLO combined image your hosting lpar. This way, you can
migrate it first, with no pressure or time constraints. Once it is there
then you can start creating the image catalogs and nwsd's for the guests.
Again, no time pressures. For grins and giggles you can try another BRMS
save of the old DSLO lpar and restore that as a guest lpar, on your new
machine. Just to test your BRMS save/restore. Again, no time
constraints. Once you have that figured out, tape and comm guesting
tested you can initialize it and start restoring the other lpars as fits
your schedule.

Rob Berendt
---
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 11/01/2018 02:43 PM
Subject: P7 V7R3 to P9 V7R3 migration recommendations /
suggestions
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
...

I'm reviewing the options for doing a P7 V7R3 to P9 V7R3 migrations.
Four LPARs, Production, R&D, Sandbox, DSLO combined image.
Currently, each LPAR has their own hardware resources.
Going forward, on the P9, Production will own all hardware, other LPARS
will be hosted clients.
...

Thank You

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.