Isode Events (Facility Detail)

Summary: Isode components write to logging streams when events occur.

Facility S5066msg

A set of messages for S5066 functionality

NameSeverityIDDescriptionAction
ARQmodefatal17The server connection was broken as a result of the client attempting a broadcast session using ARQ Mode. Application error.
BadPDUlengthfatal10An attempt was made to send a PDU with an invalid length. Programmer error.
BindAcceptPDUIndetail54
BindPDUOutdetail50
BindRejecterror8The bind to the S'5066 server failed, for the given reason. The action will depend upon the failure reason.
BindRejectPDUIndetail55
Boundsuccess7The user has been bound to the server and can commence operations. The value is the maximum MTU size allowed.
BufferTooSmallwarning23The S'5066 user provided a buffer which was not big enough to hold the largest U_PDU. Programmer error.
DataErrorswarning24A Data PDU has received with parts of it in error, and parts of it missing. It was discarded Results from transmission problems.
DataFlowPDUIndetail57
DiscardDatawarning25An RCOP/UDOP PDU for an unregistered connection ID has been received. It was discarded
DuplicateSAPfatal2More than one user is attempting to use the same S'5066 SAP value, and the SAP is not RCOP or UDOP. Programmer or configuration error
FlowOffsuccess29The S'5066 server can't take more data
FlowOnsuccess28The S'5066 server can take more data
ForcedUnbindfatal18The server connection was broken for an unknown reason. Check server logs.
Inactivefatal14The server connection was broken as a result of the failure of the client to respond to "keep-alive" messages. The application must be hanging up for more than 120 seconds
InvalidAddresserror11An attempt was made to send data to an invalid address. Probably programmer error.
InvalidConnIDfatal5A requested RCOP/UDOP connection ID is out of range. Programmer or configuration error
InvalidPDUfatal19An invalid PDU was received from the server. Possible communication problem or server software error
InvalidPDUlengthfatal22The actual length of a PDU does not correspond with the expected length. Possible communication problem or server software error
InvalidPrimitivesfatal15The server connection was broken as a result of the client sending too many invalid primitives Determine what other clients are using the server.
InvalidSAPfatal4A requested S'5066 SAP value is out of range. Programmer or configuration error
KeepAlivePDUIndetail58
KeepAlivePDUOutdetail53
NoAvailableConnIDfatal3More than one user is attempting to use the same RCOP or UDOP connection ID. Programmer or configuration error
NotInitializedfatal1An attempt was made to use STANAG 5066 services without the service being configured. Programmer or configuration error
OutOfOrderwarning26For RCOP or UDOP the PDU segments are expected in the order in which they were sent. This error indicates that an out-of-order segment was received. The segment is ignored. The sender may not have configured for in-order delivery, which is required for this implementation.
PDUrejectedwarning27
PreEmptedfatal13The server connection was broken as a result of a higher ranked client. Determine what other clients are using the server.
ReadPDUpdu101S'5066 data read
SAPclosingfatal6An attempt to bind to a server connection failed because the connection was in the process of closing. Programmer or configuration error
ServerClosedfatal12The server closed the connection unexpectedly Check the state of the server.
TooMuchExpeditedfatal16The server connection was broken as a result of the client sending too many expedited data primitives Application error.
Unbindnotice9The S'5066 server has unbound the client following the client's request. The action will depend upon the failure reason.
UnbindPDUIndetail56
UnbindPDUOutdetail51
UnexpectedPDUtypefatal21A PDU with a type was received from the server which the server should not be sending. Could be communication issue, or server error.
UnidataConfirmdetail61
UnidataPDUIndetail59
UnidataPDUOutdetail52
UnidataRejectdetail60
UnknownPDUtypefatal20A PDU with an unknown type was received from the server. Could be communication issue, or server error.
WritePDUpdu100S'5066 data written

NotInitialized

Message Text
  • S'5066 Provider not initialized
Description
An attempt was made to use STANAG 5066 services without the service being configured.
Action
Programmer or configuration error

DuplicateSAP

Message Text
  • Duplicate S'5066 SAP: %1
