Specifications

SPECIAL MESSAGES
The control units for the 1744, 1745, and 1747 equipments
produce the following
error messages. Error messages are
on the comment device unless otherwise specified.
1744/274 Digigraphic Controller Errors
Message
BDC NOT READY
BDC BUSY
Significance
Buffered data channel not ready
DGC NOT READY
Buffered data channel busy
Digigraphic console not ready
DGC EXT REJ
Digigraphic
external reject
EGC INT REJ
Digigraphic internal
reject
1745/210 Local Terminal Controller Errors
Local terminal controller error messages have the following
format:
CRT
yx
Where: y is the station number of the unit on which the
error occurs.
x is the
error code.
Error codes for the local terminal controller are as follows:
Error Code
o
2
3
4
5
6
7
8
9
96769450 A
Significance
Diagnostic
timeout
Reject in initiator
Reject doing function output
Reject attempting buffered input/output
Reject on write terminate function
Reject in interrupt response (station
interrupt)
Reject in interrupt response (end-of-
operation interrupt)
Reject in send portion of continuator
Reject after end-of-operation in continu-
ator
Allocatable core is not sufficient for this
format read size
Error Code
A
B
Significance
Zero length request; not completed with
error and not executed
Software cannot identify interrupt
(treated as ghost).
The comment device
error messages are:
Message
GI1706
GICRT
Significance
Ghost (unexpected) interrupt on 1706 con-
nected to the local terminal controller
Ghost
interrupt from local terminal con-
troller
1747 Data Set Controller Errors
Message
Significance
Data set controller reject DSC REJECT
BDC NOT READY Buffered data channel not ready
BDC BUSY
Buffered data channel busy
DSC NOT READY Data set controller not ready
Data set controller busy
DSC BUSY
TEST MODE
NO CARRIER
Data set controller in test mode
No carrier signal on the data set
EQU IPMENT STATUS CODES
The following status codes appear in one or more of the
following locations:
• System initializer error message
• Engineering log printout
• PHYSTB for the device (ESTAT2 = word 12)
In this manual, only one status is given; it is the one found in
the engineering log for that device (see Engineering Log in
section 4, for the method of finding the status word). This
status may be a composite status word developed by the
device driver. In some cases (e.g., the 1833-1 Disk),
numerous
status words can be obtained from the device by
use of a WES code requesting status with a director bit set
to the code for the status word desired. See the devices'
hardware maintenance manuals for information
on these
status words, some of which may also be saved in other
words of PHYSTB.
6-7