System Generation Manual for G-Series RVUs

System Generation Manual for G-Series RVUs—523407-001
D-1
D
Comparing SYSGENR for D-Series
RVUs With SYSGENR for G-Series
RVUs
Many changes have been made to the role of SYSGENR in G-series RVUs. This
appendix focuses on two affected SYSGENR areas: system configuration utilities and
the ALLPROCESSORS paragraph.
Changes to the System Configuration Utilities
For D-series RVUs, SYSGENR builds the I/O processes (IOPs) specified in the
CONFTEXT file into the OSIMAGE file, as it has always done.
For G-series RVUs, IOPs are not built by SYSGENR. Instead, they are built by SCF.
SYSGENR does build into the OSIMAGE file a few system-load entities that are
available at system startup, but it leaves the remaining IOPs for SCF and the
subsystem manager processes to configure and manage. This change is explained
more fully in the SCF Reference Manual for G-Series RVUs.
Figure D-1 compares the entities involved in system generation of D-series and
G-series operating systems.
For each RVU series, the figure shows key input to and output from SYSGENR.
The following system generation principles are associated with D-series RVUs:
•
SYSGENR configures most of the components of the operating system, and it
uses as input a CONFTEXT file that contains paragraphs for each system
component.
•
The Configuration Utility Program (COUP) is used for online configuration of
system components. COUP configuration records are stored in the OSCONFIG
file.
•
SYSGENR and COUP create the IOPs, which are stored in the OSIMAGE file.
The following system generation principles are associated with G-series RVUs:
•
SYSGENR configures only a few system components from the
ALLPROCESSORS paragraph of the CONFTEXT file.
•
SCF is the utility used for online configuration of system components. SCF
configuration records are stored in the CONFIG file.
•
SCF creates the IOPs, which are stored in the OSIMAGE file.
•
COUP is not supported. The OSCONFIG file still exists, but it does not contain
configuration records.