Expand Configuration and Management Manual (H06.21+, J06.10+)

Subsystem Control Facility (SCF) Commands
Expand Configuration and Management Manual — 529522-013
14 - 70
PRIMARY PROCESS Command
PRIMARY PROCESS Command
The PRIMARY PROCESS command causes the backup process to become the
primary process and the primary to become the backup. PRIMARY PROCESS is a
sensitive command.
The PRIMARY PROCESS command has this syntax:
line-name | path-name
is the name of the line or path to be switched to the backup processor.
$NCP
causes the backup processor to become the primary processor and the primary to
become the backup for $NCP.
cpu-number
is the processor number that will now become the primary processor for the
specified line or path.
Considerations
•
If the specified processor is not either the backup or primary processor, an error is
returned.
•
If the specified processor is currently the primary processor, a warning is returned.
•
The PRIMARY PROCESS command is not supported directly for Expand-over-IP
or Expand-over-PTCPIP line-handler processes. However, if you want to switch an
Expand-over-TCPIP or an Expand-over-PTCPIP line to the backup CPU, you can
abort the line handler, use the PRIMARY PROCESS command, and then restart
the line in the backup CPU.
•
The PRIMARY PROCESS command is used after an ABORT PATH command to
switch to the backup $NCP and reinitialize the node. See
Node Not Available on
page 20-33.
•
You can switch processors for objects with a single PRIMARY PROCESS
command by specifying multiple objects using parentheses as:
PROCESS ( object-name , object-name [ , object-name ] ... )
Examples
This SCF command causes the backup processor (CPU 6) to become the primary
processor and the primary to become the backup for $LINEX:
-> PRIMARY PROCESS $LINEX, 6
PRIMARY PROCESS { line-name | path-name | $NCP } , cpu-number