NonStop Operations Guide for H-Series and J-Series RVUs

system startup, even if you enable that file. You cannot simply copy a startup file to the SYSnn
subvolume and name it CIIN.
Modifying a CIIN File
After the CIIN file is established on $SYSTEM.SYSnn (as part of running DSM/SCM), you can
modify the contents of SYSnn.CIIN with a text editor such as TEDIT. You need not run DSM/SCM
again to make these changes effective.
If a CIIN File Is Not Specified or Enabled in OSM
The results of the startup TACL process varies depending on whether a CIIN file is specified in the
CONFTEXT file and whether the CIIN option is enabled.
ResultsCIIN OptionCONFTEXT CIIN Entry and CIIN File
CIIN is executed by initial (startup)
TACL process. Upon completion, this
EnabledCONFTEXT has CIIN entry, and file is
available in specified location.
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.
CIIN is executed by initial (startup)
TACL process. Upon completion, this
EnabledCONFTEXT has CIIN entry, and file is
available in specified location, but file
TACL process terminates, leaving nois empty or aborts because of syntax
TACL process available. You musterrors before another TACL process is
started. reload the system with the CIIN option
disabled in the System Startup dialog
box invoked from the OSM Low-Level
Link; then log on and correct the CIIN
file. Then, either enable the CIIN
option, using the System Startup dialog
box, and reload; or complete the
system startup process manually.
Initial TACL process is started and left
in logged-off state. You must log on to
complete the system startup process.
EnabledCONFTEXT has CIIN entry, but file is
not available in specified location.
Initial TACL process is started and left
in logged-off state. You must log on to
complete the system startup process.
DisabledCONFTEXT has CIIN entry.
Initial TACL process is started and left
logged on to the super ID (255,255).
Enabled or disabledCONFTEXT has no CIIN entry.
You must initiate the remainder of the
system startup process manually and
then log off.
NOTE: Situation 5 presents 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 described
in the Results column), log on to another user ID, or log off.
Example CIIN Files
This example CIIN file does not include a persistent CLCI TACL process.
Comment -- This is the initial command input (CIIN) file for the system.
Comment -- If CIIN is enabled in OSM and configured in your CONFTEXT
Comment -- file, the initial TACL process will read this file and
Comment -- then terminate.
204 Creating Startup and Shutdown Files