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
DTLINFOX - Enhanced Release Information Utility
- DTLINFOX Utility Overview
- Supported Operating Systems for the DTLINFOX Utility
- Control Statement Syntax for the DTLINFOX Utility
- DTLINFOX Utility Parameters
- Running the DTLINFOX Utility
- Reporting on Remote Programs by Using a PowerExchange Listener Task
- DTLINFOX Utility Examples
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
EDMUOPTS - Service Aid Utility
- EDMUOPTS Utility Overview
- Supported Operating System for the EDMUOPTS Utility
- EDMUOPTS Utility Reports
- Running the EDMUOPTS Utility
  - EDMUOPTS Utility Example JCL
  - Example EDMSDIR and EDMUPARM Reports
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 Utility
- PWXUCREG Utility Overview
- Supported Operating Systems for the PWXUCREG Utility
- Registration Statuses
- Deleting Registrations That Are No Longer Active
- Displaying Registration Summary Information
- Suspending Change Data Capture by z/OS ECCRs
  - PWXUCREG Usage Considerations
  - Suspending Change Capture for Registered Sources Temporarily
- General Syntax for PWXUCREG Commands
- PWXUCREG Commands and Parameters
- Running the PWXUCREG Utility
- Examples of PWXUCREG Utility Commands
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
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 PWXUCRGP 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
- PWXUGSK Utility Overview
- Supported Operating Systems for the PWXUGSK Utility
- PWXUGSK Control Statement Syntax
- PWXUGSK Commands and Parameters for IBM i
- PWXUGSK Commands and Parameters for z/OS
- Running the PWXUGSK Utility on IBM i
- Running the PWXUGSK Utility on z/OS
- PWXUGSK Utility Reports
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
WRKJRNLCKE- Journal Lock Table Utility for IBM i
- WRKJRNLCKE Utility Overview
- Supported Operating Systems for the WRKJRNLCKE Utility
- WRKJRNLCKE Utility Command Syntax
- Running the WRKJRNLCKE Utility on IBM i
- WRKJRNLCKE Usage Considerations

Utilities Guide

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

Back Next

DTLUCBRG Utility Source-Specific Parameters

For Adabas, IMS, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, SAP HANA, and VSAM data sources, the DTLCUBRG utility requires additional information to update registrations. Provide this information in the source-specific parameters.

These parameters have names that begin with the DBTYPE value and end with a suffix of OPTS. Each one has one or more subparameters.

The following list describes the source-specific parameters and subparameters:

ADAOPTS

Specifies parameters for Adabas sources. To use these parameters, the DBTYPE parameter must be set to ADA in the input parameter file. Otherwise, the utility issues an error message.

Syntax:

ADAOPTS=(FileNo=file number,DBID=dbid)

Subparameters:

FileNo: Required. The Adabas file number. No default is provided.
DBID: Required. The Adabas DBID. No default is provided.

HANOPTS

Specifies parameters for SAP HANA sources. To use these parameters, the DBTYPE parameter must be set to HAN in the input parameter file. Otherwise, the DTLUCBRG utility issues an error message.

Syntax:

HANOPTS=(DBSERVER=database_server,[FULLAUDIT={Y|N}],DDLFILE=path\schema.tablename.sql)

Subparameters:

DBSERVER: Required. The name of the database server. You can optionally include a port number for the server in the following format:
DBSERVER="database_server,port_number"

In this case, the double-quotation marks are required.

No default is provided.
DBNAME: Required. The name of the database that contains the tables from which changes are captured. Default is From Datamap.
DDLFILE: Optional. Specifies the path and file name of an SQL file that can be used to create triggers for registered tables. If you specfiy FULLAUDIT=Y, the file also includes the SQL to create the full-audit shadow tables. If you include the DDLFILE parameter, set the TESTRUN parameter to Y to prevent the utility from creating or updating registrations.
If the parameter value includes spaces, do not use quotes to delimit the path and file name. If you specify only a path, the utility returns an error.

If you use a wildcard to specify multiple registrations, the DDL file contains statements for all registrations that conform to the wildcard pattern.

The DDLFILE parameter has the following format:

DDFILE=path\schema.tablename.sql
FULLAUDIT: Optional. indicates whether the utility processes the change data with full audit enabled. The full audit feature creates a shadow table for changes to the SAP HANA table for which it is enabled.
If STATUS is set to Y, full audit is enabled.
If STATUS is set to N, full audit is disabled.

Default is N.

IMSOPTS

