I've known shops that let serial or model number creep into naming conventions. Like Mark, we control names across upgrades. Back in the Stone Age, IBM used to recommend embedding model number in SMF and JES names. And that required a cold start to change! Sort of nuts it seems to me.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Zelden Sent: Tuesday, April 26, 2016 3:09 PM To: [email protected] Subject: (External):Re: BCPii (Was: can a program determine the capacity setting of a z-box?) On Tue, 26 Apr 2016 13:25:45 -0700, Ed Jaffe <[email protected]> wrote: >On 4/26/2016 1:13 PM, Mark Zelden wrote: >> When my client replaces their CPCs the name is kept the same. For example >> CPCA, CPCB, CPCC, ... etc. The RACF profile is based on that name so >> nothing needs to be changed in RACF. > >A RACF SEARCH command produces the following profiles beginning with >HWI in the FACILITY class: > >HWI.APPLNAME.HWISERV >HWI.IBM390PS.P00C9632.HWISERV >HWI.TARGET.IBM390PS.P00C9632 >HWI.TARGET.IBM390PS.P00C9632.* (G) > >The P00C9632 qualifier is based on the serial number of our old CPC. >Our z13s was not an MES upgrade from the zBC12. It was a "net new" >machine and -- as such -- has a brand new serial number. (The zBC12 was >moved to our DR site.) > It sounds like that was your CPC name also. I have RACF profiles like the following and nothing needed to be changed when we rolled in 5 z13s late last year. HWI.CAPREC.IBM390PS.CF01.* (G) HWI.CAPREC.IBM390PS.CPCA.* (G) HWI.CAPREC.IBM390PS.CPCB.* (G) HWI.CAPREC.IBM390PS.CPCC.* (G) HWI.CAPREC.IBM390PS.CPCD.* (G) HWI.TARGET.IBM390PS.CF01.* (G) HWI.TARGET.IBM390PS.CPCA.* (G) HWI.TARGET.IBM390PS.CPCB.* (G) HWI.TARGET.IBM390PS.CPCC.* (G) HWI.TARGET.IBM390PS.CPCD.* (G) The RACF calls are based on the CPC name, not the definition in the HMC under the API settings. Since we kept the CPC names the change, nothing had to change in RACF. IBM copied over HMC settings as part of the migration (all 5 boxes, of which one is a stand alone CF, were all "net new" and the old ones returned to IBM). https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieac100/iea3c1_Authority_to_the_particular_resource.htm Best regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
