Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

DBMOVER Configuration File Statements

DBMOVER Configuration File Statements

PowerExchange 10.5 introduces new and changed statements in the DBMOVER configuration file.
The following statement is for optional use:
QQAQINILIB=
library_name
New
. Specify the library name that contains the QQAQINI query options file. If you do not specify this statement, PowerExchange uses the default library specified for the IBM i system.
In PowerCenter, you can override the QAQQINILIB setting in the DBMOVER configuration file by entering QAQQINILIB=
library_name
in the
PWX Override
connection attribute for the Db2 for i connection.
The following new and changed statements are for enabling TLS networking for IBM i:
LISTENER
Changed.
To use TLS networking for IBM i, you can specify SSL in tenth comma position. When you use TLS networking, the send and receive sizes in the sixth and seventh comma positions of the LISTENER statement must be set to a value that does not exceed 16384.
SSL_CONTEXT_METHOD
Changed.
As of PowerExchange 10.5, you can use the SSL_CONTEXT_METHOD statement to enable TLS networking for IBM i.
Informatica recommends avoiding the use of protocols TLSV1_1 and TLSV1, and specifying protocol TLSV1_2 on all machine types. The TLSV1_3 protocol is not currently supported by PowerExchange.
On IBM i:
  • TLSV1
    is allowed on V5R2.
  • TLSV1_1
    is allowed on V5R2.
  • TLSV1_2
    is allowed on V5R2, V5R3, and V5R4 and is the recommended choice.
If SSL_CONTEXT_METHOD is not specified then the default is that the system will accept a connection request for all protocols supported by the IBM i release.
Informatica recommends specifying protocol TLSV1_2 on all machine types. The TLSV1_3 protocol is currently not supported by PowerExchange.
SSL_CIPHER_LIST
Changed.
As of PowerExchange 10.5 on IBM i, you can specify ciphers by using four hexadecimal digits.
SSL_REQ_CLNT_CERT
Changed.
As of PowerExchange 10.5, you can use the SSL_REQ_CLNT_CERT statement on IBM i. Valid values are:
  • Y
    . The GSK session type is SERVER SESSION WITH CLIENT AUTHORITY. The X509 subject certificate from the client machine is validated against the trusted Certificate Authorities (CAs) on the IBM i server.
  • N
    . The GSK session type is SERVER SESSION. The client machine subject certificates are not requested or validated.
SSL_TOLERATE_UNTRUSTED_ISSUER
New.
PowerExchange 10.5 introduces the SSL_TOLERATE_UNTRUSTED_ISSUER statement for use on IBM i only. Valid values are:
  • Y
    . Continue processing after a certificate error 6000 has been reported. A certificate error 6000 occurs when SSL_REQ_CLNT_CERT=Y and the partner CA is not present among the trusted CAs on the IBM i machine.
  • N
    . After certificate error 6000 has been reported, the connection is not accepted.
Default is N.
For more information, see the "DBMOVER Configuration File" chapter in the
PowerExchange Reference Manual
.

0 COMMENTS

We’d like to hear from you!