ComplexEventEndDate (FIX tag 1493)

At a glance

Tag

1493

Name

ComplexEventEndDate

Datatype

UTCTimestamp (String)

Format

YYYYMMDD-HH:MM:SS[.sss]

Dialects

FIX 5.0 SP2

Messages

72

What the specification says

Specifies the end date of the date range on which a complex event is effective. The start date will be set equal to the end date for single day events such as Bermuda options

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 1493

Where tag 1493 appears

Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.

Wire format

A UTC date and time. The fractional-seconds part is optional, so two timestamps can be equal but not byte-identical. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 1493 in TypeScript

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";​const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);​const field = message.fields[1493];field?.name;   // "ComplexEventEndDate"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other UTCTimestamp fields

• 1492ComplexEventStartDate
• 1504RelSymTransactTime
• 1289DerivativeEventTime
• 1145EventTime
• 1012SideTrdRegTimestamp
• 962SideTimeInForce
• 779LastUpdateTime
• 769TrdRegTimestamp
• 629HopSendingTime
• 586OrigOrdModTime
• 515ExecValuationPoint
• 483TransBkdTime
• 443StrikeTime
• 438ContraTradeTime
• 370OnBehalfOfSendingTime
• 367QuoteSetValidUntilTime
• 345TradSesEndTime
• 344TradSesCloseTime
• 343TradSesPreCloseTime
• 342TradSesOpenTime
• 341TradSesStartTime
• 168EffectiveTime
• 126ExpireTime
• 122OrigSendingTime