6100 BSC Programming Manual

Writing Applications that Use 6100 BSC
When the request completes, the buffer has the same structure
as before, but some of the fields have different meanings:
Response. This byte contains the same number that denoted
the function in the request. For example, the
number 1 occurs in the response to SET
CONFIGURATION.
Status. This byte contains a code representing normal
completion or an error. For example, the number 0
indicates a normal completion; the number 140
indicates a modem error.
Request ID. This word contains the same number as in the
corresponding request. Thus you can tell which
request completed.
Status Detail. This word contains more information about the
completion status of the request. For example,
if the status field contains a 22 (invalid
parameter), the code in Status Detail tells
you which parameter was invalid.
Text In. This word contains the length, in bytes, of the
text field in this response. The value should
match or be less than the number in the request.
Text. This string contains additional data. For
example, in the response to a FETCH CONFIGURATION
request, this field contains the current values of
the line configuration parameters.
If the response buffer exceeds the read count specified in the
WRITEREAD call, the buffer is truncated for delivery to the
application. The condition code is zero, but the value of the
Text In field exceeds the count read value returned by GUARDIAN.
An application can compare these values to find out whether
input has been lost. To avoid receiving truncated responses,
use a value of read count that equals or exceeds the value of
Text In (in the request) plus 8.
3-25