Parameters
  1. Conflicting SAP value
Description
More than one user is attempting to use the same S'5066 SAP value, and the SAP is not RCOP or UDOP.
Action
Programmer or configuration error

NoAvailableConnID

Message Text
  • Cannot find RCOP/UDOP connection ID
Description
More than one user is attempting to use the same RCOP or UDOP connection ID.
Action
Programmer or configuration error

InvalidSAP

Message Text
  • Invalid S'5066 SAP: %1
Parameters
  1. Conflicting SAP value
Description
A requested S'5066 SAP value is out of range.
Action
Programmer or configuration error

InvalidConnID

Message Text
  • Invalid RCOP/UDOP connection ID: %1
Parameters
  1. Conflicting ConnID value
Description
A requested RCOP/UDOP connection ID is out of range.
Action
Programmer or configuration error

SAPclosing

Message Text
  • S'5066 SAP closing: %1
Parameters
  1. SAP being requested
Description
An attempt to bind to a server connection failed because the connection was in the process of closing.
Action
Programmer or configuration error

Bound

Message Text
  • S'5066 User bound to server: MTU %1
Parameters
  1. MTU size
Description
The user has been bound to the server and can commence operations. The value is the maximum MTU size allowed.
Action

BindReject

Message Text
  • Bind failed: %1
Parameters
  1. Bind reject reason
Description
The bind to the S'5066 server failed, for the given reason.
Action
The action will depend upon the failure reason.

Unbind

Message Text
  • Normal server unbound
Description
The S'5066 server has unbound the client following the client's request.
Action
The action will depend upon the failure reason.

BadPDUlength

Message Text
  • Invalid PDU length %1
Parameters
  1. Proposed length
Description
An attempt was made to send a PDU with an invalid length.
Action
Programmer error.

InvalidAddress

Message Text
  • Invalid destination address
Description
An attempt was made to send data to an invalid address.
Action
Probably programmer error.

ServerClosed

Message Text
  • Server closed connection unexpectedly
Description
The server closed the connection unexpectedly
Action
Check the state of the server.

PreEmpted

Message Text
  • Server connection pre-empted by higher ranked client
Description
The server connection was broken as a result of a higher ranked client.
Action
Determine what other clients are using the server.

Inactive

Message Text
  • Server connection closed through inactivity
Description
The server connection was broken as a result of the failure of the client to respond to "keep-alive" messages.
Action
The application must be hanging up for more than 120 seconds

InvalidPrimitives

Message Text
  • Server connection closed, too many invalid primitives
Description
The server connection was broken as a result of the client sending too many invalid primitives
Action
Determine what other clients are using the server.

TooMuchExpedited

Message Text
  • Server connection closed, too many expedited data primitives
Description
The server connection was broken as a result of the client sending too many expedited data primitives
Action
Application error.

ARQmode

Message Text
  • Server connection closed, ARQ mode unsupportable
Description
The server connection was broken as a result of the client attempting a broadcast session using ARQ Mode.
Action
Application error.

ForcedUnbind

Message Text
  • Server connection closed, unknown reason %1
Parameters
  1. Unknown unbind reason code
Description
The server connection was broken for an unknown reason.
Action
Check server logs.

InvalidPDU

Message Text
  • Invalid PDU received, %1 (%2)
Parameters
  1. Detailed reason
  2. Additional information
Description
An invalid PDU was received from the server.
Action
Possible communication problem or server software error

UnknownPDUtype

Message Text
  • Unknown PDU type %1
Parameters
  1. type code of PDU
Description
A PDU with an unknown type was received from the server.
Action
Could be communication issue, or server error.

UnexpectedPDUtype

Message Text
  • Unexpected PDU type %1
Parameters
  1. type code of PDU
Description
A PDU with a type was received from the server which the server should not be sending.
Action
Could be communication issue, or server error.

InvalidPDUlength

Message Text
  • Invalid PDU length, actual=%1 expected=%2
Parameters
  1. Actual length
  2. Expected length
Description
The actual length of a PDU does not correspond with the expected length.
Action
Possible communication problem or server software error

BufferTooSmall

