Preface
Introduction to PowerExchange Utilities
- PowerExchange Utilities Overview
- PowerExchange Utilities by Operating System
- PowerExchange Utilities Syntax Conventions
- Environment Variable Incompatibilities Between PowerExchange and PowerCenter
  - Setting the PowerExchange Environment and Starting a Utility
- PowerExchange Sample JCL
createdatamaps - Data Map Creation Utility
- createdatamaps Utility Overview
- Requirements and Considerations for COBOL Copybooks and DBDs
- createdatamaps Command Syntax
- Creating, Editing, and Testing a Data Map
- Control Files for Data Map Generation
  - Rules for Control Files
  - Control File Structure
- Schema File for Describing Control Files
- Schema File Reference
- Log File for Data Maps Creation Utility
  - JAXB Error Messages
- Redefinitions and Record IDs in COBOL Copybooks
- Copybook and DBD Metadata for IMS Data Maps
- Column Name Filters
- Unavailable Data Map Properties
- Examples
DTLCCADW - Adabas PCAT Utility
- DTLCCADW Utility Overview
- DTLCCADW Utility Functions
DTLCUIML - IMS Log Marker Utility
- DTLCUIML Utility Overview
- DTLCUIML Utility Parameters
- DTLCUIML Utility Reports
DTLINFO - Release Information Utility
- DTLINFO Utility Overview
- Supported Operating Systems for the DTLINFO Utility
- Control Statement Syntax for the DTLINFO Utility
- Control Statement Parameters for the DTLINFO Utility
- Running the DTLINFO Utility on i5/OS
- Running the DTLINFO Utility on Linux, UNIX, and Windows
- Running the DTLINFO Utility on z/OS
- DTLINFO Utility on i5/OS Examples
  - DTLINFO Utility on i5/OS - Example 1
  - DTLINFO Utility on i5/OS - Example 2
- DTLINFO Utility on Linux, UNIX, and Windows Examples
  - DTLINFO Utility on Linux, UNIX, and Windows - Example 1
  - DTLINFO Utility on Linux, UNIX, and Windows - Example 2
- DTLINFO Utility on z/OS Examples
  - DTLINFO Utility on z/OS - Example 1
  - DTLINFO Utility on z/OS - Example 2
DTLREXE - Remote Execution Utility
- DTLREXE Utility Overview
- Supported Operating Systems for the DTLREXE Utility
- Control Statement Syntax for the DTLREXE Utility
- Control Statement Parameters for the DTLREXE Utility
- Running the DTLREXE Utility on i5/OS
- Running the DTLREXE Utility on Linux and UNIX
- Running the DTLREXE Utility on Windows
- Running the DTLREXE Utility on z/OS
- DTLREXE Utility Usage Notes
- DTLREXE Utility on z/OS Example
  - DTLREXE Utility on z/OS Example JCL
  - DTLREXE Utility on z/OS Output Data Set
DTLUAPPL - Restart Token Utility
- DTLUAPPL Utility Overview
- Supported Operating Systems for the DTLUAPPL Utility
- DTLUAPPL Control Statement Syntax
- Connection Statement
- ADD and MOD Statements
- END APPL Statement
- PRINT APPL Statement
- Running the DTLUAPPL Utility on i5/OS
- Running the DTLUAPPL Utility on Linux, UNIX, and Windows
- Running the DTLUAPPL Utility on z/OS
- DTLUAPPL Utility Examples
DTLUCBRG - Batch Registration Utility
- DTLUCBRG Utility Overview
- Supported Operating Systems for the DTLUCBRG Utility
- DTLUCBRG Utility Parameters
- DTLUCBRG Code Page Processing
  - Code Page Processing for DB2 Registrations in Local Mode on z/OS
- Running the DTLUCBRG Utility
- DTLUCBRG Utility Example Reports
  - DTLUCBRG Utility with RPTCOLS=N Report Description
  - DTLUCBRG Utility with RPTCOLS=Y Report Description
- DTLUCBRG Utility Usage Notes
DTLUCDEP - CDEP Maintenance Utility
- DTLUCDEP Utility Overview
- Supported Operating Systems for the DTLUCDEP Utility
- Control Statement Syntax for the DTLUCDEP Utility
- Control Statement Parameters for the DTLUCDEP Utility
  - CDEP Definition Examples
