AM3270 and TR3271 Configuration and Management Manual

AM3270 and TR3271 Configuration and Management Manual—529993-001
D-1
D Error Messages for AM3270
This appendix describes network-related operator console error messages and
common file-system error messages. Cause and recovery information for each error
message is included.
This appendix includes messages issued only by the AM3270 subsystem. The user
can receive, through SCF, error messages generated by the file system, SCP, and so
on. File-system, SCP, and other errors originating outside the SCF environment are
described in the documentation supporting the particular source of the error, and are
not described in the SCF Reference Manual for AM3270 and TR3271. Table D-1 lists a
few errors and directs you to manuals that contain more information about them.
You can also get information about error messages by using the SCF HELP command
(for example, by typing HELP AM3270 nnnnn).
Table D-2 includes some file-system error summaries for the AM3270 subsystem.
Table D-1. Error Messages
Number Generated By Manual
-nnnnn SCP SCF Reference Manual for G-Series RVUs
nnnnn AM3270 and TR3271 SCF Reference Manual for AM3270 and TR3271
20nnn SCF SCF Reference Manual for G-Series RVUs
Table D-2. File-System Error Summary for AM3270 (page 1 of 2)
Error Number Description
0 No error. The operation completed successfully.
87 Waiting on a READ request and received an I/O request that was not a
READ.
88 A two-step READ is queued; therefore, another two-step READ is invalid.
100 Subdevice offline.
123 Subdevice busy.
124
*
A line reset has been performed.
140 Modem error.
160 Protocol error.
161 Impossible event occurred for line state.
162 Operation timed out after n retries.
171 No response to attempted operation.
172 Reply not proper for protocol.
173 Maximum NAKS sent.
* After a line ownership change has occurred, there is a period of time during which an application can receive
this error. Note that the application should retry its request when this error is received.