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. 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. DTLINFOX - Enhanced Release Information Utility
  8. DTLREXE - Remote Execution Utility
  9. DTLUAPPL - Restart Token Utility
  10. DTLUCBRG - Batch Registration Utility
  11. DTLUCDEP - CDEP Maintenance Utility
  12. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  13. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  14. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  15. DTLURDMO - Data Map Utility
  16. DTLUTSK - Task Control Utility
  17. EDMLUCTR - Log Scan and Print Utility
  18. EDMUOPTS - Service Aid Utility
  19. EDMXLUTL - Event Marker Utility
  20. HOSTENT - TCP/IP Address Reporter Utility
  21. PWXCATMY - MySQL Catalog Utility
  22. PWXUCCLPRT - Print Log Summary Utility
  23. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  24. PWXUCREG - Capture Registration Utility
  25. PWXUMAP - Map List Utility
  26. PWXUCRGP - Capture Registrations Print Utility
  27. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  28. PWXUGSK - SSL Reporting Utility
  29. PWXUSSL - PowerExchange SSL Reporting Utility
  30. WRKJRNLCKE- Journal Lock Table Utility for IBM i

Utilities Guide

Utilities Guide

Back Next

Common Parameters for Registration-specific Commands

Common Parameters for Registration-specific Commands

Common parameters are grouped into the following categories:
  • Connectivity parameters that specify the location of the CCT file and credentials to use when accessing the file
  • Registration filter parameters that specify the database type, instance identifier, registration name, status, and versions of registrations to be processed
  • Other parameters such as GENERIC or VALIDATE that specify whether more than one registration will be processed, whether registrations are modified, whether attributes are displayed.
In the following parameter descriptions, curly brackets {} indicate that one of the options must be entered and underlining indicates the default value.

Connectivity Parameters

If several registration-specific commands run in the same command set, you can specify the following optional connectivity parameters globally in the SET_CONTROL_VALUE command instead of in the registration-specific command.
EPWD=
encrypted_password
Specifies an encrypted password to use with the user ID that is specified in the associated USER parameter.
Overrides the GLOBAL_EPWD parameter in a preceding SET_CONTROL_VALUE command, if specified. For more information, see Global SET_CONTROL_VALUE Command and Parameters.
PWD=
password
Specifies a nonencrypted password to use with the user ID that is specified in the associated GLOBAL_USER parameter. This value is case-sensitive.
Overrides the GLOBAL_PWD parameter in a preceding SET_CONTROL_VALUE command, if specified. For more information, see Global SET_CONTROL_VALUE Command and Parameters.
REGISTRATION_LOCATION={
hlq.data_set_name
|
local
}
Specifies the location of the CCT file that contains the capture registrations. Default value is "local."
Overrides the GLOBAL_REGISTRATION_LOCATION parameter in a preceding SET_CONTROL_VALUE command, if specified. For more information, see Global SET_CONTROL_VALUE Command and Parameters.
USER=
user_id
Specifies a user ID that has the authority to access capture registrations in the CCT data set on the source system.
Overrides the GLOBAL_USER parameter in a preceding SET_CONTROL_VALUE command, if specified. For more information, see Global SET_CONTROL_VALUE Command and Parameters.

Registration Filter Parameters

Registration filter parameters apply to all commands except SET_CONTROL_VALUE. To filter the registrations, specify the following optional parameters.
DATABASE_TYPE=
type
Recommended. Specifies the type of source database and CDC method that is associated with the registration or registrations that the PWXUCREG command processes. Options are:
  • ADA
    . For Adabas.
  • AS4
    . For Db2 for i.
  • DB2
    . For Db2 for z/OS.
  • DCM
    . For Datacom table-based sources.
  • HAN
    . For SAP HANA on Linux, UNIX, or Windows.
  • IDL
    . For IDMS log-based sources.
  • IMS
    . For IMS log-based and synchronous sources on z/OS.
  • MSS
    . For Microsoft SQL Server on Windows.
  • MYS
    . For MySQL on Linux, UNIX, or Windows.
  • ORA
    . For Oracle on Linux, UNIX, or Windows.
  • PQS
    . For PostgreSQL on Linux, UNIX, or Windows.
  • UDB
    . For Db2 on Linux, UNIX, or Windows.
  • VSM
    . For VSAM on z/OS.
Default is the asterisk (*) wildcard, which means all database types are selected.
  • Only IMS log-based uses an ECCR and supports suspending and reactivating registrations.
  • If you try suspending and reactivating registrations for IMS synchronous sources, the PWXUCREG utility rejects the registrations and ends with error message PWX-03723.
  • You can suspend and reactivate only registrations that have a database type of ADA, DCM, IDL, or IMS (log-based).
  • All database types can be processed by the DELETE-INATIVE_REGIRATION and DISPLAY_REGISTRATION commands.
DATABASE_INSTANCE=
instance_id
Recommended. The source database identifier that was specified for the registration group that contains the registrations in the PowerExchange Navigator. The identifier varies by database type:
  • For Adabas: Use the Collection Identifier value.
  • For Datacom: Use a MUF name.
  • For IDMS: Use a LOGSID identifier.
  • For IMS: Use the RECON identifier.
You can use the asterisk (*) wildcard, or a string followed by the wildcard, in this parameter.
Default is an asterisk (*) wildcard, which means all instances are selected.
REGISTRATION_NAME=
user_registration_name
Required. Specifies the user-defined name for the registration.
You can use the asterisk (*) wildcard, or a string followed by the wildcard, in this parameter.
If you are processing a single registration with the GENERIC=N parameter, the registration name must be fully specified without a wildcard.
Default is the asterisk (*) wildcard, which selects all names.

Other Parameters

To suspend or re-activate registrations for multiple registrations or validate registrations, specify the following optional parameters.
GENERIC={
N
|Y}
Issue registration-specific parameters that suspend or re-activate registrations for multiple registrations. Options are:
  • Y
    . Commands to suspend or re-activate registrations can process multiple registrations. An asterisk (*) wildcard must be specified in a registration filter parameter including DATABASE_TYPE, DATABASE_INSTANCE, or REGISTRATION NAME.
  • N
    . Commands to suspend or re-activate registrations can process only one registration at a time.
Default is N.
Overrides the global GENERIC parameter in a preceding SET_CONTROL_VALUE command. For more information, see Global SET_CONTROL_VALUE Command and Parameters.
This parameter is not supported for the DELETE_INACTIVE_REGISTRATION and DISPLAY_REGISTRATION commands.
VALIDATE={
N
|Y}
Controls whether to validate the registrations.
  • Y
    . Validate the registrations. Perform processing for the command, except for modifying the registration.
  • N
    . Perform processing for the command and update registrations on the CCT file.
Default is N.
Overrides the GLOBAL_VALIDATE parameter in a preceding SET_CONTROL_VALUE command. For more information, see Global SET_CONTROL_VALUE Command and Parameters.
0 COMMENTS
We’d like to hear from you!