- Running the DTLUCDEP Utility on i5/OS
- Running the DTLUCDEP Utility on Linux, UNIX, and Windows
- Running the DTLUCDEP Utility on z/OS
- DTLUCDEP Utility on i5/OS Example
- DTLUCDEP Utility on Linux, UNIX, and Windows Example
- DTLUCDEP Utility on z/OS Example
DTLUCSR2 - IDMS SR2 and SR3 Records Utility
- DTLUCSR2 Utility Overview
- Running the DTLUCSR2 Utility
DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
- DTLUCUDB Utility Overview
- Running the DTLUCUDB Utility
  - DTLUCUDB Utility Syntax
  - Command Options for the DTLUCUDB Utility
- Gathering Diagnostic Information to Resolve a DB2 Capture Problem
DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
- DTLULCAT and DTLULOGC Utilities Overview
- Running the DTLULCAT Utility
- Running the DTLULOGC Utility
- Manually Manipulating the Log Catalog
- Guidelines for Adding Logs to the Catalog with the DTLULCAT and DTLULOGC Utilities
DTLURDMO - Data Map Utility
- DTLURDMO Utility Overview
- Supported Operating Systems for the DTLURDMO Utility
- Control Statement Overview for the DTLURDMO Utility
- Control Statement Syntax for the DTLURDMO Utility
- Control Statements and Parameters for the DTLURDMO Utility
- Scope of Operands
- Running the DTLURDMO Utility on i5/OS
- Running the DTLURDMO Utility on Linux, UNIX, and Windows
- Running the DTLURDMO Utility on z/OS
- DTLURDMO Control Statement Examples
- DTLURDMO Report Examples
DTLUTSK - Task Control Utility
- DTLUTSK Utility Overview
- DTLUTSK Command Line Utility on i5/OS
- DTLUTSK Command Line Utility on Linux, UNIX, and Windows
  - Displaying DTLUTSK Utility Help
- DTLUTSK Job on z/OS
  - Example JCL for a DTLUTSK Job on z/OS
  - Example Output from a DTLUTSK Job on z/OS
- DTLUTSK Command Line Utility on z/OS
- Running the DTLUTSK Utility in the PowerExchange Navigator
- DTLUTSK Utility Security
EDMLUCTR - Log Scan and Print Utility
- EDMLUCTR Utility Overview
- Supported Operating Systems for the EDMLUCTR Utility
- Control Statement Syntax for the EDMLUCTR Utility
- Control Statement Parameters for the EDMLUCTR Utility
  - -SEL Statement
  - -MASK Statement
- Running the EDMLUCTR Utility
- EDMLUCTR Utility Usage Notes
- EDMLUCTR Utility Examples
EDMXLUTL - Event Marker Utility
- EDMXLUTL Utility Overview
- Creating an Event Marker in Batch Mode
- EDMXLUTL Utility JCL Statements
- EDMXLUTL Utility Control Statements
- EDMXLUTL Utility EVENT Command
  - EVENT Command Syntax
  - EVENT Command Usage
- Keyword Sets for the BASEEDM Category
  - MARK Keyword Set
  - NOTIFY Keyword Set
- EDMXLUTL Utility Example
HOSTENT - TCP/IP Address Reporter Utility
- HOSTENT Utility Overview
- Supported Operating Systems for the HOSTENT Utility
- Running the HOSTENT Utility on i5/OS
- Running the HOSTENT Utility on Linux and UNIX
- Running the HOSTENT Utility on z/OS
- HOSTENT Utility Usage Notes
  - HOSTENT Utility Resolver Details
- HOSTENT Utility Output
- HOSTENT Utility on i5/OS Example
- HOSTENT Utility on Linux and UNIX Example
- HOSTENT Utility on z/OS Example
PWXCATMY - MySQL Catalog Utility
- PWXCATMY Utility Overview
- Supported Operating Systems for the PWXCATMY Utility
- PWXCATMY Operation Types
- Command Syntax and Parameters
PWXUCCLPRT - Print Log Summary Utility
- PWXUCCLPRT Utility Overview
- Supported Operating Systems for the PWXUCCLPRT Utility
- Command Syntax for the PWXUCCLPRT Utility
- PWXUCCLPRT Utility Parameters
  - PWXUCCLPRT INPUT Statement Parameters
  - PWXUCCLPRT OUTPUT Statement Parameters
