6100 BSC Programming Manual

Writing Applications that Use 6100 BSC
STATUS CODES AND DETAILS
Two fields of the response buffer contain status information.
The status field contains a general message, while the detail
field contains further explanation of the status code. For
example, if the status code is 22 (invalid parameter), the detail
code might be 128 (invalid function field). Thus the application
can check the code in the status field and then, if necessary,
check the detail field for more information.
In some cases, there can be a zero in the status field and yet a
non-zero value in the detail field. For example, if you issue an
ABORT and there is no request outstanding, the status field will
contain a 0, but the detail field will contain a 4 (no request
active).
NOTE
The status codes are the same as the file system errors
returned by ENVOY.
The next few pages describe first the status codes, and then
the detail codes.
Status Codes
Value (Decimal) Description
0 The request completed as expected.
22 A field in the request buffer had an illegal
value. The detail field identifies the
invalid parameter.
122 The request was aborted. This or some other
process made an ABORT request.
140 A modem error occurred. The detail field
identifies the error.
160 The request was invalid for the line state.
For example, a SET CONFIGURATION request is
allowed only in DISCONNECTED state. The
detail field identifies the state.
If the request was HALT READ, BSC was
processing a STOP request.
3-59