Understanding Notes® Data Type Transfer Conversions

When using HCL Enterprise Integrator (HEI) or Domino® Enterprise Connection Services (DECS) and transferring data to and from DB2® databases, the following considerations are useful.

• Although several DB2® data types support 15 or more digits, for example DB2's BIGINT supports 19 digits, Notes® truncates and rounds values of 16 or more digits. For best results, use 15 digits or less when Notes® is the source or target of transfers.
• When using LotusScript®, LCFields that are defined to store a DB2® BIGINT should be of type LCTYPE_NUMERIC.
• When creating metadata in Notes® from a DB2® source, all DB2® number types will create a Notes® Number, all DB2® date or time types will create the Notes® DateTime, and all other DB2® data types will create Notes® Text.
• When creating metadata in DB2® from a Notes® source, the Notes® Number will create a DB2® DOUBLE, Notes® DateTime will create a DB2® TIMESTAMP, and all other Notes® data types will create a DB2® CLOB.
• DB2 Universal Database™ forces column-specific code pages in tables using the GRAPHIC data types. The Connector for DB2® ONLY supports the translation of data to a single code page. On UNIX™ platforms, this is the code page of the operating system. On Win32, this is the code page specified by the environment variable DB2CODEPAGE or the operating system code page if this variable is not set. The Connector for DB2® does not support the translation of multiple code pages per table, as seen with DB2® GRAPHIC data types. This consideration is most applicable to Japanese, traditional Chinese, and UNICODE code page usage. For more information, see the National Language Support (NLS) material in your DB2® user documentation.