Created the LPARs today manually as Rob suggested - that was always my plan
b anyway, but it's something of a drag and annoying to have to re-do
something that's been done using the system planning tool. I've previously
used the export function with no problems (on the advice of my p buddies who
were using it all the time).
The level on the HMC doesn't look that far back to me looking at the HMC
support web site but I'll confess comprehending that site needs a whole lot
more time than I gave it. Since the System planning tool was the absolute
latest and greatest (downloaded fresh that morning) I agree it's possible
the HMC needs to be updated again to keep them in lock step. If that's the
case though, they should really specify which versions of the HMC the SPT
supports/can be used with, or better yet, just make it work properly.
I might ask one of my IBM buddies but I mainly wanted to see if it was
something obviously stupid I was doing that would provide a quick way
forward.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Wednesday, 28 April 2010 8:08 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: HMC System Plan Deployment error
I believe that version of HMC code level to be somewhat old, I have worked
on the HMC for a while now but I have never attempted to do a System Plan
Import. If you have IBM support I would call them and see what they say, if
your sure the machine can support LPAR etc then I would probably move
forward if time is an issue and go the route that Rob has specified.
On Tue, Apr 27, 2010 at 3:56 PM, <rob@xxxxxxxxx> wrote:
As an Amazon Associate we earn from qualifying purchases.
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.