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.4.0 HotFix 1
  • All Products

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

Release Guide

Release Guide

Back Next

DBMOVER Configuration File Statements

DBMOVER Configuration File Statements

The DBMOVER configuration file includes the following new and changed statements:
ADABAS_MU_SEARCH={Y|
N
}
New
. Enables PowerExchange to include Adabas multiple-value fields in SQL search and selection operations. A multiple-value field is a single field that occurs a variable number of times in a record. It appears as type MU in an Adabas record description. Valid values are:
  • Y
    . PowerExchange uses multiple-value Adabas descriptor fields in searches. If you specify a multiple-value field in a WHERE clause of an SQL SELECT statement, PowerExchange scans the field for values specified in the search.
  • N
    . PowerExchange will not include Adabas multiple-value fields in searches.
Default is N.
If you set the ADABAS_MU_SEARCH statement to Y, make sure that the ADAOPT statement is also set to Y to use L3 commands to read records from file in logical sequence by descriptor value.
AS4J CAPI_CONNECTION
In this statement, you can specify the following parameter with the new P option:
LIBASUSER={
N
|Y|M|P}
Changed
. Specify the P option if you want PowerExchange to write the name of the program that made a DML change to the DTL__CAPXUSER field of the change record.
The default value of N is retained.
CAPX CAPI_CONNECTION
This statement can now contain the following optional parameter:
VALIDATEREGS={
N
|Y}
New
. Controls whether the PowerExchange extraction of data from PowerExchange Logger for Linux, UNIX, and Windows ends or continues if it detects a source entry in the CDC interest list for which the PowerExchange Logger is
not
 capturing change data. In this situation, the extraction process issues message PWX-36947, either as error message or informational message.
Options are:
  • Y
    . The PowerExchange Logger extraction process issues message PWX-36947 as an error message and then ends.
  • N
    . The PowerExchange Logger extraction process issues message PWX-36947 as an informational message and continues processing.
Default is N.
CMDNODE
Changed
. You can now use the CMDNODE statement to collect capture statistics for a PowerExchange Adabas, IDMS, or IMS log-based ECCR or Datacom table-based ECCR on z/OS. Use the following parameters:
  • Changed
    . Set the
    service_name
     parameter to the ECCR name. The ECCR name must match the ECCR specified on the corresponding SVCNODE statement.
  • New
    . Specify the ECCR option instead of CONDENSE or LISTENER.
LRAP CAPI_CONNECTION
This statement can now contain the following new optional parameter:
FUZZYRSTART={
Y
|N}
New
. Controls whether the restart2 token in the restart information that the PowerExchange Client for PowerCenter sends to the PowerExchange Logger for z/OS for a CDC session points to a
begin-uow
 record or any RBA position that you specify in the restart2 token.
This parameter also pertains to the Restart Token 2 value that you specify for PowerExchange Navigator CAPX and CAPXRT database row tests.
Options are:
  • Y
    . Allow the restart2 token to point to any RBA position in the PowerExchange Logger logged data. This option enables you to skip a problematic record.
  • N
    . Require the restart2 token to point to a begin-uow record in the PowerExchange Logger logged data.
Default is Y.
In previous PowerExchange releases, the default behavior was to always point to a begin-uow record. You can reinstate this behavior by specifying FUZZYRSTART=N.
MYSQL CAPI_CONNECTION
New
. This statement is required to capture change data from MySQL source tables. For more information about the syntax and parameters, see DBMOVER Configuration File.
NODE
Changed
.You can now specify whether SSL client certificate validation is required by using a trailing Y|N parameter at the end of the statement. Default is Y.
SVCNODE
Changed
. You can now specify an ECCR name in the
service_name
 parameter. The ECCR name must match the ECCR that is specified in the corresponding CMDNODE statement.
UOWC CAPI_CONNECTION
This statement can now contain the following optional parameter:
CUOWS=
number_of_concurrent_UOWs
New
. The expected number of concurrent UOWs that contain data of CDC interest. If you specified a large MEMCACHE value, have excessive spill file allocations, and a large number of concurrent UOWs reported in message PWX-10742 or PWX-10782, increase this parameter value to cause less memory cache to be used per UOW. By reducing memory cache use per UOW, more concurrent UOWs can be accommodated without allocating spill files. This parameter in no way restricts the maximum number of concurrent UOWs that the UOW Cleanser can process.
Valid values are 1 through 65535. Default is 34.
For more information, see the
PowerExchange Reference Manual
.
0 COMMENTS
We’d like to hear from you!