- Example PWXUCCLPRT Parameter File
- Examples of PWXUCCLPRT Output
PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
- PWXUCDCT Utility Overview
- Supported Operating Systems for the PWXUCDCT Utility
- Control Statement Syntax for PWXUCDCT Commands
- PWXUCDCT Commands and Parameters
  - Commands
  - Parameter Descriptions
- Running the PWXUCDCT Utility
- Usage Notes for the PWXUCDCT Utility
- Examples of PWXUCDCT Utility Commands
PWXUCREG - Capture Registration Suspend Utility
- PWXUCREG Utility Overview
- PWXUCREG Usage Considerations
- Supported Operating Systems for the PWXUCREG Utility
- Suspending Change Capture for Registered Sources Temporarily
- General Syntax for PWXUCREG Commands
- Summary of PWXUCREG Commands
- Global SET_CONTROL_VALUE Parameters
- Registration-specific Command Parameters
- Running the PWXUCREG Utility
- Examples of PWXUCREG Utility Commands
  - Example 1. Suspending a Capture Registration
  - Example 2. Reactivating a Capture Registration
PWXUCRGP - Capture Registrations Print Utility
- PWXUCRGP Utility Overview
- Supported Operating Systems for the PWXUCRGP Utility
- Control Statement Syntax for the PWXUCRGP Utility
- PWXUCRGP Parameters
- Running the PWXUCRGP Utility
- PWXUCRGP Report Levels of Detail
- Examples of PWXUCGRP Reports
PWXUDMX - Data Maps Update Time ECSA Memory Utility
- PWXUDMX Utility Overview
- Supported Operating Systems for the PWXUDMX Utility
- Running the PWXUDMX Utility on z/OS
- PWXUDMX Commands and Parameters
PWXUGSK - SSL Reporting Utility for z/OS
- PWXUGSK Utility Overview
- Supported Operating Systems for the PWXUGSK Utility
- PWXUGSK Control Statement Syntax
- PWXUGSK Commands and Parameters
- Running the PWXUGSK Utility
- PWXUGSK Utility Reports
PWXUMAP - Map List Utility
- PWXUMAP Utility Overview
- Supported Operating Systems for the PWXUMAP Utility
- General Syntax for the PWXUMAP Utility
- PWXUMAP Commands and Parameters
- Running the PWXUMAP Utility
- Examples of PWXUMAP Reports
- PWXUMAP Utility Usage Notes
PWXUSSL - PowerExchange SSL Reporting Utility
- PWXUSSL Utility Overview
- Supported Operating Systems for the PWXUSSL Utility
- Control Statement Syntax for PWXUSSL Commands
- PWXUSSL Commands and Parameters
- Running the PWXUSSL Utility
- PWXUSSL Utility Reports

Utilities Guide

10.4.0
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1

Back Next

PWXUCRGP Parameters

The utility supports the following parameters:

