Error Messages

        <ERR> <Code> <Command in error>

It is desirable to include debugging aids in the initial protocol for checking out Network Control Programs, etc.

There are three classes of errors--content errors, status errors, and resource allocation or exhaustion. <Code> specifies the class and the offending member of the class. The command is returned to the sending NCP for identification and analysis.

Examples of status errors are: messages sent over blocked links and attempts to unblock an unblocked link. Examples of content errors are: an invalid RFC complete; a message sent on a link not connected; closing of an unconnected link; and an attempt to unblock an unconnected link. Examples of resource errors are: a request for a non-existent program and connection table overflow, etc. Resource errors should be followed by a <CLS> in response to the <RFC>.