CP6100 I/O Process Programming Manual

Using CP6100: Managing Lines
The typical command context for ALTER LINE <ldev>, PROGRAM is:
1. Use STOP to stop the line.
2. Use ALTER LINE <ldev>, PROGRAM to change the program to be
downloaded.
3. Use START to start the line again.
The ALTER LINE <ldev>, PROGRAM command requires that the line be
stopped.
Remember that a change in the protocol affects all users of the
line. Changing the protocol to benefit one application can
make it impossible for other applications to use the line.
ALTER LINE <ldev>, CONFIG (<offset> [,<data>] ...)
This command lets you set or change the values of line
configuration parameters. You can change almost any parameter
SYSGEN lets you define. (The Communications Management Interface |
(CMI) Operator's Guide lists the options for each protocol; the |
System Management Manual for Tandem NonStop Systems lists and |
describes each one.) |
Current values of all parameters are stored in a block in the
LIU. The protocol uses those values in its operation. If a line
has AUTOCONF specified in its SYSGEN definition, CP6100 keeps a
template for the configuration block and sends that template to
the LIU immediately after every download, as well as on the
first new OPEN after every opener has closed the line. The
ALTER LINE <ldev>, CONFIG command changes the values in the
template block.
The command is legal only if the line is stopped and has AUTOCONF
in its SYSGEN definition; then configuration changes take effect
on the next download, as shown in Figure 3-2. If a line is
started or does not have AUTOCONF specified in its SYSGEN
definition, ALTER LINE <ldev>, CONFIG may not be used.
These facts have important implications for the use of ALTER
LINE <ldev>, CONFIG:
• In the ALTER command, you supply a list of values, along with
an offset into the configuration block. There are no symbolic
names for the parameters; the offset determines where new
values are inserted. Be careful to specify correct offsets,
October 1985
3-13