Mapping Processor Hardware Interface Items to Customization Dialog
Table 1 lists the functional elements of the processor hardware interfaces shown in Connectivity and Functionality at a Glance and shows their relationship to the related policy entries in the System Automation Customization Dialog.
Not all required data input fields of the listed policy entries are referenced in this table. To learn more about these policy entries and all required customization input data, see "Entry Type Reference", sections "Processor Entry Type", "System Entry Type" in IBM Z System Automation Defining Automation Policy.
Some policy entry customization items must also be defined in the SE or HMC configuration settings. Make sure that these definitions are identical in their readable form. An example of such items is the Auth Token, which is needed for an INTERNAL connection definition and must be defined in uppercase. See Hardware Preparation for more information.
| Processor Hardware Interface Items | Policy Entry | Related Policy Information and Comments |
|---|---|---|
| z15 | PRO (Processors) | Policy: Processor Information Fields: Processor Type, Processor Mode, HW Resource Name, Network Name No processor hardware-specific name or device type must be defined. Use the generic type name Mainframe to classify the processor as real hardware. By default, the Mode is set to LPAR. This is correct for all supported mainframe processors. Your mainframe processor must have an address in the (SNA) format: Network_Name.NAU. The IBM mainframes have a factory set network name of IBM390PS and a NAU name that is derived from the unique CPC serial number. Both names can be changed by the customer. The SNA format processor address is stored in the SE and can be determined with the SE or HMC (CPC details). |
| CPC Support Element | PRO (Processors) | Policy: Processor Information Field: TCP/IP Address/Hostname or identifier ISQET32 for BCPii redirection Make sure that the address is valid in your customer network and that the host name gets correctly resolved. |
| HMC1, HMC2 | PRO (Processors) | Policy: Processor Information Field: Alternate Address/Hostname or identifier ISQET32 for BCPii redirection Make sure that the address is valid in your customer network and that the host name gets correctly resolved. If you have multiple HMCs in your environment, make sure that the HMC that you plan to use for Processor Operations has your processor that is defined in its CPC group. |
| SNMP Path | PRO (Processors) | Policy: Processor Information Field: Connection Protocol The SNMP value enables Processor Operations SNMP communication. |
| TCP/IP Path | PRO (Processors) | Policy: Processor Information Field: Processor Type Use the PSM processor type to define a connection to a Processor Operations Service Machine, which is required to manage z/VM guests. This automatically assigns the connection protocol TCPIP for this processor. |
| INTERNAL Path | PRO (Processors) | Policy: Processor Information Field: Connection Protocol The value INTERNAL enables the BCPii connection protocol. |
| Logical Partitions (LPARs) | PRO (Processors) | Policy: LPARs and Systems Fields: LPAR Name, Target Mode, Target System Name Processor Operations requires that you define at least one LPAR of your CPC and assign a defined system to it. Otherwise, the interfaces do not work. |
| PSM | PRO (Processors) | Policy: Processor Information Field: Processor Type For the z/VM guest support, define a processor of type PSM. See Other functions for details. Policy: Guests and Systems Here you define the name of the virtual machine as defined on the z/VM host system, the architecture mode of the virtual machine, and the corresponding target system name. |
| z/OS A, z/OS B, z/VM A | SYS (Systems) and PRO (Processors) | Policy: Systems > System Information Fields: Operating system, Image/System name For a list of the supported operating system environments, see section Other functions for details. The Image/System name is used by Processor Operations as the target system name parameter to address commands to this system's CPC, LPAR, or integrated console. In LPAR Management commands, the target system name parameter is used as a shortcut of the parameter format processorname.LPARname. Policy: Processors > LPARs and Systems If you have not already assigned a system in the LPARs and Systems policy of the processor entry, link the target system to the LPAR that you want to use for this system. Unassigned target systems are ignored by Processor Operations. You can define a system entry for any of the supported operating systems. See Other functions for details. |
| z/VM guest | SYS (Systems) | Policy: System information Fields: Operating system, Image/System name The z/OS, z/VM, Linux for System z, and z/VSE operating systems are supported by Processor Operations as z/VM guest operating systems. The name that is defined as the Image/System name is identical to the operating system name, which might be different to the system entry name. The Image/System name is used by Processor Operations as the target system name parameter to address commands to this guest system's PSM, virtual machine, or console. |
| Usage Examples | SYS (Systems) | Policy: Target System Info, IPL Info In the Target System Info policy, you can specify if Processor Operations should start a connection to the processor hardware/LPAR of this target system automatically, after the Processor Operations initial startup is complete. In the IPL Info policy, you can specify for z/OS or z/VM target systems the automatic responses to important IPL operator prompt messages. |