Connections for INFACore > Connections to source and target endpoints > ODBC
  

ODBC

Create an ODBC connection to connect to an application that is ODBC compliant.

Feature snapshot

Operation
Support
Read
Yes
Write
Yes

Connection properties

Configure the connection properties to connect to DB2.
Before you configure the connection properties, you'll need to get information from DB2.
The following table describes the ODBC connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
User Name
User name for the database login.
Password
Password for the database login. The password cannot contain a semicolon.
Data Source Name
System DSN.
Schema
Schema used for the source or target.
Code Page
The code page of the database server or flat file defined in the connection. 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.
  • - 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 Extended UNIX Code (incl. JIS X 0212)
  • - Japanese EUC (with \<-> Yen mapping)
  • - Japanese EUC (Packed Format)
  • - IBM EBCDIC Japanese
  • - IBM EBCDIC Japanese CP939
  • - Japanese EBCDIC Fujitsu
  • - HITACHI KEIS Japanese
  • - NEC ACOS JIPSE Japanese
  • - UNISYS Japanese
  • - MITSUBISHI MELCOM Japanese
  • - Japanese EBCDIC-Kana Fujitsu
  • - HITACHI KEIS-Kana Japanese
  • - NEC ACOS JIPSE-Kana Japanese
  • - UNISYS-Kana Japanese
  • - MITSUBISHI MELCOM-Kana Japanese
  • - EBCDIC Japanese
  • - EBCDIK Japanese
  • - PC Japanese SJIS-78 syntax (IBM-942)
  • - PC Japanese SJIS-90 (IBM-943)
  • - EBCDIC Japanese Katakana SBCS
  • - EBCDIC Japanese Katakana (w/ euro)
  • - EBCDIC Japanese Latin-Kanji (w/ euro)
  • - EBCDIC Japanese Extended (DBCS IBM-1390 combined with DBCS IBM-1399)
  • - EBCDIC Japanese Latin (w/ euro update)
  • - EBCDIC Japanese Katakana SBCS (w/ euro update)
  • - MS Taiwan Big-5 w/ HKSCS extensions
  • - MS Windows Traditional Chinese, superset of Big 5
  • - Taiwan Big-5 (w/ euro update)
  • - Taiwan Big-5 (w/o euro update)
  • - PC Chinese GBK (IBM-1386)
  • - Chinese EUC
  • - Simplified Chinese (GB2312-80)
  • - Hong Kong Supplementary Character Set
  • - ISO 8859-8 Hebrew
  • - PC Hebrew (old)
  • - PC Hebrew (w/o euro update)
  • - PC Hebrew (w/ euro update)
  • - MS Windows Hebrew (older version)
  • - MS Windows Hebrew (w/o euro update)
  • - Lotus MBCS encoding for Windows Hebrew
  • - EBCDIC Hebrew (updated with sheqel, control characters)
  • - EBCDIC Hebrew (w/ euro)
  • - EBCDIC Hebrew (updated w/ euro and new sheqel, control characters)
  • - Israeli Standard 960 (7-bit Hebrew encoding)
ODBC Subtype
The ODBC connection subtype that you must select to connect to a specific database. The subtype defines the capabilities that you can configure while you create a mapping.
You can select the DB2 option to read from or write to DB2.
The rest of the options are not applicable.
Driver Manager for Linux
When you create a new ODBC connection on Linux platform, you can select a driver manager for the Linux Secure Agent. Select one of the following driver managers:
  • - Data Direct
  • - unixODBC2.3.0
  • - unixODBC2.3.4
The default driver manager is UnixODBC2.3.0.

Read properties

The following table describes the advanced source properties that you can configure in the Python code for the read operation:
Property
Description
Pre SQL
Pre-SQL command that must be run before reading data from the source.
Post SQL
Post-SQL command that must be run after reading data from the source.
SQL Override
The SQL statement to override the default query generated from the specified source type to read data from the ODBC source.

Write properties

The following table describes the advanced target properties that you can configure in the Python code for the write operation:
Property
Description
Update Override
An update SQL statement that updates the data in an ODBC target table. The update SQL statement you specify overrides the default update statements that the Secure Agent generates to update the target based on key columns. You can define an update override statement to update target tables based on both key or non-key columns.
In the override statement, you must enclose all reserved words in quotation marks.