4.5. Error handling
The following sections defines how errors should be handled.
4.5.1. Unknown component
If the component (cId) is not known, then the site must answer with
CommandResponse/StatusResponse where q or age is set according to the
table below. v should be set to null.
Message type |
Content |
|---|---|
StatusResponse |
q=undefined |
CommandResponse |
age=undefined |
4.5.2. SXL mismatch
If there is a mismatch of the SXL when receiving a command, status or alarm request, which is not caught during communication handshake (See RSMP/SXL Version), then this is considered a serious error resulting in MessageNotAck.
This includes:
unknown alarm code id (
aCId)unknown status code id (
sCI)unknown command code id (
cCI)unknown name (
n) in arguments or return values
4.5.3. Unimplemented statuses or commands
If a status (sCI) or command (cCI) is unimplemented, the site answers
with CommandResponse/Response where q or age is set according to the
table below. v should be set to null.
Message type |
Content |
|---|---|
StatusResponse |
q=unknown |
CommandResponse |
age=unknown |
4.5.4. Incomplete commands
If not all arguments are included in a CommandRequest, then this is considered a serious error resulting in MessageNotAck.