OUTPUT_FILE=file_name: Required. The name of the output file for the report, such as
my_registrations.txt
. The output file is a standard text file on the local Linux, UNIX, or Windows machine. The target location for the output file cannot be on i5/OS or z/OS.
LOCATION={node_name| local }: The location of the CCT file that contains the registration information. You can specify
local
if the CCT file is on the machine where the utility runs, or you can specify the node name of a remote machine where a PowerExchange Listener runs. If the location is a remote Listener node, and the SECURITY parameter in the DBMOVER configuration file is set to level 1 or 2, a user ID and either a password or an encrypted password are required.
Default is
local
.
OVERRIDE_CCT_FILE=file_name: The name of the CCT file that contains the registration information, if different than the current CCT file for the PowerExchange Listener specified in the LOCATION parameter. For example, if you use the DTLURDMO utility to copy registrations to a specific CCT file name, you can use this parameter to report information from that file.
UID=user_name: A user name that allows access to the remote PowerExchange Listener that is identified by the LOCATION parameter. The requirement for the user name depends the value of the SECURITY statement in the PowerExchange DBMOVER configuration file associated with the remote Listener.
For a source on a supported Linux, UNIX, and Windows system, if you enabled PowerExchange LDAP user authentication and, if applicable, disabled relational pass-through authentication, the user name is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.
EPWD=encrypted_password: An encrypted password for the user who is specified in the UID parameter.
If the utility accesses a remote i5/OS or z/OS location, you can enter an encrypted PowerExchange passphrase instead of an encrypted password. Do not encrypt a passphrase that contains invalid characters, such as double-quotation marks, single quotation marks, or currency symbols.
Do not specify both the EPWD and PWD parameters. Use EPWD if you are not allowed to store passwords in a readable format.
PWD=password: A clear-text password for the user who is specified in the UID parameter. If the utility accesses a remote i5/OS or z/OS location, you can enter a valid PowerExchange passphrase instead of a password.
Do not specify both the PWD and EPWD parameters .
CRNAME=registration_name: The registration name that is used to filter the registrations that are included in the report. The name can be up to eight lowercase characters and can include a trailing asterisk if multiple registration names use the same format. For example, you can specify int2* to include the registration names int2a, int2b, and int2c. The registration name can be user defined when a capture registration is added in the PowerExchange Navigator or generated by the DTLUCBRG utility.
DBTYPE=database_type: A three-character keyword for the source database type. This value is used to filter registrations for which the utility reports information. Options are:
Asterisk (*) wildcard only, for all supported types of databases
ADA
for Adabas
AS4
for DB2 for i (i5/OS)
DB2
for DB2 for z/OS
DCM
for Datacom.
IDM
for log-based IDMS
IMS
for IMS
MSS
for Microsoft SQL Server
MYS
for MySQL
ORA
for Oracle
PGS
for PostgreSQL
UDB
for DB2 for Linux, UNIX, and Windows
VSM
for VSAM
Default is the asterisk (
*
) wildcard.
Use DB2
only for DB2 for z/OS.
INSTANCE=instance_name: An instance name for the specified database type. If you specify the DBTYPE parameter, you can use the INSTANCE parameter to further filter the registrations for which information is reported to a specific instance_name.
REPORT_LEVEL={ SINGLELINE |SUMMARY|COLUMNS}: The level of detail to include in the report. Options are:
SINGLELINE
. Reports a single line of information for each capture registration that is included in the report. This information is also included in the SUMMARY and COLUMNS report outputs. For more information, see Single-Line Report Content.
SUMMARY
. Reports summary information about each capture registration in the report. A SUMMARY report includes the same information as a SINGLELINE report and additionally includes the user name associated with the registration group, the most recent update date, the PowerExchange version of the system that updated the registration, edit sequence, registration type, and data columns. For more information, see Summary Report Content.
COLUMNS
. Reports information about each column in the capture registration. A COLUMN report includes the same information as a SUMMARY report and additionally includes detailed information about each column in the capture registration. For more information, see Column-Level Report Content.
Default is SINGLELINE. For more information, see PWXUCRGP Report Levels of Detail.
REPORT_SEQUENCE={ TAG |TABLE|CRNAME}: A secondary level of sorting information in the report. Each report is sorted first by database type and instance and then by the criterion in this parameter. Options are:
TAG
. Sort by registration tag name.
TABLE
. Sort by schema and table name.
CRNAME
. Sort by CRNAME.
Default is
TAG
.
STATUS=registration_status: A registration status to use for filtering the capture registrations for which to report information. Options are:
Asterisk (*) wildcard only. Include capture registrations of all statuses.
A
. Include only capture registrations with an Active status.
H
. Include only capture registrations with a History status.
I
. Include only capture registrations with an Inactive status.
S
. Include only capture registrations with a Suspended status.
Default is asterisk (*
).
TRACING={Y| N }: Turns on the UCRGP trace filter for the utility without having to edit the TRACING statement in the PowerExchange DBMOVER configuration file. Options are:
Y
. Run the trace filter for the utility.
N
. Do not run the trace filter for the utility.
Default is
N
. Set TRACING=Y only at the direction of Informatica Global Customer Support.

Rename Saved Search

Table of Contents

Utilities Guide

Utilities Guide

PWXUCRGP Parameters

PWXUCRGP Parameters