System Generation Manual for G-Series RVUs

SYSGENR Overview
System Generation Manual for G-Series RVUs—523407-001
1-3
Changing the System Configuration Offline With
DSM/SCM
Changing the System Configuration Offline With DSM/SCM
Most system configuration changes are now performed online using the Subsystem
Control Facility (SCF). Refer to the SCF Reference Manual for G-Series RVUs or the
product-specific configuration or SCF manual.
For G-series RVUs, changes to the CONFTEXT file require you to change the system
configuration offline. To bring CONFTEXT file changes into effect, a system load is
needed.
To change the CONFTEXT file, perform the following steps:
1. Modify the CONFTEXT file as described in Section 2, Contents of the CONFTEXT
File.
2. Run DSM/SCM and follow all required instructions. Refer to the DSM/SCM User’s
Guide for more information.
How SYSGENR Works
The following subsections describe how SYSGENR works:
Programs Invoked by SYSGENR
Depending on the software installation choices you specify, SYSGENR uses several
other programs:
•
BACKUP – Copies the new operating system files to a system image tape (SIT).
This SIT is “bootable”; that is, it can be used to load the system.
•
BIND – Creates TNS (file code 100) system code and system library files.
•
DISKGEN – Copies the new operating system files to a system image disk (SID).
•
NLD (native link editor) – Builds the SYSCLR and SYSDP2 files.
•
SWID (software ID) – Audits file identification information about your software.
•
TEMPLI – Merges template object files to build resident and nonresident Event
Management Service (EMS) template files.
Topic Page
Programs Invoked by SYSGENR
1-3
Input Files for SYSGENR 1-4
Optional Preprocessing Commands for SYSGENR 1-6
Output From SYSGENR 1-6
Note. If you run BACKUP outside SYSGENR or DSM/SCM to create a tape of the same
operating system files, you cannot load the system from this tape. Because only
SYSGENR places boot code on a SIT, only SYSGENR can produce a bootable SIT.