CP6100 I/O Process Programming Manual

Using CP6100: Programming
example BSC, provide two levels of status in the buffer:
the status field gives a general description of the error
that occurred, and the detail field gives more information
pertaining to the error.
For specific descriptions of the status codes returned by each
protocol, consult the books that describe the protocols.
Notice that when a WRITEREAD call completes with a condition code
of zero, that doesn't mean the application request completed
without error. It means the request successfully reached the
protocol task, which may or may not have succeeded in its
execution. To find out whether the desired action was taken by
the protocol, you have to look at the second byte in the
WRITEREAD buffer (see Figure 2-2); a value of zero in that
position tells you everything worked.
-----------------------------------------------------------------
| |
| RETRY THESE, BUT FIRST REVIEW APPENDIX A |
| ------------------------------------------------------------ |
| 31 No buffer space for DEBUG subdevice. |
| ------------------------------------------------------------ |
| 33 No buffer space for requested count. |
| ------------------------------------------------------------ |
| 124 Non-responding LIU. Trying to reset. |
| ------------------------------------------------------------ |
| 200 Device owned by other CPU. |
| ------------------------------------------------------------ |
| 210 Path switch occurred. |
| ------------------------------------------------------------ |
| 211 CPU failure. |
| ------------------------------------------------------------ |
| 230 CPU power on. |
| ------------------------------------------------------------ |
| 231 Controller power on, channel reset, or loss |
| of contact with subsystem cabinet. |
| |
-----------------------------------------------------------------
Figure 2-4. File System Errors (Page 1 of 2)
October 1985
2-14