CP6100 I/O Process Programming Manual

Using CP6100: Managing Lines
SINGLE-PORT CONTROLLERS. A communication subsystem having |
single-port controllers is configured as if only one controller |
existed for the subsystem. |
|
To add a communication subsystem having single-port controllers |
to a NonStop System and define the CP6100 lines attached to the |
subsystem, you make the following additions to the configuration |
file: |
|
• Define the 6101 controllers in the CONTROLLERS paragraph. |
Indicate the CPUs to which the controllers will be attached, |
and assign a subchannel address to the controllers. |
|
• Define the path in the PATHS paragraph. (Note that the |
concept of "alternate path" does not apply to the single-port |
controller configuration during system generation.) Although |
it appears there is only one controller, each entry represents |
a pair of controllers and identifies two paths to the lines in |
the subsystem, one path through each controller associated |
with a separate CPU. |
|
Later, you'll notice that CMI calls the two paths A and B. |
Path A is considered the primary path and is always assumed to |
be associated with the lower-numbered CPU of the pair of CPUs |
defined in the CONTROLLERS paragraph. Path B is associated |
with the higher-numbered CPU. |
|
• 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 the path defined in the |
PATHS paragraph. |
|
Figure 3-1b shows some excerpts from a configuration file for the |
single-port controllers environment. |
October 1985
3-5