DL_TEST_RES (dl_test_res_t) - conveys the TEST response DLSDU from the DLS User to the DLS Provider in response to a DL_TEST_IND.
The message consists of one M_PROTO message block, followed by zero or more M_DATA blocks containing zero or more bytes of data. The message structure is as follows:
typedef struct { t_uscalar_t dl_primitive; t_uscalar_t dl_flag; t_uscalar_t dl_dest_addr_length; t_uscalar_t dl_dest_addr_offset; } dl_test_res_t;
- dl_primitive
conveys DL_TEST_RES
- dl_flag
indicates the flag values for the response as follows:
- DL_POLL_FINAL
indicates if the poll/final bit is set.
- dl_dest_addr_length
conveys the length of the DLSAP address of the destination DLS User. If the destination user is implemented using DLPI, this address is the full DLSAP address returned on the DL_BIND_ACK.
- dl_dest_addr_offset
conveys the offset from the beginning of the M_PROTO message block where the destination DLSAP address begins.
The message is valid in states DL_IDLE and DL_DATAXFER.
The resulting state is unchanged.
On an invalid TEST response request, a DL_ERROR_ACK is issued to the usr.
- DL_BADADDR
The DLSAP address information was invalid or was in an incorrect format.
- DL_BADDATA
The amount of data exceeded the DLS provider's limit for TEST messages.
- DL_SYSERR
A System error has occurred and the UNIX System error is indicated in the DL_ERR OR_ACK.
- DL_NOTSUPPORTED
Primitive is known but not supported by the DLS Provider
- DL_OUTSTATE
The primitive was issued from an invalid state
- DL_TESTAUTO
Previous bind request specified automatic handling of TEST responses.
- DL_UNSUPPORTED
Requested service not supplied by provider.
Contents | Next section | Index |