Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

General Tab

General Tab

On the
tab in the
PowerExchange Data Source
wizard, enter the following optional properties for a PowerExchange data source definition.
Integration Mask
The integration mask. Enter a comma-delimited list of any of the following options:
  • CPOOL. Initializes connection pooling.
  • DFN. If you specify DFN, the PowerExchange data source type is returned as follows:
    If you do not specify DFN, the following string is returned:
    Informatica recommends that you use the default value.
  • ILMBRIDGE. Specify this option if the Informatica Data Archive product accesses data via a JDBC-ODBC bridge connection to the PowerExchange ODBC driver. Specify this option to enable the following options: BINASCHAR, CLOSEDSTMREUSE, NOFKEYS, NOUNDERSCORE, SQLLEN4BYTES, and V3COLNAMES.
  • OWB. Defines various SQL validations and statement reuse properties. Used by Oracle Warehouse Builder.
  • V30. Causes the ODBC SQLColumns() call to return V3 column names. Used by the IBM DB2 Information Integrator (II).
  • VERBOSE. Causes extra messages to be generated regarding Integration Mask options.
In addition, you can enable the following Integration Mask options by specifying either the specific option or the ILMBRIDGE option:
  • BINASCHAR. Causes the ODBC SQLColAttributes() call to change BIN or VARBIN columns to CHAR or VARCHAR columns and double the lengths.
  • CLOSEDSTMREUSE. Causes a statement opened in read or select mode to be retained after an ODBC SQLFreeStmt() call of type SQL_CLOSE. Subset of StmtKeepAlive.
  • NOFKEYS. Causes the SQLForeignKeys() ODBC call to return an empty result set without a call to the PowerExchange Listener.
  • NOUNDERSCORE. Prevents underscore (_) characters from being replaced with the percent sign (%) in DTLDescribe processing. This option allows PowerExchange to process a single NRDB2 table.
  • SQLLEN4BYTES. Specifies that the JDBC-ODBC bridge calls SQLGetData with a 4-byte integer buffer to return the length of the target data.
  • V3COLNAMES. Causes ODBC V3 names to be returned for all metadata result sets, such as SQLTables(), SQLColumns(), and SQLPrimaryKeys(). Superset of the V30 flag.
Corresponding ODBC Parameter: COMPATIBILITY
Maximum Rows
The maximum rows for retrieval.
Valid values are from 0 to 2147483647.
Default is 0, which indicates unlimited rows.
Corresponding ODBC Parameter: MAXROWS
Pacing Size
The number of rows or kilobytes. Set this property when an application, such as an interactive application, cannot keep pace with the flow of data from the PowerExchange Listener.
For maximum performance, set this property to 0.
Default is the value of the API rows_requested parameter.
Corresponding ODBC Parameter: PACESIZE
Select this option to specify the pacing size in kilobytes.
Default is
Corresponding ODBC Parameter: INTERPRETASROWS
As Rows
Select this option to specify the pacing size in rows.
Default is
Corresponding ODBC Parameter: INTERPRETASROWS
Select this option to compress data.
This option is cleared by default.
Corresponding ODBC Parameter: COMPRESS
Select this option to encrypt data.
This option is cleared by default.
Corresponding ODBC Parameter: ENCRYPT, as follows:
  • If this option is selected, ENCRYPT=N.
  • If this option is cleared, ENCRYPT=Y.
The encryption option, which has the following value:
  • AES
    . Data is encrypted by using the Advanced Encryption Standard (AES) algorithm.
The values of
are deprecated. PowerExchange converts a value of
If you select an encryption option, you must select an encryption level in the
Corresponding ODBC Parameter: ENCRYPT
Required if you select the
encryption option.
The encryption level.
The options are:
  • 1
    . Use a 128-bit encryption key.
  • 2
    . Use a 192-bit encryption key.
  • 3
    . Use a 256-bit encryption key.
Default is
if the
encryption option is selected.
Corresponding ODBC Parameter: ENCRYPTLEVEL
MQ Get Opt
The type of read operation to be performed from an MQSeries queue.
The options are:
    . Reads a copy of the data on the queue.
  • READ
    . Reads the data and removes it from the queue.
Default is
Corresponding ODBC Parameter: MQGETOPT
The application name that identifies extracts. Specifying the application name increases the ability to identify individual use of a single connection. This is then available to task control.
Corresponding ODBC Parameter: DTLAPP
PWX Overrides
Optional. The following overrides apply to PowerExchange ODBC connections for bulk data movement or CDC sessions:
If you specify multiple overrides, use a comma (,) as a separator, for example:
ARRAYSIZE. The DB2 fetch array size, in number of rows, for DB2 bulk data movement operations that use the DB2 access method. The array size pertains to the DB2 multiple-row FETCH statements that PowerExchange uses to read data from DB2 source tables. Valid values are from 1 through 5000. Default is 25.
PowerExchange dynamically lowers the array size when all the following conditions are true:
  • The database type is DB2.
  • The table contains LOB columns.
  • The ARRAYSIZE value is greater than 1.
  • Row size * ARRAYSIZE is greater than 16000000 bytes.
LOWVALUES. If you previously set the LOWVALUES statement in the DBMOVER configuration file to Y for PowerExchange Client for PowerCenter (PWXPC) sessions, you can use this ODBC parameter to specify an override of LOWVALUES=N for sessions that use PowerExchange ODBC connections. You must use PWXPC instead of ODBC to preserve hexadecimal '0' values, called
low values
, in source character fields when passing these values to a PowerCenter session for delivery to a VSAM target on
or a sequential file target on Linux, UNIX, Windows, or z/OS.
QAQQINILIB. If you previously specified the QAQQINILIB statement in the DBMOVER configuration file, you can use this parameter to specify an alternate QAQQINI library for an IBM i source.
TCPIP_OP_TIMEOUT specifies a timeout, in seconds, for a network operation. When the client-side application thread detects that the network operation exceeds this timeout interval, PowerExchange ends the connection and issues a timeout error message.
TCPIP_CON_TIMEOUT specifies a timeout, in seconds, for a connection attempt. If PowerExchange cannot establish an ODBC connection within this time interval, PowerExchange issues an error message.
TCPIP_HB_INTERVAL specifies a heartbeat interval, in seconds, that overrides the default
heartbeat interval of 507 seconds. If PowerExchange does not receive data before the TCP/IP heartbeat interval elapses, PowerExchange ends the ODBC connection and associated workflow with a heartbeat timeout error. Use this override to prevent dropped connections from TCP/IP heartbeat timeout errors.
USE_CATALOG_METADATA. Specify USE_CATALOG_METADATA=Y to read metadata from the catalog during a DB2 bulk load session, rather than issuing a SELECT statement. Then, when PowerExchange reads the metadata from the catalog, it is not necessary to grant PowerExchange SELECT privileges on the table.
Corresponding ODBC Parameter: PWXOVERRIDES
Allow Insert Into 0 Rows
A SQL INSERT INTO schema.table operation on a source table might result in 0 rows being inserted and a SQL transformation error. When you select this option, PowerExchange suppresses the error condition and processing continues.
Corresponding ODBC Parameter: AllowInsertInto0Rows.


We’d like to hear from you!