Flat File Connections > Flat file connections > Flat file connection properties
  

Flat file connection properties

Defines the properties you need to assign to for a flat file source connection.
The following table describes the flat file connection properties:
Connection Property
Description
Runtime Environment
Runtime environment that contains the Secure Agent to use for accessing the flat files.
Or for CDI, a serverless runtime environment that contains the mounted EFS or NFS directories which contain the flat files.
Note: Do not select a runtime environment with Secure Agents that run on NTT. A flat file connection cannot use a Secure Agent that runs on NTT.
Directory
Directory where the flat file is stored. Must be accessible by all Secure Agents in the selected runtime environment.
Enter the full directory or click Browse to locate and select the directory.
When you use the connection, you can select a file that's contained in the directory or in any of its subdirectories.
This directory is also used in any data disks configured for a serverless runtime environment.
Maximum length is 100 characters. Directory names can contain alphanumeric characters, spaces, and the following special characters:
/ \ : _ ~
The directory is the service URL for this connection type.
Note: On Windows, the Browse for Directory dialog box does not display mapped drives. You can browse My Network Places to locate the directory or enter the directory name in the following format: \\<server_name>\<directory_path>. If network directories do not display, you can configure a login for the Secure Agent service.
Do not include the name of the flat file. You specify the file name when you create the task.
In a serverless runtime environment, this directory must be one of the mounted directories or their sub directories in the data disk.
Browse button
Use to locate and select the directory where flat files are stored.
Date Format
Date format for date fields in the flat file. Default date format is:
MM/dd/yyyy HH:mm:ss
Code Page
The code page of the system that hosts the flat file. Select one of the following code pages:
  • - MS Windows Latin 1. Select for ISO 8859-1 Western European data
  • - UTF-8. Select for Unicode data
  • - UTF-16 encoding of Unicode (Big Endian)
  • - UTF-16 encoding of Unicode (Lower Endian)
  • - Shift-JIS. Select for double-byte character data.
  • - ISO 8859-15 Latin 9 (Western European)
  • - ISO 8859-2 Eastern European
  • - ISO 8859-3 Southeast European
  • - ISO 8859-5 Cyrillic
  • - ISO 8859-9 Latin 5 (Turkish)
  • - IBM EBCDIC International Latin-1
  • - Japanese EUC (with \ <-> Yen mapping
  • - IBM EBCDIC Japanese
  • - IBM EBCDIC Japanese CP939
  • - PC Japanese SJIS-78 syntax (IBM-942)
  • - PC Japanese SJIS-90 (IBM-943)
  • - MS Windows Traditional Chinese, superset of Big 5
  • - Taiwan Big-5 (w/o euro update)
  • - Chinese EUC
  • - ISO 8859-8 Hebrew
  • - PC Hebrew (old)
  • - PC Hebrew (w/o euro update)
  • - EBCDIC Hebrew (updated with new sheqel, control characters)
  • - IBM EBCDIC US English IBM037
  • - UTF-32 encoding of Unicode (Lower Endian)
  • - ISO 8859-1 Western European.
  • - IBM EBCDIC French
  • - ISO 8859-10 Latin 6 (Nordic) *
  • - EBCDIC Finland, Sweden
  • - MOS-DOS Thai, superset of TIS 620
  • - 7-bit ASCII
  • - EBCDIC Finland, Sweden (w/euro update)
  • - MS-DOS Windows Latin 2 (Central Europe)
  • - Japanese EBCDIC-Kana Fujitsu
In advanced mappings, flat file objects in cloud storage connections must use UTF-8 encoding.
If the file contains supplementary characters with UTF-16 encoding, the task fails.
Note: When you use a flat file connection with the Shift-JIS code page and a UTF data object, be sure to install fonts that fully support Unicode.
* Data preview uses a similar ISO 8859-4 Scandinavian/Baltic code page, but runtime processing uses ISO 8859-10 Latin 6 (Nordic), so data preview and runtime encoding won't match.