System Generation Manual for G-Series RVUs

Using Preprocessing Commands
System Generation Manual for G-Series RVUs—523407-001
3-4
Making SYSGENR Work Files Permanent
Examples
•
The following example specifies that SYSGENR use a remote version of BACKUP:
ASSIGN SYSGEN^BACKUP, \EAST.$SYSTEM.ZUTIL.BACKUP
•
The following example specifies that, for a migration from D40 to G00, SYSGENR
run G00 BIND from the PDTSYS subvolume on the volume where installation tools
are located, instead of the D40 BIND at the default location at
$SYSTEM.SYSTEM:
ASSIGN SYSGEN^BINDER, $S11B.PDTSYS.BIND
•
The following example specifies that SYSGENR run a remote copy of DISKGEN.
If you do not supply this ASSIGN, SYSGENR looks for DISKGEN on the local
system on $SYSTEM.SYSTEM:
ASSIGN SYSGEN^DISKGEN, \EAST.$SYSTEM.SYS03.DISKGEN
•
The following example specifies that SYSGENR run NLD from the PDTSYS
subvolume on the volume where the latest installation tools are located, instead of
at $SYSTEM.SYSTEM:
ASSIGN SYSGEN^LINKER, $S11B.PDTSYS.NLD
•
The following example specifies that SYSGENR use the software identification tool
at another location than $SYSTEM.SYSTEM:
ASSIGN SYSGEN^SWID, $SYSTEM.SYS55.SWID
•
The following example specifies that SYSGENR run a remote copy of TEMPLI. If
you do not supply this ASSIGN, SYSGENR looks for TEMPLI on the local system
on $SYSTEM.SYSTEM:
ASSIGN SYSGEN^TEMPLI, \EAST.$OTHER.SYSGEN.TEMPLI
•
The following example specifies that SYSGENR run XLLINK from a location other
than $SYSTEM.SYSTEM:
ASSIGN SYSGEN^XLLINK, $SYSTEM.NATIVE.XLLINK
Making SYSGENR Work Files Permanent
SYSGENR creates temporary work files that are used as storage areas while it runs.
SYSGENR normally purges these work files when it terminates. However, you can
save one or more of these work files (except for the SYSGENH and SYSGENP work
files, which cannot be saved) after SYSGENR finishes by using an ASSIGN command
before you run SYSGENR.
If you wish to save all the SYSGENR work files, use the PARAM WORKFILE
command described later in this section.