You are here: Field Rules Reference > Field Rules Summary > RunDate

RunDate

Use this field level rule to get the run date from the transaction data (TRNFILE.DAT file) and format that date using the mask you specify.

The mask on the RunDate rule supports the following syntax:

A number (between 1 and 10 for compatibility with prior releases) and this format: DinFmt:outFmt

The D indicates a date conversion using the new method. Here is a list of the date formats you can choose:

Enter

To take a date in this format...

And output it in this format...

1

YYMMDD

MMDDYY

2

YYYYMMDD

MMDDYYYY

3

YYYYMMDD

MMDDYY

4

YYMMDD

MM-DD-YY

5

YYMMDD

MM/DD/YY

6

YYYYMMDD

MM-DD-YY

7

YYYYMMDD

MM/DD/YY

8

MMDDYY

MM-DD-YY

9

MMDDYY

MM/DD/YY

10

YYYMMDD

MM/DD/YY

D

inFmt is one of the standard date formats which consists of a format character, optional date separator, and an optional year size (2 or 4).

outFmt is also a standard date format for the destination field and is separated from the inFmt by a colon (:).

For compatibility with prior releases, masks (1 through 10) and the destination formats with a single letter, such as D, indicate the system will omit leading zeros or spaces. Also, please note that Month indicates both upper- and lowercase letters are used while MONTH indicates only uppercase letters are used. Mon indicates the month will be abbreviated in upper- and lowercase letters.

Using locales

If you use one of the standard formats, use the @XXX (without the percent). For example, D44@CAD is the standard format for Month DD, YYYY in Canadian French. If you are creating your own format, use %@???. For instance, D%@CAD%B %#d, %Y yields the same result as the standard format D44@CAD.

Note The run date is typically stored in YYYYMMDD format and therefore does not require any locale information on the input format.

See also