1.4.2: Solicited Response Overview
When replies are made an initial response and final response are issued. It is unwise for the host to issue
further commands until the final response has been received. Section 1.3: Identifier Considerations,
describes the action of identifiers on these replies and specifies rules which may also suppress the replies.
1.4.2.1: Initial Response
This will be given on receipt of a valid command and for a positive acknowledge will be of the form:
(Source_ID)(Group_ID)(Destination_ID)!
In this way, the host quickly knows that the destination has received and understood the command.
1.4.2.1.1: Initial Response Failure
This will be given on receipt of an invalid command and will be of the form:
(Source_ID)(Group_ID)(Destination_ID)!$FAIL sc fn$
Where „sc‟ is a status code (see section 1.8.1.1: Status Codes) specifying why the task could not be
completed, and „fn‟ specifies which field was responsible.
Note: There is no final response.
1.4.2.2: Final Response
This will be given on completion of the task and will be of the form:
(Source_ID)(Group_ID)(Destination_ID)!$Status_String$
The status string will be a unique response to the originating command.
1.4.2.2.1: Final Response Failure
This will be given where a task could not be completed and will be of the form:
(Source_ID)(Group_ID)(Destination_ID)!$FAIL sc fn$
Where „sc‟ is a status code (see section 1.8.1.1: Status Codes) specifying why the task could not be
completed, and „fn‟ specifies which field was responsible.
Note:
1
In all cases, identifiers will only be returned as part of the response if supplied as part of the command (refer
to section 1.3: Identifier Considerations for further details).
2
Fields are numbered from left to right, starting at 1.
To Next Page
Loading...
Need help?
General