Message Text
  • Provided buffer is too small %1
Parameters
  1. required size
Description
The S'5066 user provided a buffer which was not big enough to hold the largest U_PDU.
Action
Programmer error.

DataErrors

Message Text
  • Data PDU with %1 error blocks and %2 missing blocks
Parameters
  1. Number of blocks with errors
  2. Number of blocks not received
Description
A Data PDU has received with parts of it in error, and parts of it missing. It was discarded
Action
Results from transmission problems.

DiscardData

Message Text
  • Discarding data for unregistered connection ID %1
Parameters
  1. connection ID
Description
An RCOP/UDOP PDU for an unregistered connection ID has been received. It was discarded
Action

OutOfOrder

Message Text
  • Segment out of order, actual=%1 expected=%2
Parameters
  1. Actual sequence number
  2. Expected sequence number
Description
For RCOP or UDOP the PDU segments are expected in the order in which they were sent. This error indicates that an out-of-order segment was received. The segment is ignored.
Action
The sender may not have configured for in-order delivery, which is required for this implementation.

PDUrejected

Message Text
  • PDU to %1:%2 rejected: %3
Parameters
  1. Destination address
  2. Destination SAP
  3. Detailed reason
Description
Action

FlowOn

Message Text
  • S'5066 Flow control is on
Description
The S'5066 server can take more data
Action

FlowOff

Message Text
  • S'5066 Flow control is off
Description
The S'5066 server can't take more data
Action

BindPDUOut

Message Text
  • BIND pdu sent, SAP=%1 rank=%2 mode=0x%3
Parameters
  1. SAP
  2. rank
  3. mode
Description
Action

UnbindPDUOut

Message Text
  • Unbind pdu sent
Description
Action

UnidataPDUOut

Message Text
  • UNIDATA REQUEST pdu sent, dest=%1:%2 len=%3 prio=%4 mode=(%5,%6,%7) ttl=%8 applic=%9 connid=%10 pdunum=%11 pduseg=%12 data=%13
Parameters
  1. Destination address
  2. Destination SAP
  3. length
  4. priority
  5. Transmission mode
  6. Ack request
  7. PDU delivery order
  8. TTL
  9. Application ID
  10. Destination Connection ID
  11. PDU number
  12. PDU segment
  13. first part of data
Description
Action

KeepAlivePDUOut

Message Text
  • KEEPALIVE pdu sent
Description
Action

BindAcceptPDUIn

Message Text
  • BIND ACCEPT pdu received, mtusize=%1
Parameters
  1. mtusize
Description
Action

BindRejectPDUIn

Message Text
  • BIND REJECT pdu received, %1
Parameters
  1. reason
Description
Action

UnbindPDUIn

Message Text
  • UNBIND pdu received, %1
Parameters
  1. reason
Description
Action

DataFlowPDUIn

Message Text
  • DATA FLOW %1 pdu received
Parameters
  1. on/off
Description
Action

KeepAlivePDUIn

Message Text
  • KEEPALIVE pdu received
Description
Action

UnidataPDUIn

Message Text
  • UNIDATA INDICATION pdu received, src=%1:%2 len=%3 prio=%4 applic=%5 connid=%6 pdunum=%7 pduseg=%8
Parameters
  1. Source address
  2. Source SAP
  3. length
  4. priority
  5. Application ID
  6. Destination Connection ID
  7. PDU number
  8. PDU segment
Description
Action

UnidataReject

Message Text
  • UNIDATA REJECT pdu received, src=%1:%2: data=%3: %4
Parameters
  1. Source address
  2. Source SAP
  3. start of data
  4. Reason
Description
Action

UnidataConfirm

Message Text
  • UNIDATA CONFIRM pdu received, src=%1:%2 data=%3
Parameters
  1. Source address
  2. Source SAP
  3. start of data
Description
Action

WritePDU

Message Text
  • %1
Parameters
  1. File containing PDU
Description
S'5066 data written
Action

ReadPDU

Message Text
  • %1
Parameters
  1. File containing PDU
Description
S'5066 data read
Action

All rights reserved © 2002 - 2024 Isode Ltd.