As I mentioned a follow-on post, I eventually PORed to get the new IODF active with no change other than LPAR name. It's not clear from Carlos's post that the all the other original LPAR attributes and connections would remain intact after first becoming '*'. If not, POR (in my particular case) was less painful than having to redefine everything else from scratch.
. . 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: carlos roberto visconde <[email protected]> To: [email protected], Date: 05/18/2013 02:36 PM Subject: Re: Renaming an LPAR dynamically Sent by: IBM Mainframe Discussion List <[email protected]> Yes, you have first rename the LPAR to '*', in IODF (IOCDS) Activate the IODF Deactivate the partition, uncheck to CRYPTO PROCESSORs of that partition, Activate the partition. (puting CHPIDS OFF) Deactivate the LPAR then active new IODF with new Name Chek the CRYPTO PROCESSORs, activate the partiiton 2013/5/10 Skip Robinson <[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
