CP6100 I/O Process Programming Manual
 Using CP6100: Managing Lines
 SOFTWARE INSTALLATION AND LINE CONFIGURATION
 Before any application can use a CP6100 line, you have to install
 the system software and describe the line to the system. This
 procedure entails the following steps, taken in sequence:
 1. Prepare a SYSGEN configuration file to describe the 6100
 subsystems, the supporting software (like CSM), and the
 CP6100 lines.
 2. Use SYSGEN to create a new system image from the files
 on the Site Update Tape (SUT), and to load that image
 into the NonStop System.
 3. Use the FUP GIVE and SECURE commands and the CMI ALTER
 command to define the group of users who can control
 CP6100 lines--for example, who can start and stop lines
 or change their configuration.
 Once you've taken these steps, you can start the lines for
 applications to use.
 | Other manuals discuss each of the above steps in detail. The
 | System Management Manual for Tandem NonStop Systems discusses
 | steps 1 and 2, the GUARDIAN Operating System Utilities Reference
 | Manual describes the FUP commands, and the Communications
 | Management Interface (CMI) Operator's Guide discusses CMP
 | security, i.e., the way you restrict control of data
 communication lines. The next few pages give an overview of the
 installation and configuration process, with a few guidelines and
 warnings to help you along.
 The Configuration File
 | DUAL-PORT CONTROLLERS. To add a communication subsystem having
 | dual-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 each controller will be attached,
 and assign a subchannel address to each controller. Both
 controllers in a subsystem must be attached to the same pair
 of CPUs; they can have the same primary CPU, or each can
 have a different primary. (You list the CPUs in order:
 primary, secondary.) The subchannel address for each
 controller must be divisible by 32 (%40); the controller
 occupies 32 addresses, beginning with the one specified.
 October 1985
 3-2