Specifies parameters for IMS sources. To use these parameters, the DBTYPE parameter must be set to IMS in the input parameter file. Otherwise, the utility issues an error message.

Syntax:

IMSOPTS=([TYPE={SYN|LOG}][,DBDNAME=DBD_name][,IMSID=subsystem_id][, PRIMDSN=dataset_name])

Subparameters:

TYPE: Optional. The type of PowerExchange IMS CDC processing that you use. Options are:
SYN
for IMS synchronous CDC.
LOG
for IMS log-based CDC.

Default is SYN.
DBDNAME: Optional. The database name from the DBD. Default is From Datamap.
IMSID: Optional. The IMS subsystem ID, which matches the value in the IMSID statement in the DBMOVER member of the RUNLIB library. No default is provided.
PRIMDSN: Optional. The primary data set name. No default is provided.

MSSOPTS

Specifies parameters for Microsoft SQL Server sources. To use these parameters, the DBTYPE parameter must be set to MSS in the input parameter file. Otherwise, the DTLUCBRG utility issues an error message.

Syntax:

MSSOPTS=(DBSERVER=database_server,DBNAME=database_name,[UPDATESTATUS={Y|N}])

Subparameters:

DBSERVER: Required. The name of the database server. You can optionally include a port number for the server in the following format:
DBSERVER="database_server,port_number"

In this case, the double-quotation marks are required.

No default is provided.
DBNAME: Required. The name of the database that contains the tables from which changes are captured. Default is From Datamap.
UPDATESTATUS: Optional. indicates whether the utility can change the status of multiple registrations in one operation and delete and rebuild the associated publications. Use this parameter when you need to switch the status of many registrations at one time, or when you need to make DDL changes to many source tables and do not want to manually re-create the registrations and regenerate the publications.
If you specify UPDATESTATUS=Y, the utility performs the following actions, depending on the STATUS setting:

If STATUS is set to I, the active registrations that you select are set to inactive and the associated publications are deleted.
If STATUS is set to A, the inactive registrations that you select are set to active and the associated publications are automatically rebuilt based on the existing registrations.

You can filter the registrations for the utility to process by specifying the CONDTYPE, TABLE, and CRGNAME or CRGPREFIX parameters.

Default is N.

MYSOPTS

Specifies a parameter for MySQL sources. To use this parameter, the DBTYPE parameter must be set to MYS in the input parameter file. Otherwise, the utility issues an error message.

Syntax:

MYSOPTS=(DBSERVER="{database_server_name|localhost}[{,port_number|3306}]")

Subparameter:

DBSERVER: Required. Enter the server name or IP address of the MySQL server where the source database is located. If the MySQL server is on the local host where the DTLUCBRG utility runs, you can enter
localhost
. Optionally, you can append the port number if you use a port other than the default port of 3306, for example,
DBSERVER="localhost,3456"
.

ORAOPTS

Specifies a parameter for Oracle sources. To use this parameter, the DBTYPE parameter must be set to ORA in the input parameter file. Otherwise, the utility issues an error message.

Syntax:

ORAOPTS=(DDLFILE=[path][file_name])

Subparameter:

DDFILE: Required. The name of the file that stores ALTER DDL statements for supplemental log groups. You can specify the file name only or the full path and file name, for example,
oraopts.sql
or
c:\sql\oraopts.sql
. Alternatively, you can enter the subparameter with a blank value,
DDFILE=
, to use the default file name and directory.
If the parameter value includes spaces, do not use quotes to delimit the path and file name. If you specify only a path, the utility returns an error.

If you use a wildcard to specify multiple registrations, the DDL file contains statements for all registrations that conform to the wildcard pattern.

Default value is dtlucbrg_ora.sql.

PGSOPTS

Specifies parameters for PostgreSQL sources. To use these parameters, the DBTYPE must be set to PGS in the input parameter file. Otherwise, the DTLUCBRG utility issues an error message.

Syntax:

PGSOPTS=(DBSERVER=database_server,DBNAME=database_name)

Subparameters:

DBSERVER: Required. The name of the database server. You can optionally include a port number for the server in the following format:
DBSERVER="database_server,port_number"

In this case, the double-quotation marks are required.

No default is provided.
DBNAME: Required. The name of the database that contains the tables from which changes are captured.

VSMOPTS

Specifies a parameter for VSAM sources. To use this parameter, the DBTYPE parameter must be set to VSM in the input file. Otherwise, the utility issues an error message.

Syntax: