Creating a New Processor

How to create new policy objects in general is described in How to Create New Policy Objects.

Figure 1 shows the panel for defining a new Processor policy object.

Name

The processor name must have 1 to 8 alphanumeric characters and must begin with an alphabetic character, #, $, or @. The name must be different from the names of all groups, subgroups, systems (including the processor operations names), and processors defined in the current policy database.

Processor Type

Specifies the processor machine type of the target hardware. Select a name from the list shown to specify the processor type.

Use the generic type name Mainframe to specify the IBM® System z Mainframes supported in SA z/OS.

The actual processor type is determined at SA z/OS processor operations runtime when a target system associated with the target hardware is initialized. The default is Mainframe.

Use the type PSM to specify a ProcOps Service Machine on VM as virtual hardware for VM guest systems. For more details about the PSM, see IBM Z® System Automation Customizing and Programming.

Mode

Specifies the operating mode of the processor hardware as defined in the Reset Profile that is used for hardware activation. For zSeries, 390-CMOS in logical partition mode, and PSM processors specify LPAR. Note that for processors of type PSM, the mode is forced to LPAR.

Connection Protocol

Indicates the protocol used for communication with the processor:

INTERNAL

Connection via the operating system (BCPII).

SNMP

Connection through TCP/IP network or BCPii redirection.

TCPIP

Connection through TCP/IP. It is the only valid connection protocol for processors of type PSM.

You can also specify multiple values in this field.

HW Resource Name

Specifies the network addressable unit name (NAU) of the local support element attached to the CPC for processors of type Mainframe. On the HMC/SE this name is shown as the second part of the SNA address when viewing the CPC's network information details. The SNA address is needed to identify uniquely the processor in a CPC LAN. In addition, the CPC name is part of the internally built security resource name for SAF checking purposes.

For processors of type PSM this definition is only used as the security resource name for SAF checking purposes.

Network Name

Specifies the name of the SNA network in which the support element resides for processors of type Mainframe. On the HMC/SE this name shown as the first part of the SNA address when viewing the CPC's network information details. The SNA address is needed to identify uniquely the processor in a CPC LAN. In addition, the network name is part of the internally built security resource name for SAF checking purposes.

For processors of type PSM this definition is only used as the security Network Name for SAF checking purposes.

The following specification is for INTERNAL and TCPIP processors:

Auth Token

Specifies an acronym for the community name setting made in the support element for processors of type Mainframe and connection protocol INTERNAL. The setting is used to validate the connection. For processors of type PSM it is the authorization token for TCPIP connections. (TCPIP is the only possible connection protocol for ProcOps Service Machine.)

The following specifications are for SNMP processors:

Community Name

Specifies the community name of the support element. It is defined at the support element, and is used to validate the connection. It is only used for SNMP Version 2.

Note: If you want to use SNMP Version 3 specify NONE. Be aware that for SNMP Version 3 additional definitions have to be done in policy PROCESSOR INFO.

ProcOps Target HW Name

Specifies the name that the Processor Operations feature of SA z/OS knows the processor by. For processors with only SNMP specified as connection protocol, this name is defaulted to the processor's entry name. If you specify multiple connection protocols this field is required and must be different from the processor's entry name.

The name must be unique among the names of groups, subgroups, systems (including both the entry names and system/image names) and processors (including both the entry names and the Processor Operations Target HW names) in the current policy database.

The following specifications are for SNMP and TCPIP processors:

TCP/IP Address or Hostname - Alternate Address or Hostname

Specifies the TCP/IP address or symbolic hostname for communication with the target hardware, for these communication protocols, the ProcOps Service Machine.

At least one address is required for SNMP and TCPIP connections.

For SNMP connections both addresses might be specified. The first address is used for the support element first adapter address and the alternate is used for the second adapter address or HMC. If both are specified, the support element first adapter address has preference and the second adapter address can be used to recover from adapter failures.

Use the ProcOps focal command point ISQIPSWT to perform the switch from the first to the second adapter address. Depending on the Support Element version, a second adapter with an alternate may not be supported.

A HMC address alone may be considered if multiple processors should be controlled via one single connection.

The following specification is for SNMP processor connections only:

ISQET32 for BCPii redirection

A hostname value of ISQET32 causes to use the BCPii connection to the target hardware Support Element, bypassing the IP network. BCPii redirection always targets the SE, even if specified for an HMC. Note that these redirected BCPii connections are part of the ProcOps SNMP protocol implementation.