A few more points about grouping, of which I'm a big fan. -- Grouping can be used for LPARs as well as CECs. Hard-to-distinguish LPAR names can also be made more distinct with creative group naming, including multi-word labels.
-- Unlike early implementation in the 90s, a group can be embedded within another group. In other words, groups can be hierarchical. A well-constructed group array can mask lower-level ambiguities. Just drill down from the work space icon to the actual object. -- An object or group can belong to more than one group according to your needs. -- Grouping makes no serious changes to the HMC landscape. If you set up definitions that you don't like, you can delete and redefine over and over until you're satisfied. (Been there.) Having said all this, I'd like to reiterate that nothing beats starting with good names in the first place for both CECs and LPARs. In a past discussion of CEC naming, it seemed that some customers believe that names are delivered from on high along with the product. Not so. If you do not give your CE (substitute label de jour) guidance, she may follow some conventional practice and create, say, P+serial#. But a new CEC is a tabula rasa. Within syntax limits, you can call it anything you like. You do have to synchronize HMC with IODF. Other than that proviso, let your mind run free. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of R.S. > Sent: Thursday, January 7, 2016 11:33 PM > To: [email protected] > Subject: [Bulk] Re: Change CPC name in HMC > > I think, grouping doesn't help me. > Why I'm considering CPC name change: there are two machines managed by > the HMC, the serial numbers and it's names are the same with one character > exception. This is error prone. More: LPARs view shows all the LPARs from > both machines. LPAR names are different for each machines, but also there is > only one character of difference. > So, imagine "P0012345:LPN00T vs P0012435:LPM00T". Both describe tech > LPAR, but on different machines. Easy to mismatch when drag'n'dropping > some icon. > So, I would like to have "FRANKIE:LPN00T vs MARY:LPM00T". Not to mention > It's easier to say "FRANKIE" than "P0012435" by the phone. > > I'm going to do some tests now. > Thank you all, who responded. > > Regards > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > W dniu 2016-01-07 o 23:44, Skip Robinson pisze: > > I for one had a different interpretation of 'rename'. You just want an icon > > on the HMC to have your own 'nickname'? True CEC name still P+serial#? > What > > I would do/have done in the past is this. Very simple and requires no > > refresh. And no ill consequences if it's not right the first time. > > > > 1. Go into the 'grouping' function. > > 2. Create a new group for the CEC. > > 3. Assign one only one item to this group: your CEC with its natural born > > name. > > 4. Name the group with your desired nickname. It's not limited to 8 > > characters. You can force a name to multiple lines with a special delimiter > > that used to be documented in the Help file. I think it's vertical bar '|'. > > 5. From now on your nickname will appear in the work space. When you > click > > on it, you will see the true name, but for practical purposes you will see > > the nickname. > > > > I apologize if you want something different. > > > > . > > . > > . > > J.O.Skip Robinson > > Southern California Edison Company > > Electric Dragon Team Paddler > > SHARE MVS Program Co-Manager > > 323-715-0595 Mobile > > [email protected] > > [email protected] > > > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] > >> On Behalf Of Ted MacNEIL > >> Sent: Thursday, January 7, 2016 10:47 AM > >> To: [email protected] > >> Subject: [Bulk] Re: Change CPC name in HMC > >> > >> We 'had' to do this, once. > >> IBM originally recommended that LPAR names be independent of the > 'name' > >> of the image name running within it. > >> > >> Then, with GDPS, they recommended the reverse. The implementation > went > >> without a hitch. > >> All our reporting/billing? Not so well. > >> > >> - > >> -teD > >> - > >> Original Message > >> From: Skip Robinson > >> Sent: Thursday, January 7, 2016 10:59 > >> To: [email protected] > >> Reply To: IBM Mainframe Discussion List > >> Subject: Re: Change CPC name in HMC > >> > >> First off, you can name a CPC anything you want within the syntax rules. > >> Ideally you should pick a good name at initial install, but it can be > > changed > >> later. That being said, after we installed z12s in a new data center in > > 2013, we > >> intended to rename the z196 remaining in the old data center. We never > got > >> that done because we had never actually renamed a box before and were > >> wary of what it would take to accomplish without disruption. Nothing > > crucial > >> depended on a rename, so we shined it on. The name is embodied in two > >> places: > >> > >> -- The IODF names all processors. > >> -- The HMC/SE names each processor in several places from POR (Reset) > >> profile onward. > >> > >> IODF and HMC must agree. For a new box, this is not so hard. The trick is > >> make a change without hosing up the environment. Also consider other > >> implications: > >> > >> -- BCPii must also be updated. I consider that part of the HMC/SE tasks > >> above, but don't overlook it. > >> -- POR will be required. > >> -- SMF records contain the CPC name. Any post processing must take a > >> change into account. > >> -- It's not uncommon for various automation processes to refer to CPC by > >> name. Again, allow for this. > >> -- Many folks in the IT community may be attached to the old name in > >> various ways. Any change must 'socialized' thoroughly. > >> > >> I suggest you pick a name that you won't regret later. Consider the > > effects of > >> future model upgrades, workload repurposing, and physical relocation. > >> However, if an upgrade involves a transition period where both old and > new > >> boxes must coexist, you need two separate names at least for a while. I > > can > >> see the appeal of serial number to avoid these conundrums, buy as you > note > >> the number is meaningless to all but a handful of infrastructure geeks. > >> > >> . > >> . > >> . > >> J.O.Skip Robinson > >> Southern California Edison Company > >> Electric Dragon Team Paddler > >> SHARE MVS Program Co-Manager > >> 323-715-0595 Mobile > >> [email protected] > >> [email protected] > >> > >> > >>> -----Original Message----- > >>> From: IBM Mainframe Discussion List [mailto:IBM- > >> [email protected]] > >>> On Behalf Of Elardus Engelbrecht > >>> Sent: Thursday, January 7, 2016 04:56 AM > >>> To: [email protected] > >>> Subject: [Bulk] Re: Change CPC name in HMC > >>> > >>> Tony Thigpen wrote: > >>> > >>>> I have done such a change on two z10s with good results. The third time > >> did > >>> not go so well. For some reason, the secondary cpc did not change. > >> Everything > >>> looked ok until we did a POR, then it would not come up. We had to > > restore > >> the > >>> CPC. > >>> > >>> Ouch. Where is that behaviour documented? > >>> > >>> Do you get a warning during the renaming that an upcoming POR may > fail? > >>> > >>>> I don't know what went wrong, but after that, we no longer change the > >>> names. > >>> > >>> Now you got a new scar and a T-shirt as a bonus ... :) > >>> > >>> I would also not repeat that stunt after one failure. > >>> > >>> Groete / Greetings > >>> Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
