System Generation Manual for G-Series RVUs

Contents of the CONFTEXT File

System Generation Manual for G-Series RVUs—523407-001

2-5

FILES_TO_COPY_TO_NEW_SYSTEM (Required)

You use this entry to specify RVU-dependent or system-dependent object files, data

files, configuration files, and optional-product millicode files to be included in the new

operating system. When creating the system image disk or tape, SYSGENR copies

the files to the $SYSTEM.SYSnn subvolume specified by the

SYSTEM_VOLUME_SUBVOL entry, keeping their security settings.

The list of files is subject to change with each software RVU and is added to the

CONFAUX file by DSM/SCM. If you use the CONFAUX file (the normal procedure),

you need enter only the installation descriptor TANDEM^FILES^TO^COPY. The form

of this entry is shown here.

If you wish to list additional files to be copied that are not listed in the CONFAUX file,

perform the following steps:

1. Replace the semicolon (;) ending the entry with a comma (,).

2. List the additional files. For multiple files, enter a comma (,) after each file name.

3. Enter a semicolon (;) after the last file name listed to terminate the

FILES_TO_COPY_TO_NEW_SYSTEM entry.

Object files that are not RVU-dependent should be placed on $SYSTEM.SYSTEM in

order to save disk space, because having multiple versions on each SYSnn

subvolume results in multiple copies of those files.

The following example shows a FILES_TO_COPY_TO_NEW_SYSTEM entry with an

additional file, the user file DMON, added:

If you do not use the CONFAUX file, the following guidelines apply:

•

You must identify each file to be copied to the new operating system.

•

To place a file in a subvolume other than $SYSTEM.SYSnn, perhaps under a

different file name, use the RENAME_TO option shown for two files in the example

later in this subsection.

•

The USERID file, which contains names and user IDs, and the USERIDAK file,

which is an alternate-key file for USERID, are the only files that need to be placed

in $SYSTEM.SYSTEM during system generation. Other RVU-independent files

that must later reside there, such as the TEDIT and TGAL files, are not involved in

the system-generation process. DSM/SCM assembles these files on

$SYSTEM.SYSTEM along with the TACLSEGF segment file during the Apply

process. TACLSEGF contains directories for products that have TACL code.

FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY;

FILES_TO_COPY_TO_NEW_SYSTEM TANDEM^FILES^TO^COPY,

$S11B.ZINSPECT.DMON;