Renaming an LPAR dynamically

Skip Robinson

unread,

May 10, 2013, 10:48:14 AM5/10/13

to

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.

.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
JO.Skip....@sce.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN

Barry Merrill

unread,

May 10, 2013, 11:00:48 AM5/10/13

to

FWIW when you rename an LPAR, the LPAR NUMBER can change since
the LPAR numbers are now assigned alphabetically to LPAR names.

Barry Merrill

Herbert W. "Barry" Merrill, PhD
President-Programmer
MXG Softtware
Merrill Consultants
10717 Cromwell Drive
Dallas, TX 75229
ba...@mxg.com

http://www.mxg.com - FAQ has Most Answers
ad...@mxg.com - invoices/PO/Payment
sup...@mxg.com - technical
tel: 214 351 1966 - expect slow reply, use email
fax: 214 350 3694 - prefer email, still works

Bill Johnson

unread,

May 10, 2013, 11:25:31 AM5/10/13

to

Some software, the Control products from BMC come to mind have the LPAR name embedded in some of the datasets and will not work if you change the LPAR name dynamically.

________________________________
From: Skip Robinson <Jo.Skip....@SCE.COM>
To: IBM-...@LISTSERV.UA.EDU
Sent: Friday, May 10, 2013 10:48 AM

Subject: Renaming an LPAR dynamically

Staller, Allan

unread,

May 10, 2013, 11:33:34 AM5/10/13

to

Last I heard, the LPAR must be deactivated/renamed/ activated

HTH,

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.

</snip>
.

Martin Packer

unread,

May 10, 2013, 11:38:19 AM5/10/13

to

Not to disagree but how does User Partition Number play into this? (FWIW
my code now displays both partition numbers.)

Cheers, Martin

Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM

+44-7802-245-584

email: martin...@uk.ibm.com

Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Alan Field

unread,

May 10, 2013, 11:39:17 AM5/10/13

to

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" <Jo.Skip....@SCE.COM>
To: IBM-...@LISTSERV.UA.EDU,
Date: 05/10/2013 09:48
Subject: Renaming an LPAR dynamically

R.S.

unread,

May 10, 2013, 1:06:17 PM5/10/13

to

W dniu 2013-05-10 16:48, Skip Robinson pisze: > 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. I think that it is impossible. BTW: WHY? Why do you need to change LPAR name? The only thing I can imagine (except naming convention, and aesthethics) *was* requirement for zNALC (and previously for z/OS.e) which required lparname to begin with some string (ZNAL and ZOSE). Radoslaw Skorupka Lodz, Poland tej wiadomo ci mo e zawiera informacje prawnie chronione Banku przeznaczone wy cznie do u ytku s bowego adresata. Odbiorc e by jedynie jej adresat z wy czeniem dost pu os b trzecich. Je eli nie jeste adresatem niniejszej wiadomo ci lub pracownikiem upowa nionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dzia anie o podobnym charakterze jest prawnie zabronione i mo e by karalne. Je eli otrzyma wiadomo omy kowo, prosimy niezw ocznie zawiadomi nadawc wysy c odpowied oraz trwale usun wiadomo czaj c w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: in...@brebank.pl d Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru S dowego, nr rejestru przedsi biorc w KRS 0000025237, NIP: 526-021-50-88. ug stanu na dzie 01.01.2013 r. kapita zak adowy BRE Banku SA (w ca ci wp acony) wynosi 168.555.904 z otych. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN

Skip Robinson

unread,

May 10, 2013, 6:16:53 PM5/10/13

to

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
JO.Skip....@sce.com

carlos roberto visconde

unread,

May 18, 2013, 5:36:06 PM5/18/13

to

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 <Jo.Skip....@sce.com>

Skip Robinson

unread,

May 19, 2013, 10:50:22 AM5/19/13

to

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
JO.Skip....@sce.com

From: carlos roberto visconde <cvis...@IG.COM.BR>
To: IBM-...@LISTSERV.UA.EDU,
Date: 05/18/2013 02:36 PM
Subject: Re: Renaming an LPAR dynamically
Sent by: IBM Mainframe Discussion List <IBM-...@LISTSERV.UA.EDU>

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 <Jo.Skip....@sce.com>

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

carlos roberto visconde

unread,

May 19, 2013, 8:07:08 PM5/19/13

to

My sugestion was to you avoid POR, with that procedure only the LPAR you
had to put PCHID and Crypto processor offline and after online, woud be the
LPAR you had to rename.

2013/5/19 Skip Robinson <Jo.Skip....@sce.com>

carlos roberto visconde

unread,

May 27, 2013, 5:35:59 PM5/27/13

to

As you do not change all the other original LPAR attributes and
connections, those will remain intact after first becoming '*'.

2013/5/19 Skip Robinson <Jo.Skip....@sce.com>