Skip to content
FIXtags

FIX MESSAGE 35=2

ResendRequest

MsgType (35) = 2SessionAdded FIX.2.7

Definition

The resend request is sent by the receiving application to initiate the retransmission of messages. This function is utilized if a sequence number gap is detected, if the receiving application lost a message, or as a function of the initialization process.

FIX 4.2 group names/IDs were assigned during the official Orchestra translation; some mappings to later versions are approximate. This layout stays within the 4.2 source.

Message structure 32 distinct fields

Source order, including nested components and groups. Group counts precede the repeated entries. “Required here” is relative to the enclosing component or group, not unconditional in the message. A dash means not marked required; conditional requirements remain in the source notes. This is a reference, not a counterparty-specific validator.

  1. StandardHeaderComponentRequired

    MsgType = 2

    StandardHeader definition & usage →

    1. 8 BeginStringStringRequired here

      FIX.4.2 (Always unencrypted, must be first field in message)

    2. 9 BodyLengthintRequired here

      (Always unencrypted, must be second field in message)

    3. 35 MsgTypeStringRequired here

      (Always unencrypted, must be third field in message)

    4. 49 SenderCompIDStringRequired here

      (Always unencrypted)

    5. 56 TargetCompIDStringRequired here

      (Always unencrypted)

    6. 115 OnBehalfOfCompIDString—

      Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    7. 128 DeliverToCompIDString—

      Trading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)

    8. 90 SecureDataLenint—

      Required to identify length of encrypted section of message. (Always unencrypted)

    9. 91 SecureDatadata—

      Required when message body is encrypted. Always immediately follows SecureDataLen field.

    10. 34 MsgSeqNumintRequired here

      (Can be embedded within encrypted data section.)

    11. 50 SenderSubIDString—

      (Can be embedded within encrypted data section.)

    12. 142 SenderLocationIDString—

      Sender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    13. 57 TargetSubIDString—

      "ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)

    14. 143 TargetLocationIDString—

      Trading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)

    15. 116 OnBehalfOfSubIDString—

      Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    16. 144 OnBehalfOfLocationIDString—

      Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    17. 129 DeliverToSubIDString—

      Trading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    18. 145 DeliverToLocationIDString—

      Trading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)

    19. 43 PossDupFlagBoolean—

      Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)

    20. 97 PossResendBoolean—

      Required when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)

    21. 52 SendingTimeUTCTimestampRequired here

      (Can be embedded within encrypted data section.)

    22. 122 OrigSendingTimeUTCTimestamp—

      Required for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)

    23. 212 XmlDataLenint—

      Required when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)

    24. 213 XmlDatadata—

      Can contain an XML-formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.) See Appendix M – FIXML Support

    25. 347 MessageEncodingString—

      Type of message encoding (non-ASCII characters) used in a message’s "Encoded" fields. Required if any "Encoding" fields are used.

    26. 369 LastMsgSeqNumProcessedint—

      The last MsgSeqNum value received and processed. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.

    27. 370 OnBehalfOfSendingTimeUTCTimestamp—

      Used when a message is sent via a "hub" or "service bureau". If A sends to Q (the hub) who then sends to B via a separate FIX session, then when Q sends to B the value of this field should represent the SendingTime on the message A sent to Q. (always expressed in UTC (Universal Time Coordinated, also known as "GMT")

  2. 7 BeginSeqNointRequired
  3. 16 EndSeqNointRequired
  4. StandardTrailerComponentRequired

    StandardTrailer definition & usage →

    1. 93 SignatureLengthint—

      Required when trailer contains signature. Note: Not to be included within SecureData field

    2. 89 Signaturedata—

      Note: Not to be included within SecureData field

    3. 10 CheckSumStringRequired here

      (Always unencrypted, always last field in message)