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

Using SCF to Configure and Manage NonStop
S-Series Servers
SCF Reference Manual for G-Series RVUs—520413-004
1-14
Performing Online Configuration Changes on a
Remote System
nonsensitive commands, such as INFO and SETPROMPT.) See page 5-15 for the
lists of sensitive and nonsensitive SCF commands.
Standard file-system security restricts access to a saved system configuration file
based on its file security attributes.
The owner of a generic process can also issue sensitive commands to it. Generic
processes are described in the SCF Reference Manual for the Kernel Subsystem.
Performing Online Configuration Changes on a Remote System
To install a new RVU or make a major system configuration change on another system
in the network, you create an SCF command file on the local system for the new
remote configuration. Doing this has no impact on the performance of the current
running system. If you want, you can test the new configuration on a stand-alone test
system. Then you implement the new configuration by moving the command file to the
remote system, loading that system, and running SCF with the command file as input.
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.
Caution. Do not change the security of the current CONFIG file. $ZCNF has exclusive access
to this file.