Planning to choose feasible CPC names
To identify an IBM Z CPC by name, the console name of the attached SE is used within the console UIs and APIs. This name is factory preset to Pxxxxxxx, where xxxxxxx is the machine serial number. The SE also has a netid, which is factory preset to IBM390PS. The SE console name is always taken as the CPC name in the IBM Z console environment, you cannot change this. However, you can customize the SE console name and the netid. Note, that a Netid.console_name SNA style address will be used internally for BCPii communication although SNA itself is not involved. SA z/OS® response reports from the IBM Z hardware also contain this address.
IBM operating systems, IO configuration programs (HCD), and systems management platforms (SA z/OS) tolerate to use CPC names that are not identical to CPC SE console names. IBM recommends that CPC names should not contain mainframe device-type numbers or IBM mainframe brand names, as they could eventually cause additional name change efforts, in case you migrate to a mainframe of different type or brand name. Note that z/OS takes the CPC name of the in-memory IODF data at system IPL time. IODF data sets are created by the IO configuration program.
SA z/OS recommends that you customize the CPC SE console netid in a way that it can be used to identify your own enterprise or internal organization. The SE console name should be shorter than the allowed 8 characters. This SE console name is also used as CPC name in the HCD-IODF configuration utility, so that in the end z/OS uses this name as its local CPC name. SA z/OS and other applications can use the compact name to establish a prefix-appendix scheme to combine the SE console name, which is also the CPC name, with additional criterion markers of your choice, all pointing to the same CPC.
Example
IBM factory set SE console name..P004711
IBM factory set SE netid.........IBM390PS
is changed to:
User customized SE console name..CLOUD7
User customized SE netid.........MYCORP11
and used with the IO configuration utility to define:
HCD CPC name.....................CLOUD7
which will be used by z/OS as:
local CPC name...................CLOUD7
SA z/OS PDB definition:
PDB processor entry Name.........CLOUD7
HW Resource Name.................CLOUD7
Network Name.....................MYCORP11
ProcOps Target HW Name...........$CLOUD7
The previous example illustrates how to use the name CLOUD7 persistently to identify the unique
IBM Z mainframe of the MYCORP11 company to the various functions or services that need this name,
including SA z/OS. The $ prefix was chosen to enable parallel usage of SNMP and
INTERNAL protocols for CLOUD7 in SA z/OS, so ProcOps and for instance GDPS can both monitor this
mainframe.