Operating the Processor Hardware Interfaces
The System Automation product offers two hardware interfaces. Depending on your processor policy protocol definitions, one or both hardware interfaces can be used after the System Automation agent is started.
INTERNAL path
This interface is based on the internal BCPii processor communication protocol and does not require TCP/IP or Processor Operations to be active. No start or stop commands are available to control the interface. It is activated automatically as part of the System Automation start. A session to the Support Element of your CPC is established after the BCPii start is complete. When the System Automation agent is stopped, the BCPii connection to the CPC is stopped.
The INTERNAL path is exclusively used by GDPS.
Processor Operations – SNMP path
This interface requires TCP/IP, or can be redirected to INTERNAL path by defining a hostname of ISQET32. The z/VM guest systems can be also controlled.
| Command | Description |
| ISQSTART | This command starts Processor Operations. Depending on your Processor Operations policy definitions for each entity, a Processor Operations connection is established to the target systems, CPC, and HMC. |
| ISQSTOP | This command stops Processor Operations. All active connections to the CPC, HMC, or z/VM PSM are closed. |
Operation
| Command | Description |
| ISQXDST | Processor Operations Status System dialog. Shows the status of the monitored components: processor (THW), system (TGT), and the communication link. |
| ISQCCMD | Interface to perform HW common commands, such as ACTIVATE, DEACTIVATE, or LOAD. |
| ISQSEND | The command communicates with the "Operating System Messages" integrated console (SE/HMC) for each LPAR, in order to send commands to and receive responses from the operating system running in this LPAR. |
Details about the hardware interface commands can be found in "Processor Operations Commands" in IBM Z® System Automation Operator's Commands.