System Generation Manual for G-Series RVUs

Contents of the CONFTEXT File
System Generation Manual for G-Series RVUs—523407-001
2-8
INITIAL_COMMAND_FILE or
INITIAL_COMINT_INFILE (Required)
SYSGENR copies the file specified in this entry to the new SYSnn subvolume on the
system disk and renames it CIIN. If you do not specify a CIIN file in the
INITIAL_COMMAND_FILE or INITIAL_COMINT_INFILE entry, the following occurs:
•
The operating system does not look for the startup file (SYSnn.CIIN) at system
startup; therefore, you cannot simply copy your startup file to the SYSnn
subvolume and name it CIIN.
•
The system load process creates a startup TACL (INIT TACL) on $YMIOP.#CLCI.
This TACL prompt is displayed in the TACL window on the primary system console
and is in the logged-off state. If the primary system console is not available at
system load, this TACL prompt is displayed on the backup system console.
Further system startup operations must be performed manually by logging on to
the system.
After the CIIN file is established on the new SYSnn subvolume, you can modify the
contents of SYSnn.CIIN using a text editor such as PS Text Edit (TEDIT). You need
not run DSM/SCM again to make these changes effective.
If a CIIN File Is Not Specified or Enabled in TSM
Table 2-2 describes the results of the startup TACL process based on whether a CIIN
file is specified in the CONFTEXT file and whether the CIIN disabled option is checked
Note. HP recommends that you not invoke other command files from the CIIN file. To ensure
proper system startup, the system should be brought up in stages, in order to facilitate
recovery should any step fail.