Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.4
  • All Products

Table of Contents

Search

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

Release Guide

Release Guide

Back Next

DBMOVER Configuration File Statements

DBMOVER Configuration File Statements

The DBMOVER configuration file contains the following new, changed, and dropped statements:
ABEND_SW={
N
|Y}
Changed
. Option Y was changed to print the PowerExchange call stack by using CEE3DMP and the control areas at the time of the abend. Use this option to bypass IBM or third-party abend diagnostic tools. This option is for z/OS only.
CREDENTIALS_CASE={A|
D
|S]
Changed
. PowerExchange handling of mixed-case passwords under option A changed. On IBM i or z/OS, PowerExchange now processes and passes user IDs and passwords to the operating system for authentication, as follows:
  1. PowerExchange converts the user ID to uppercase.
  2. PowerExchange checks whether the operating system is configured to handle mixed-case passwords.
    • If the operating system is configured to handle mixed-case passwords, PowerExchange keeps the password case as is.
    • If the operating system is not configured to handle mixed-case passwords, PowerExchange converts the password to uppercase. On z/OS, if the password is longer than eight characters, which indicates it is a passphrase, PowerExchange keeps the case in which the password was entered.
IBMI_2ND_LEVEL_HELP={Y|
N
}
New
. Controls whether IBM i second-level help information is included in PowerExchange messages that report operating system or API errors. The second-level help provides additional information, such as a reason or reason code, to help diagnose the error.
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.
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.
SSL_CIPHER_LIST=
cipher_list
Changed.
 On IBM i, you can specify ciphers by using four hexadecimal digits.
SSL_CONTEXT_METHOD=
context_method
Changed.
 You can now use this statement to enable TLS networking for IBM i.
The TLSV1_3 protocol is not currently supported by PowerExchange. Informatica recommends that you use the TLSV1_2 protocol on all machine types, including IBM i. Avoid using TLSV1_1 and TLSV1.
On IBM i:
  • TLSV1
     is allowed on IBM i 5.2.
  • TLSV1_1
     is allowed on IBM i 5.2.
  • TLSV1_2
     is allowed on IBM i 5.2, 5.3, and 5.4 and is the recommended choice.
If you do not specify SSL_CONTEXT_METHOD, the default is that the system accepts connection requests for all protocols that the IBM i release supports.
Informatica recommends specifying protocol TLSV1_2 on all machine types. The TLSV1_3 protocol is currently not supported by PowerExchange.
SSL_REQ_CLNT_CERT={N|Y}
Changed
. The SSL_REQ_CLNT_CERT statement controls whether a PowerExchange server uses an SSL certificate to authenticate the identity of a PowerExchange client. You can now use this statement on IBM i. Valid values are:
  • Y
    . Use the GSK session type of 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
    . Use GSK session type of SERVER SESSION. The client machine subject certificates are not requested or validated.
Default is Y for PowerExchange servers on IBM i.
SSL_TOLERATE_UNTRUSTED_ISSUER={
N
|Y}
New.
 For use on IBM i systems, to control whether to continue or stop processing after a certificate error 6000 has been reported. Valid values are:
  • Y
    . Continue processing after a certificate error 6000 has been reported. A certificate error 6000 occurs when the SSL_REQ_CLNT_CERT statement is set to Y and the partner CA is not present among the trusted CAs on the IBM i machine.
  • N
    . Stop processing and do not accept the connection after certificate error 6000 has been reported.
SVCDUMP={
N
|Y}
New
. On z/OS, controls whether PowerExchange generates an SVCDUMP at the point of an abend.
The following statements can no longer appear in the DBMOVER configuration file:
  • REPOS_CONNECT
  • REPOS_DEFAULT_CONNECTION
  • REPOS_ENABLE
  • RPX_DIR
For more information, see the "DBMOVER Configuration File" chapter in the
PowerExchange Reference Manual
.
0 COMMENTS
We’d like to hear from you!