System Generation Manual for G-Series RVUs

Contents of the CONFTEXT File
System Generation Manual for G-Series RVUs—523407-001
2-9
INITIAL_COMMAND_FILE or
INITIAL_COMINT_INFILE (Required)
in the TSM client software (the System Startup dialog box of the TSM Low-Level Link
Application).
Table 2-2. Results of Startup TACL Process
CONFTEXT CIIN Entry
and CIIN File CIIN Option Results
1. CONFTEXT file has
CIIN entry and file is
available in specified
location.
Enabled CIIN is executed by initial (startup) TACL
process. Upon completion, this TACL
process terminates. You must log on to a
different TACL process (the TACL process
on $YMIOP.#CLCI started by the CIIN file)
to complete the system startup process.
2. CONFTEXT file has
CIIN entry and the file
is available in the
specified location, but
the file is empty or
has syntax errors
before another TACL
process is started.
Enabled CIIN is executed by initial (startup) TACL
process. Upon completion, this TACL
process terminates, leaving no TACL
process available. You must reload the
system with the CIIN disabled option
checked in the System Startup dialog box,
then log on and correct the CIIN file. Then,
either uncheck the CIIN disabled option and
reload or complete the system startup
process manually.
3. CONFTEXT file has
CIIN entry but the file
is not available in
specified location.
Enabled Initial TACL process is started and left in
logged-off state. You must log on to
complete the system startup process.
4. CONFTEXT file has
CIIN entry.
Disabled Initial TACL process is started and left in
logged-off state. You must log on to
complete the system startup process.
5. CONFTEXT file has
no CIIN entry.
Enabled Initial TACL process is started and left
logged on to the super ID (255,255). You
must initiate the remainder of the system
startup process manually and then log off.
6. CONFTEXT file has
no CIIN entry.
Disabled Initial TACL process is started and left
logged on to the super ID (255,255). You
must initiate the remainder of the system
startup process manually and then log off.
Caution. Items 5 and 6 in Table 2-2
present a security issue: the initial TACL process is left
logged on to the super ID (255,255). You must either immediately continue with the system
startup process (as stated in the Results column), log on to another user ID, or log off.