Re: Back Tracking wrkhdwrsc *cmn (controllers created via HMC/LPARS) ?

Kirk I can't seem to back track this at all, this is what it shows:

U8203.E4A.10002C6-V1-C7



On Wed, Jun 20, 2012 at 5:17 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

I think you are talking about the vSCSI controllers. If you are, the
location listed in WRKHDWRSC *CMN will contain the vSCSI number you
assigned it. I don't have a system to access at the moment but the
location will loc like xxxxxx -V20 for vSCSI controller 20.

Something I do is Number my vSCSI controllers to match the LPAR so LPAR2
controllers are 20, 21 etc as needed. LPAR3 are 30,31 etc. so a they self
document.


On Wed, Jun 20, 2012 at 1:10 PM, Jack Kingsley <iseriesflorida@xxxxxxxxx

wrote:

If I create a new LPAR on the HMC it creates a 290B CTLXX controller.

How

can I back track the controller that was created on the HMC to know which
LPAR is correpsonds to. The wrkcfgsts *nws will show me the relationship
from the i5/os side but how can I back track it to the hmc lpar setups.
--
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.

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