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

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMUOPTS - Service Aid Utility
  18. EDMXLUTL - Event Marker Utility
  19. HOSTENT - TCP/IP Address Reporter Utility
  20. PWXCATMY - MySQL Catalog Utility
  21. PWXUCCLPRT - Print Log Summary Utility
  22. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  23. PWXUCREG - Capture Registration Suspend Utility
  24. PWXUCRGP - Capture Registrations Print Utility
  25. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  26. PWXUGSK - SSL Reporting Utility for z/OS
  27. PWXUMAP - Map List Utility
  28. PWXUSSL - PowerExchange SSL Reporting Utility

Utilities Guide

Utilities Guide

Back Next

ADD and MOD Statements

ADD and MOD Statements

Use the ADD and Mode statements to generate or specify restart tokens for ODBC or PWXPC extractions. You can also use these statements to add or modify applications and the capture registrations associated with an application. For example, if you create a new capture registration, you can modify an existing application to include it.
For ODBC extractions, the utility updates application and registration information in the CDEP file based on the ADD and MOD statements.
The information in the CDEP file does not apply to PWXPC extractions.
You can configure the ADD and MOD statement statements to generate restart tokens at the application level or registration level or to add the sequence and restart tokens that you specify for a capture registration in these statements to the CDEP file.
To generate restart tokens, use the RSTTKN GENERATE keyword at the application level or the GENERATE keyword at the registration level. Restart tokens generated at the registration level override those generated at the application level. Restart tokens generated at the application level apply to any capture registrations in ADD or MOD RSTTKN statements that do not include a GENERATE parameter or specific SEQUENCE and RESTART values.
If you use ODBC extractions, PowerExchange maintains restart tokens for each registration associated with an application in the CDEP file.
If you use PWXPC extractions, PWXPC maintains the restart tokens in the state table for a relational target database on the target or in the state file for a nonrelational target on the Integration Service machine. For more information about PWXPC and restart token management, see
PowerExchange Interfaces for PowerCenter
.
When you define ADD or MOD statements, use the following rules and guidelines:
  • To add a new application, use the ADD APPL and ADD RSTTKN statements.
  • To modify an existing application, use the MOD APPL statement.
  • To add or modify an existing capture registration for an existing application, use the MOD RSTTKN statement.
  • If you attempt to add an application that already exists, DTLUAPPL produces an error.
  • The ADD or MOD APPL statement must always end with an END APPL statement.
  • For PWXPC extractions, do not use the application name that is specified in the PWXPC application connection for generating restart tokens.
application_name
Specifies the name of the application to be added or modified. This value is case sensitive.
instance
Specifies the source instance. Ensure that this value matches the instance value that is displayed in the PowerExchange Navigator for the registration group and extraction group. The type of value varies by data source type.
The following table identifies the instance value type for each source type:
Data Source
Instance Value
Adabas
The DBID value.
Datacom
The MUF Name value that is specified for the registration group.
Db2 for i (i5/OS)
The DBID value in the CAPTPARM member of the CFG file.
Db2 on Linux, UNIX, or Windows (Db2 LUW)
The database name that is specified for the registration group.
Db2 for z/OS
The Db2 subsystem ID.
IDMS
The CV name.
IMS
The IMS system identifier.
Microsoft SQL Server
The instance value that is specified for the registration group
MySQL
The instance value that is specified for the registration group.
Oracle
The
collection_identifier
 value that is specified in the ORACLEID statement in the DBMOVER configuration file.
PostgreSQL
The instance value that is specified for the registration group
VSAM
The instance value that is specified for the registration group.
Values from the registration group definition are in all uppercase. Use the same case when specifying the values in this parameter.
RSTTKN GENERATE
Generates restart tokens that mark the current end of the change stream at the application level. The generated restart tokens apply to the capture registrations associated with application for which restart tokens are not generated at the registration level or specifically defined in SEQUENCE and RESTART keywords.
CAPTMETH=
access_method
Specifies one of the following capture access methods:
  • CAPXRT
    . For real-time or continuous extraction mode.
  • CAPX
    . For batch extraction mode.
    Valid only for the following CDC sources: Db2 LUW, Oracle, Microsoft SQL Server, MySQL, and PostgreSQL.
CONDTYPE={P|F}
Specifies the condense type for which DTLUAPPL generates restart tokens.
Enter one of the following options:
  • P
    . Partial condense processing by the PowerExchange Logger for Linux, UNIX, or Windows or by PowerExchange Condense on i5/OS or z/OS. Valid for all source types.
  • F
    . Full condense processing by PowerExchange Condense on i5/OS and z/OS. Valid for Datacom, DB2 for z/OS, and VSAM sources on z/OS that specify key columns. Also valid for DB2 for i5/OS tables that have primary keys and DDS files that are defined with a unique key.
No default.
JRN=
library
/
journal
Overrides the Db2 for i journal that is specified in the capture registration.
Valid for Db2 for i CDC only.
ORACOLL=
collection_id
Overrides the collection identifier that is recorded for the capture registration in the CCT file.
Valid for Oracle CDC only.
ORACONN=
source_connect_string
Overrides the Oracle connection information for a specific Oracle collection ID, which is specified as the third positional parameter in the ORACLEID statement in the dbmover.cfg configuration file. By using this override in conjunction with ORAINST, you can use a single set of capture registrations to capture data from multiple Oracle instances.
You can specify ORACONN or ORAINST or both. If one of these parameter values is not specified, PowerExchange uses the parameter value from the ORACLEID statement in dbmover.cfg configuration file for the missing parameter.
Valid for Oracle CDC only.
ORAINST=
instance
Overrides the Oracle instance name for a specific Oracle collection ID, which is specified as the second positional parameter in the ORACLEID statement in the dbmover.cfg configuration file. By using this override in conjunction with ORACONN, you can use a single set of capture registrations to capture data from multiple Oracle instances.
Valid for Oracle CDC only.
ORASCHEMA=
schema
Overrides the Oracle schema name that is specified for the registration group. By using this override, you can use of a single set of capture registrations to capture data from multiple schemas in an Oracle instance.
Valid for Oracle CDC only.
UDBDB=
database
Specifies the connection database when it is different from the registration database.
Valid for Db2 LUW CDC only.
{ADD|MOD} RSTTKN
registration_name
 [DB=
library
/
table
} [GENERATE]
Adds a capture registration to an application or generates restart tokens at the registration-level.
registration_name
Specifies the name of the capture registration. This value is case sensitive.
DB=
library
/
table
Overrides the Db2 table that is specified in the capture registration.
Valid for Db2 for i CDC only.
GENERATE
Generates restart tokens that mark the current end of the change stream for the capture registration.
0 COMMENTS
We’d like to hear from you!