Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
OnBehalfOfSendingTime <370>
- Tag
370- Type
- UTCTimestamp (base String)
- Pedigree
- Added FIX 4.2
- Versions
- Not in FIX Latest · Not in FIX 4.4 · FIX 4.2 ✓
This page shows OnBehalfOfSendingTime <370> as defined in FIX 4.2. Tag 370 is not in FIX Latest. Search FIX Latest.
Description (from the Orchestra file)
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")
Used in
Components and repeating groups (1)
| Name | Kind | Presence |
|---|---|---|
| StandardHeader | Component | Optional |
All 46 messages that can carry OnBehalfOfSendingTime, including through components and groups
- Advertisement
- Allocation
- AllocationAck
- BidRequest
- BidResponse
- BusinessMessageReject
- DontKnowTrade
- ExecutionReport
- Heartbeat
- IOI
- ListCancelRequest
- ListExecute
- ListStatus
- ListStatusRequest
- ListStrikePrice
- Logon
- Logout
- MarketDataIncrementalRefresh
- MarketDataRequest
- MarketDataRequestReject
- MarketDataSnapshotFullRefresh
- MassQuote
- NewOrderList
- NewOrderSingle
- News
- OrderCancelReject
- OrderCancelReplaceRequest
- OrderCancelRequest
- OrderStatusRequest
- Quote
- QuoteAcknowledgement
- QuoteCancel
- QuoteRequest
- QuoteStatusRequest
- Reject
- ResendRequest
- SecurityDefinition
- SecurityDefinitionRequest
- SecurityStatus
- SecurityStatusRequest
- SequenceReset
- SettlementInstructions
- TestRequest
- TradingSessionStatus
- TradingSessionStatusRequest