Skip to end of banner
Go to start of banner

Retransmit Reject

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

CME Globex sends a Retransmit Reject message when a Retransmit Request message from the customer is rejected.

35=RetransmitReject

TagNameBinary TypeBinary LengthReqEnumerationDescription
39011ReasonString4848N

Reject reason details.

Will only be used for descriptive rejects.

39001UUIDuInt648Y

Matches RetransmitRequest.UUID.

39017LastUUIDuInt64NULL8N

Matches RetransmitRequest.LastUUID.

39002RequestTimestampuInt648Y
Matches RetransmitRequest.RequestTimestamp.
39012ErrorCodesuInt162Y

Rejection reasons:

0 - OutOfRange: FromSeqNo + Count is beyond the range of sequence numbers

1 - InvalidUUID: The specified UUID is unknown or is not authorized for the requester to access.

2 - RequestLimitExceeded: The message count exceeds maximum retransmission size of single request

3 - RetransmitAlreadyInProgress: Prior Retransmit still in progress so cannot send a new one

4 - InvalidTimestamp: Value sent by the client in RequestTimestamp is out of acceptable range (MIN, MAX)

5 - InvalidFromSeqNo: Value sent by the client in FromSeqNo is out of acceptable range (MIN, MAX)

6 - RequiredUUIDMisssing: null value in UUID field

7 - RequiredRequestTimestampMissing: null value in RequestTimestamp field

8 - RequiredFromSeqNoMissing: null value in FromSeqNo field

9 - RequiredMsgCountMissing: null value in MsgCount field

9553SplitMsgSplitMsg1N

0=Split Msg Delayed

1=Out of Order Msg Delayed

2=Complete Msg Delayed

Indicates if a message was delayed as a result of:

  • being split among multiple packets (0)
  • TCP re-transmission (1)
  • due to a previously submitted split or out of order message (2).

If absent then the message was not delayed, split, or received out of order.

  • No labels