File extension properties
| Keyword | Values or example | Description |
|---|---|---|
| dataFileExt | .dat | File extension for incoming ANSI X9.37, ANSI X9.100-187, X9.37 UCD, X9.100-187 UCD, and X9.100-180 transmissions |
| eofFileExt | .eof | File extension for the file that marks the end of transmission. |
| rteFileExt | .rte | File extension for route information files |
| fatfFileExt | .fat | File extension for fixed account table files |
| derFileExt | .der | File extension for primary DTA error files |
| vlfFileExt | .vlf | File extension for VLF files |
| ciffFileExt | .ciff | File extension for CIFF files |
| captureFileExt | .rcap | File extension for storing remote capture messages |
| errorFileExt | .err | File extension for error files |
| endofdayFileExt | .eod | File extension for end of day (EOD) files |
When a data file is presented to the Gateway Server, it is accompanied by a file with the same name, but with an EOF extension. The accompanying EOF trigger file indicates to the Gateway Server that all data files needed to process the related data file are available.
Using the incoming EOF required column of the file suffix table, specify whether the EOF trigger file is needed. If N or No is specified, the EOF file is not needed to process the data file and the Gateway Server begins processing the data file when it is exclusively available. Ensure all files that are associated with the data file are present before the data file arrives in the incoming source folder. The default value of the incoming EOF required column is Y or Yes, which requires an EOF file for each data file presented to the Gateway Server.
If an EOF file is not used, put the file in the source folder with a different file extension. Then, rename the file to the final file name with the correct file extension when the entire file is in the source folder. For example, move filename.tmp to the source folder and then rename the file to filename.dat.