Date and Time Format Variables

3DSpace provides six different variables that define formats for the display and entry of dates and times.

See Also
About Date and Time Formats
Live Collaboration Settings
Configuring Live Collaboration
Variable (format) Meaning/Usage Default Tokens
MX_NORMAL_DATETIME_FORMAT Normal (long) date/time. Used for displaying all dates. Also, the system first attempts to parse entered dates using this pattern. +day mon dom+, +yr4 h12:min:sec +mer +tz
MX_NORMAL_DATE_FORMAT Normal (long) date only. Used for displaying date-only entries, like date attributes. +day mon dom+, +yr4
MX_NORMAL_TIME_FORMAT Normal (long) time only. Currently not used. h12:min:sec +mer +tz
MX_TERSE_DATETIME_FORMAT Terse (short) date/time. Provides additional format for date/time input. moy/dom-/-yr2 h12:min-:-sec +mer
MX_TERSE_DATE_FORMAT Terse (short) date only. Provides additional format for date input. moy/dom-/-yr2
MX_TERSE_TIME_FORMAT Terse (short) time only. Currently not used. hr12:min-:-sec +mer
Note that day, yr4, mer, and tz are normally displayed in date/time strings by default, but are not required input when entering a date (as denoted by the + preceding these tokens). Also, yr2 and sec are required as input in the terse formats, but are not displayed in corresponding formatted strings.

These formats are used for both displaying dates in Studio Modeling Platform apps and for parsing dates input to the system. (These formats do not affect the format of displayed dates/times in apps.) The "normal" formats are used for displaying and/or entering dates and times, while the "terse" formats may optionally be used for input. In other words, when a date/time is entered, the system attempts to parse it with the "normal" format first. If that doesn't work, the system tries the "terse" format.

When using apps, the normal and terse datetime formats are set in the MatrixIniDefaults program, which is installed with the framework. These settings must be in sync with properties in emxSystem.properties. Do not adjust these settings in the server's .ini file because they will override the setting in the MatrixIniDefaults program.

For more information about configuring date/time formats for the apps, see Installation and Setup | Administrate | 3DEXPERIENCE Platform | 3DSpace Administration | Live Collaboration Server | Configuring Live Collaboration | Configuring Date and Time Formats.

Date formats may be made up of any combination of the following tokens:

Token Meaning
day day of the week (mon, tue, wed,...)
DAY day of the week, not abbreviated
mon month (jan, feb, mar,...)
MON month, not abbreviated
tz time zone (edt, cdt, pdt,...)
TZ time zone, not abbreviated
mer time meridian (am, pm, or blank for 24 hour time)
sec seconds, 0 - 59
min minutes, 0 - 59
h12 hour in 12 hour format, "mer" will be non-blank
H12 hour in 12 hour format, "mer" will be non-blank. Always outputs 2 digits, for example, 05.
h24 hour in 24 hour format, "mer" will be blank
H24 hour in 24 hour format, "mer" will be blank. Always outputs 2 digits, for example, 05.
yr2 abbreviated year (98, 99, 00...)
yr4 full year (1998, 1999, 2000..)
dom day of month (1, 2, 3,..., 31)
DOM day of month (1, 2, 3,..., 31). Always outputs 2 digits, for example, 04.
doy day of year (1, 2, 3,..., 365)
DOY day of year (1, 2, 3,..., 365). Always outputs 3 digits, for example, January 3 would be 003.
moy month of year (1, 2, 3,..., 12)
MOY month of year (1, 2, 3,..., 12). Always outputs 2 digits, for example, 04.