System Generation Manual for G-Series RVUs

Using Preprocessing Commands
System Generation Manual for G-Series RVUs—523407-001
3-6
Making SYSGENR Work Files Permanent
Keeping some work files permanent is useful if you wish to look at the work files for
debugging purposes after system generation. For example, you might wish to keep a
permanent copy of the work file SYSGENF (the CONFLIST file) as a file on disk.
Because SYSGENF is an EDIT file, you can view the permanent copy with a text editor
such as TEDIT.
DSM/SCM allows you to specify if work files are to be made permanent. See the
DSM/SCM User’s Guide for details.
The following SYSGENR work files are useful as permanent work files:
The syntax for creating a permanent work file is shown below.
SYSGEN-workfilename
is the name of a work file created by SYSGENR that you do not want purged at the
completion of SYSGENR. See Table 3-1 for the list of work files.
SYSGENT A list of all SYSTEM_LIBRARY_CODE_FILES to be sent to NLD, the
native mode linker, to build SYSCLR.
SYSGENU A list of all files to be sent to NLD, the native mode linker, to build the
DP2 process.
SYSGENW The OSCONFIG database, which is built by SYSGENR and contains
SPIFF and SWID records.
SYSLIB00 The TNS and accelerated portion of system library.
Work File Name File Content
SYSCLR TSYSCLR file
SYSDP2 TSYSDP2 file
SYSGENA OSIMAGE file
SYSGENF CONFLIST file
SYSGENK Resident template file
SYSGENL Nonresident template file
SYSCOD00 System code object file
SYSLIB00 System library object file
ASSIGN SYSGEN-workfilename,
[[[\system.]$volume.]subvolume.]filename
Table 3-1. SYSGENR Work Files (page 2 of 2)
Work File Name Contents