System Generation Manual for G-Series RVUs

Contents of the CONFTEXT File
System Generation Manual for G-Series RVUs—523407-001
2-7
INITIAL_COMMAND_FILE or
INITIAL_COMINT_INFILE (Required)
CIIN file) if both the CIIN file is specified in the CONFTEXT file and the CIIN disabled
option is not checked (CIIN is enabled) in the TSM client software. When all the
commands in the CIIN file have been executed, the startup TACL process terminates.
The CIIN file contains a limited set of commands that reload the remaining processors
and start a TACL process pair on the system console. You determine the contents, but
usually the CIIN file contains commands to:
•
Load all processors that are not currently running
Alternatively, the CIIN file can reload only a minimum set of processors (such as
processor 1) to bring up a minimal system. This action allows you to test for
successful startup of a minimal system environment before you bring up the
remainder of the system.
•
Start a TACL process pair on the system console for the system console TACL
window ($YMIOP.#CLCI)
When the startup TACL terminates after executing the commands in the CIIN file,
you need this TACL process pair to enable you to log on to the system and
complete the system startup process.
For more information on TSM features and configuring TSM client software, refer
to the TSM Configuration Guide and the TSM Online User Guide.
Establishing a CIIN File
The CIIN file is initially configured at the factory in the $SYSTEM.SYS01 subvolume.
There is nothing you need to do to establish this file. DSM/SCM automatically copies
the CIIN file from the initial location into each SYSnn you create.
To specify the name of the CIIN file in the CONFTEXT file, use the syntax for either the
INITIAL_COMMAND_FILE entry or INITIAL_COMINT_INFILE entry shown here.
Either entry is applicable for G-series RVUs.
Note. Before this TACL process pair is started, the appropriate terminal emulator window
(session) must be started in TSM. This session must be started before you perform a
system load. The CIIN file example on page 2-10 tells you how to use TSM to start this
session.
Note. The CIIN file must be owned by a member of the super-group (255,n). It is
recommended that you specify “N” for the read-access portion of the file security attribute
(RWEP) to allow the file to be read by any user on the network. For example, you might secure
this file “NCCC.”
[ INITIAL_COMMAND_FILE | INITIAL_COMINT_INFILE ]
[[ $volume.]subvolume.]filename;