In the absence of encouraging advice, I went ahead and PORed the CEC, which implemented the correct LPAR name. It's a new machine with no production images yet, so no loss. I was hoping to learn something for a future case where POR would be highly unwelcome. Oh well.
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Alan Field <[email protected]> To: [email protected], Date: 05/10/2013 08:39 AM Subject: Re: Renaming an LPAR dynamically Sent by: IBM Mainframe Discussion List <[email protected]> Skip, I recall trying this once. When I converted the name to * it lost all the chpid/device info. I decided that the function was pretty useless (as far as renaming an lpar) is concerned. Alan Field Technical Engineer Principal BCBS Minnesota Phone: 651.662.3546 Mobile: 651.428.8826 From: "Skip Robinson" <[email protected]> To: [email protected], Date: 05/10/2013 09:48 Subject: Renaming an LPAR dynamically Sent by: IBM Mainframe Discussion List <[email protected]> I've poked around and not found a concise explanation. We have an LPAR whose name needs to change. Everything else in the IODF is fine, just a name problem. Current hardware and software. I changed the name in HCD. When I tried to ACTIVATE the new IODF, it choked on the name mismatch. I gather that I can first rename to '*', then rename for real in two successive IODFs. If I do that, do I preserve all original chpid and device connections? I don't want to start over from scratch when only the name is wrong. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
