Messages relating to the transport layer
| Name | Severity | ID | Description | Action |
|---|---|---|---|---|
| AddressUnknown | fatal | 103 | The transport address presented is unknown. | |
| BadITOTlength | fatal | 402 | The packet length in the ITOT packet header is incorrect. The connection is broken. | |
| BadITOTversion | fatal | 400 | The version number at the start of an ITOT TPKT was incorrect. The connection is broken. | |
| BadMaxTPDUsize | fatal | 302 | The requested maximum TPDU size was invalid. | |
| BadOperation | warning | 53 | A transport layer parameter was incorrect. | |
| BadParameter | error | 52 | A transport layer parameter was incorrect. | |
| BadProvider | fatal | 314 | There is some problem with the capabilities of the transport provider. | |
| Congestion | error | 101 | Lack of resources or some other transient problem caused a transport layer disconnection. | |
| Duplicate | error | 231 | An attempt to reuse the source reference for the same NSAPs was detected. | |
| Error | error | 12 | OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event. | See log entry for details |
| ErrorS | error | 28 | OSI Transport Layer Error. Isode's medium term plan is to remove all common use of this event, Isode's long term plan is to remove all use of this event. | See log entry for details |
| Fatal | fatal | 13 | OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event | See Log entry for details. Please send information on the occurrence of this event to support@isode.com |
| FatalS | fatal | 29 | OSI Transport Layer Fatal Event. This event should only occur in very unusual situations. Isode's medium term plan is to remove all use of this event. | See Log entry for details. Please send information on the occurrence of this event to support@isode.com |
| Interrupt | info | 31 | An operation was interrupted | |
| InvalidLength | error | 238 | A length field in the transport PDU was found to be invalid. | |
| ListenFailure | fatal | 352 | There was a failure listening on the given address. The associated error gives more details. | |
| Mismatch | error | 232 | There was a problem with transport connection references. | |
| ModuleMismatch | fatal | 350 | When initializing a transport layer module, a mismatch was found between the name the loader thought was the module's name, and the actual name. | |
| NConnectFailed | warning | 401 | When the NSAP address gives multiple actual addresses, the transport layer will attempt each address in turn. This message logs the failure of the initial addresses. | |
| Negotiation | fatal | 230 | The transport providers failed to negotiate. Normally a result of a failure to agree a transport class. | |
| NetDisconnect | error | 51 | The network connection was lost. | |
| NetRefused | error | 236 | Failed to create the network connection over which the transport connection is made. | |
| NoEndPoint | error | 309 | The transport provider does not use an end point which can be used with poll() or select(). | |
| NoFactory | fatal | 310 | The transport stack implementation lacks a factory method for the type of object required. | |
| NoNSAPAddress | error | 301 | There was no network address in the transport called address. | |
| NoProvider | error | 308 | The operation could not be performed as there was no transport service provider. | |
| NormalDisconnect | success | 228 | A normal transport layer disconnection. | |
| NoSession | fatal | 102 | The session entity is not attached to a TSAP. | |
| NoStack | fatal | 311 | There was no transport stack configured for the given network address. | |
| Notice | notice | 6 | General notice level event: See log entry for details | No Operator Action |
| NoticeS | notice | 22 | General notice level event: See log entry for details | No Operator Action |
| NoTsap | fatal | 312 | There was no transport stack configured for the given network address. | |
| NotSpecified | error | 100 | A transport level disconnect was sent with no specific reason. | |
| NoUser | fatal | 300 | There was no TS User object available for the transport layer. This is a programming error. | |
| Overflow | error | 235 | It was not possible to assign a connection reference as there were too many assigned. | |
| Protocol | error | 233 | A protocol error was detected. | |
| RejectBadParam | error | 304 | A received TPDU has an unknown parameter field. | |
| RejectBadType | error | 305 | A received TPDU has an unknown TPDU type field. | |
| RejectBadValue | error | 306 | A received TPDU has an invalid value for the given field | |
| RejectReceived | error | 307 | The peer system rejected a TPDU for the reason given. | |
| RejectUnspecified | error | 303 | A received TPDU was rejected for no specific overall reason, more detail is given in the context. | |
| RemoteCongestion | error | 229 | Lack of resources or some other transient problem caused a transport layer disconnection. | |
| RestoreFailure | fatal | 351 | There was a failure when rebuilding the information for a transport endpoint following transfer of the endpoint to another process. | |
| Tailoring | fatal | 313 | There is a value error in the loading the tailoring for the transport provider module. If the value is <missing> then a mandatory value is missing from the tailoring file. | |
| Timer | info | 30 | A timeout was encountered. | |
| TPDU | pdu | 2 | Transport PDU | No Operator Action |
| UserData | info | 54 | ||
| Waiting | warning | 32 | There are indications waiting |