System Generation Manual for G-Series RVUs
Running DSM/SCM and SYSGENR
System Generation Manual for G-Series RVUs—523407-001
4-2
What Happens When You Run DSM/SCM
DSM/SCM automatically runs SYSGENR when creating a new configuration. After you
are certain the CONFTEXT file is free of errors, you must run DSM/SCM to generate a
new operating system.
What Happens When You Run DSM/SCM
After using DSM/SCM to specify all needed PARAMs and ASSIGNs, you are ready to
run DSM/SCM, which automatically runs SYSGENR. To start DSM/SCM, perform the
following steps:
1. Be sure that ZDSMSCM is the current subvolume.
2. If a TM management process (TMP) is not running, run TMFSTART.
>RUN TMFSTART
3. Run STARTSCM.
>RUN STARTSCM
When SYSGENR is invoked by DSM/SCM, it returns this prompt:
SYSGEN - T9023 GUARDIAN 90 - T9023F40 - (29FEB96) 15 APR 1996 10:23
COPYRIGHT TANDEM COMPUTERS INCORPORATED 1980, 1983, 1987, 1991
TNS/R VERSION
SYSGENR then builds its work files, a task that lasts about 8-15 minutes, depending
on the size of the system and how busy the processor is. If you specify a spooler
location as the OUT listfile in your RUN SYSGENR command, SYSGENR sends
to the spooler a copy of the CONFLIST file. You can monitor the progress of
SYSGENR by using the Peruse JOB command to specify your SYSGENR job. Then
use the LIST LAST command to monitor progress.
If SYSGENR generates any errors, it terminates without producing a new system
image.
When SYSGENR has completed building its work files without any errors, it displays
the following message on the terminal:
SYSTEM IMAGE IS FOR A name SYSTEM
After filling all requests for system image disks (SIDs) and system image tapes (SITs),
SYSGENR saves the SYSGENF file as the $SYSTEM.SYSnn.CONFLIST file, closes
the spooled copy, and then terminates. At this time you can either print the spooled
copy or move it to an edit file.
Because the CONFLIST file can be hundreds of pages long, you might want to view it
online. If you decide to move the file copy from the spooler to an edit file on your
default subvolume, enter a Peruse command like the following:
Note. If you are using multiple logical targets on a system, always run DSM/SCM from the first
ZDSMSCM subvolume installed on the target system (the subvolume from which INITENV was
run) to ensure that the correct installation files are used. You can also run STOPSCM from the
same ZDSMSCM subvolume if DSM/SCM has finished processing all of its tasks.