SCF Reference Manual for G-Series RVUs (G06.27+)

Using SCF to Configure and Manage NonStop
S-Series Servers
SCF Reference Manual for G-Series RVUs—520413-005
1-15
Running SCF in a Network
Running SCF in a Network
The behavior of SCF on mixed systems, that is, a network including G-series, D-series,
and C-series systems, is affected by the PIN configuration of the Subsystem Control
Point (SCP) and the site from which you choose to perform intersystem management.
Running SCP at a High PIN
SCF is configured to run at a low PIN.
Although the SCP is delivered as a low-PIN process, it can run at either a high PIN or a
low PIN. However, when run at a high PIN, it cannot communicate with processes
located on a C-series system.
You can use the Binder tool to change SCP to a high-PIN process. For instance, a
super-group user (255,n) can use the following BIND commands to change the SCP
process from a low PIN to a high PIN:
@ADD * FROM SCP
@SET HIGHPIN ON
@BUILD SCPNEW!
SCF always starts subsystem product modules at a low PIN. Refer to the appropriate
subsystem-specific SCF reference manual for more information about running SCF in
mixed-system environments.
The following figures show SCF communications permitted within and between nodes
of a network.
Figure 1-3 shows the communications paths available to a low-PIN process on a
G-series system, illustrated as $SCF1. $SCF1 can communicate with a low-PIN
process, such as $SCP1, on a D-series or G-series system; $SCF1 can also
communicate with high-PIN processes, such as $SCP2 and $SCP3. Further, $SCF1 is
accessible from a system on a C-series system, so $SCF1 can communicate with
$SCP4.