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

• The IP addresses used in this section are examples only. If you use the example files described
in this section on your system, you must change the IP addresses in these examples to IP
addresses that are appropriate for your LAN environment.
• The configuration track-ID for the SWAN concentrator used in the example files, X001XX, is
also an example.
If you use the example files described in this section on your system, you must change the
configuration track-ID used in these examples to the actual configuration track-ID assigned to
your SWAN concentrator.
CIIN File
The CIIN file is a TACL command (OBEY) file that contains a limited set of commands that usually:
• Start a TACL process pair on the system console for the system console TACL window
($YMIOP.#CLCI).
When the startup TACL executes the commands in the CIIN file and terminates, the
$YMIOP.#CLCI process pair lets you log on to the system and complete the system startup.
NOTE: Before these TACL processes start, open the appropriate terminal emulator windows
with the OSM Low-Level Link. You must open these windows before performing a system load.
OSM software lets you define primary and backup IP addresses for TACL windows. For more
information about configuring OSM software, see the OSM Low-Level Link online help.
• Load all processors that are not currently running.
Alternatively, the CIIN file can reload a minimal set of processors, such as processor 1, to
bring up a minimal system. You can then test for successful startup of a minimal system
environment before you bring up the remainder of the system.
Normally, the initial TACL process invokes the CIIN file automatically after the first processor is
loaded if all these conditions are true:
• The CONFTEXT configuration file located in the $SYSTEM.SYSnn subvolume has an
INITIAL_COMMAND_FILE entry for the CIIN file.
• The CIIN file is available in the specified location.
• The CIIN option is not disabled in the System Load dialog box.
NOTE: By default, the CIIN file contains commands needed to start the (permanent) TACL
process pair and to reload all the processors in the system. Do not place commands to prime
the processors in the CIIN file.
Establishing a CIIN File
The CIIN file is configured at the factory as $DSMSCM.SYS.CIIN. You do not need to establish
this file. DSM/SCM automatically copies the CIIN file from the initial location into each SYSnn
you create.
NOTE: The CIIN file must be owned by a member of the super-group (255,n). HP recommends
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.”
The name of the CIIN file is specified in the INITIAL_COMMAND_FILE entry of the CONFTEXT
configuration file.
A system generation program (run from the DSM/SCM application) copies the file specified in the
CONFTEXT file onto the SYSnn subvolume on the disk and renames the file CIIN. If no file is
specified in CONFTEXT, the operating system does not look for the startup file SYSnn.CIIN at
CIIN File 203