K-Series to S-Series Differences

sequence, you can create additional startup files for the system, subsystems, system
software, processes, communication lines, and applications. For examples of startup
files:
For G06.21 and later, see the NonStop S-Series Hardware Installation and
FastPath Guide.
●
For G06.20, see the NonStop S-Series Hardware Installation Guide.●
For G06.19 and earlier, see the NonStop S-Series Planning and Configuration
Guide.
●
Configuring Devices and System Attributes Online
System files are handled differently in G-series systems. For the location of system
configuration information and information on the contents of the $SYSTEM.SYSnn
subvolume for G-series systems, see the Interactive Upgrade Guide, or for G06.19 and
earlier, the G-Series Highlights and Migration Planning Guide.
For K-series servers, SYSGENR uses the CONFTEXT file to define hardware and
build the processes that are specified in the configuration file into the operating system.
For NonStop S-series servers, SYSGENR uses the ALLPROCESSORS section of the
CONFTEXT file only and this ALLPROCESSORS section contains only a few entries.
All the other entries that would be in the ALLPROCESSORS section for K-series
servers are either configured using SCF or configured automatically for S-series
servers. In some cases, how an attribute is configured depends on which G-series
RVUs you are running.
When you use DSM/SCM, it automatically runs SYSGENR when you change anything
in the CONFTEXT file (however, CONFTEXT now contains so little information that the
need for modification is rare).
SCF is the S-series equivalent for most of the configuration that is done using
CONFTEXT for K-series servers. For example, many K-series communications
controllers (which were configured in CONFTEXT) are replaced by the S-series SWAN
concentrator or adapters. To configure the SWAN concentrator, use the SCF interface
to the WAN subsystem. Then, use the SCF interface for various different subsystems
depending on which communication subsystem you are configuring. For example, for
an Expand-over-FOX line, use the SCF interface to the Kernel subsystem, the SCF
interface to the ServerNet/FX adapter subsystem, and the SCF interface to the WAN
subsystem.
SCF does not build the processes that are specified in the configuration file into the
operating system. The configuration information is not located in the operating system,
but instead it is stored in the configuration database files (located in the
$SYSTEM.ZSYSCONF subvolume), which enables you to change the system
configuration online.
Changing the System Name, System Node Number, and Time Attributes