CP6100 I/O Process Programming Manual

Using CP6100: Managing Lines
• Define the paths in the PATHS paragraph. Each entry
represents a pair of controllers and identifies two paths,
one through each controller, to the lines in the subsystem.
A line attached to the subsystem can have either path as its
primary; its primary CPU will be the one assigned to the
appropriate controller in the CONTROLLERS paragraph. (Thus,
if the primary path to $BSC is through controller CIU1, and
the CONTROLLERS entry for CIU1 makes CPU 5 its primary, the
I/O process that controls $BSC will run in CPU 5.)
Later, you'll notice that CMI calls the two paths A and B.
The name in the first column of a PATHS entry identifies path
A; the name after the keyword ALTERNATE_PATH identifies
path B.
• Define the microcode files in the MICROCODE_FILES paragraph.
There is an INSTALL DEFINE (TANDEM^MICROCODE^FILES) that
enumerates the files supplied by Tandem.
• Define the lines and the CSM process pair in the PERIPHERALS
paragraph. Associate each line with a path and an LIU number.
The name of the path tells which controller is primary for the
LIU. Define one CSM process pair for the 6100 subsystem;
associate it with path A and LIU 0. For each line, indicate
which I/O process will control the line. For each line and
the CSM, supply configuration parameters.
Figure 3-1a shows some excerpts from a configuration file for the |
dual-port controllers environment. |
October 1985
3-3