CP6100 I/O Process Programming Manual
 Using CP6100: Managing Lines
 for LOAD, BOOT --> RUN
 for RESET, RUN --> BOOT
 The CONTROL command is legal only if the line is in the STOP
 state. That state may result from an earlier STOP command, from
 an error that caused CP6100 to stop the line, or from a cold-load
 of the system if the STARTDOWN parameter was specified in SYSGEN.
 EXAMINING AND CHANGING THE CONFIGURATION
 CMI provides facilities for changing the configuration of a line.
 There are three kinds of changes you can make to affect how a
 line operates:
 • You can change the program that will be downloaded to the line
 the next time the line is started. For example, you can
 cause a line running BSC to run ADCCP instead.
 • You can change line parameters like the baud rate, the frame
 size, or the offset for ASCII/EBCDIC translation. In fact,
 you can alter almost any parameter SYSGEN lets you define.
 • You can change the range of protocols that a line can run.
 For example, you can restrict a line to run only byte
 synchronous protocols, or to run only bit synchronous
 protocols, or both. (The hardware is capable of running
 any protocol, but you can impose a restriction.)
 The next few paragraphs describe the commands you use to make
 these changes. For syntax and further reference about the
 | commands, consult the Communications Management Interface (CMI)
 | Operator's Guide.
 ALTER LINE <ldev>, PROGRAM
 This command lets you specify the file that will be downloaded to
 the LIU. Typical uses for this command are error recovery
 situations; if you get error messages that suggest an LIU
 malfunction--a number of such messages are discussed in Appendix
 A--you might want to try downloading first the same file you last
 downloaded, then a copy of that file if you suspect that the file
 itself might be bad. Another use for this command is to let one
 line handle different protocols at different times; the
 implication is that various devices can be patched into available
 ports, and that the configuration of those ports changes to
 accommodate device protocols. Finally, you can use the command
 to install a new release of a protocol module or to correct an
 error in the SYSGEN configuration file.
 October 1985
 3-12










