Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
OrigSendingTime <122>
- Tag
122- Type
- UTCTimestamp (base String)
- FIXML name
OrigSnt- Pedigree
- Added FIX 4.0
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
This page shows OrigSendingTime <122> as defined in FIX 4.4. For the current standard, see tag 122 OrigSendingTime in FIX Latest.
OrigSendingTime <122> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
OrigSendingTime carries the original transmission time, in UTC, of a message that is being sent again as the result of a resend request.
Where it is used
StandardHeader (component) . In all, 93 messages in FIX 4.4 can carry it. Full list.
Example message
8=FIX.4.4|9=184|35=D|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|43=Y|122=20261116-08:29:00.000|11=ORD-1001|1=ACCT-01|21=1|55=AAPL|54=1|60=20261116-08:30:00.000|38=1000|40=2|44=190.50|59=0|10=124 Illustrative example, not real orders or market data. A NewOrderSingle (35=D) in FIX 4.4, shown with BeginString FIX.4.4. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.4 dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Original time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as "GMT") when transmitting orders as the result of a resend request.
Used in
Components and repeating groups (1)
| Name | Kind | Presence |
|---|---|---|
| StandardHeader | Component | Optional |
All 93 messages that can carry OrigSendingTime, including through components and groups
- Advertisement
- AllocationInstruction
- AllocationInstructionAck
- AllocationReport
- AllocationReportAck
- AssignmentReport
- BidRequest
- BidResponse
- BusinessMessageReject
- CollateralAssignment
- CollateralInquiry
- CollateralInquiryAck
- CollateralReport
- CollateralRequest
- CollateralResponse
- Confirmation
- ConfirmationAck
- ConfirmationRequest
- CrossOrderCancelReplaceRequest
- CrossOrderCancelRequest
- DerivativeSecurityList
- DerivativeSecurityListRequest
- DontKnowTrade
- ExecutionReport
- Heartbeat
- IOI
- ListCancelRequest
- ListExecute
- ListStatus
- ListStatusRequest
- ListStrikePrice
- Logon
- Logout
- MarketDataIncrementalRefresh
- MarketDataRequest
- MarketDataRequestReject
- MarketDataSnapshotFullRefresh
- MassQuote
- MassQuoteAcknowledgement
- MultilegOrderCancelReplace
- NetworkCounterpartySystemStatusRequest
- NetworkCounterpartySystemStatusResponse
- NewOrderCross
- NewOrderList
- NewOrderMultileg
- NewOrderSingle
- News
- OrderCancelReject
- OrderCancelReplaceRequest
- OrderCancelRequest
- OrderMassCancelReport
- OrderMassCancelRequest
- OrderMassStatusRequest
- OrderStatusRequest
- PositionMaintenanceReport
- PositionMaintenanceRequest
- PositionReport
- Quote
- QuoteCancel
- QuoteRequest
- QuoteRequestReject
- QuoteResponse
- QuoteStatusReport
- QuoteStatusRequest
- RFQRequest
- RegistrationInstructions
- RegistrationInstructionsResponse
- Reject
- RequestForPositions
- RequestForPositionsAck
- ResendRequest
- SecurityDefinition
- SecurityDefinitionRequest
- SecurityList
- SecurityListRequest
- SecurityStatus
- SecurityStatusRequest
- SecurityTypeRequest
- SecurityTypes
- SequenceReset
- SettlementInstructionRequest
- SettlementInstructions
- TestRequest
- TradeCaptureReport
- TradeCaptureReportAck
- TradeCaptureReportRequest
- TradeCaptureReportRequestAck
- TradingSessionStatus
- TradingSessionStatusRequest
- UserRequest
- UserResponse
- XMLnonFIX