CP6100 I/O Process Programming Manual

Using CP6100: Managing Lines
There are two important points you should consider when |
configuring single-port controllers: |
|
• The single-port controller environment is configured to look |
to SYSGEN as if only one controller were installed--there is |
no alternate path. Therefore, you cannot configure various |
I/O processes on different paths in the configuration file. |
|
• Whenever you use CMI to alter an I/O process to use the other |
path, a CPU switch always results. |
Security Considerations
To prevent unauthorized users from controlling CP6100 lines--
starting, stopping, suspending or activating them, downloading
them or changing their configuration--the system manager uses
the following commands in sequence:
1. Use the FUP GIVE command to give the CMP object file to a
specific user. The name of the CMP object file is normally
$SYSTEM.SYSnn.CMP. If you use another name for the system
disk, use that name in the GIVE command.
2. Use the FUP SECURE command with the PROGID option, so when
CMP runs, its accessor ID is that of the person who owns the
file, i.e., the person specified in the GIVE command.
For background information on accessor ID, see the GUARDIAN |
Operating System Utilities Reference Manual. |
3. After starting each CMP, use the CMI ALTER CMP command to
decide who can execute privileged commands. The full command
is of the form:
ALTER CMP <name> SECURITY "attribute"
where <name> is the name of one instance of CMP, and the
attribute is a single character from the following list:
O Only the owner, and only from this system
G Anyone in the owner's user group, on this system
A Anyone on this system
U Only the owner, from anywhere in the network
C Anyone in the owner's user group, anywhere in the network
N Anyone, anywhere in the network
The effect of the security attribute is to determine which
users, other than the owner, can execute privileged CMI
commands. The "owner," in this context, is either 1) the user
whose userid matches the accessor ID of CMP, or 2) the user
identified with the OWNERID in a previous CMI command
(see the Communications Management Interface (CMI) Operator's |
October 1985
3-9