Datatype UTCTimestamp
SYNOPSIS:
string field representing time/date combination represented in UTC (Universal Time Coordinated, also known as "GMT") in either YYYYMMDD-HH:MM:SS (whole seconds) or YYYYMMDD-HH:MM:SS.sss* format, colons, dash, and period required.
Valid values:
YYYY = 0000-9999, MM = 01-12, DD = 01-31, HH = 00-23, MM = 00-59, SS = 00-60 (60 only if UTC leap second), sss* fractions of seconds.
The fractions of seconds may be empty when no fractions of seconds are conveyed (in such a case the period is not conveyed), it may include 3 digits to convey milliseconds, 6 digits to convey microseconds, 9 digits to convey nanoseconds, 12 digits to convey picoseconds; Other number of digits may be used with bilateral agreement.
Leap Seconds: Note that UTC includes corrections for leap seconds, which are inserted to account for slowing of the rotation of the earth. Leap second insertion is declared by the International Earth Rotation Service (IERS) and has, since 1972, only occurred on the night of Dec. 31 or Jun 30. The IERS considers March 31 and September 30 as secondary dates for leap second insertion, but has never utilized these dates. During a leap second insertion, a UTCTimestamp field may read "19981231-23:59:59", "19981231-23:59:60", "19990101-00:00:00". (see http://tycho.usno.navy.mil/leapsec.html)
EXAMPLE: TransactTime(60)="20011217-09:30:47.123" millisecond
TransactTime(60)="20011217-09:30:47.123456" microseconds
TransactTime(60)="20011217-09:30:47.123456789" nanoseconds
TransactTime(60)="20011217-09:30:47.123456789123" picoseconds
Pedigree
| Added |
EP |
Updated |
EP |
Deprecated |
EP |
| FIX.4.2 | | FIX.5.0SP2 | 256 | | |
Mappings
| Standard |
Base type |
Parameter |
Pattern |
| XML | xs:dateTime | | |