When you run the DTLUCBRG utility, you might receive error messages that imply the registrations that are being created might not be usable. For example:

PWX-09702  Oracle ID 
xxxx not found in configuration

Correct the error that the message reports and then re-run the utility. Repeat this process until the utility generates no error messages. It is particularly important to eliminate errors that result from the lookup of existing registrations, because these errors might result in unusable registrations even if no entries are found.
First attempt to create a small volume of registrations.
Include the following parameter in the utility input to perform a test run of the utility without creating the registrations:
TESTRUN Y
After you perform a test run without errors for a small volume of registrations, try the test run again for the complete set of registrations that you want to create. After this run completes without errors, specify TESTRUN N in the utility input and run the utility again to create the registrations. Default is TESTRUN Y.

For z/OS, specify a minimum REGION size of 64M to accommodate memory requirements for utility processing.

If you use the DTLUCBRG utility to create capture registrations for data sources on z/OS but the utility does not find the required source data maps in the DATAMAPS member on the LOCATION_DM node, the utility does not create the registrations and does not report the error. Instead, the utility appears to end successfully with RC=0. To avoid this problem, ensure that the data maps for the source objects exist in the DATAMAPS member before you run the utility.

In some cases, the DTLUCBRG utility might not generate the BI and CI columns even though the CREATEBICI parameter is specified. For example, the utility does not generate BI and CI columns for DB2 for z/OS LOB columns. In this case, the utility ignores the attempt to create the columns in the extraction map and writes a warning message to the output file.

If you use the DTLUCBRG utility with DB2 for i5/OS sources, you can specify either a flat physical file or source physical file in the INPUT_FN, OUTPUT_FN, or ERROR_FN keyword of the CREATEBICI parameter. These keywords point to input, output, and error files. If you want to specify a member within a file, enclose the entire file and member name specification in double quotation marks. For example:

CREATEBICI=(COLUMNS=ALL, EXTINFO=BICI, INPUT_FN=MYLIB/MYFILEIN, 
OUTPUT_FN=MYLIB/MYFILEOUT, ERROR_FN=”MYLIB/MYSRCFILE(ERROR_MBR)”

If you are generating before-image or change-indicator columns and the COLUMNS keyword identifies user-defined columns with expressions that invoke PowerExchange functions, ensure that the functions support BI buffering. If a function does not support BI buffering, PowerExchange does not generate BI or CI columns for the field. For more information, see Expression-Field Functions That Support CREATEBICI Processing.

For z/OS and IBMi operating systems, the extraction maps generated by the utility might exceed the default record lengths used for the system. For z/OS the default record length is 88 characters and for IBMi it is 184 characters. If you encounter errors when the system attempts to write the output from the utility, you might need to modify the utility input file or JCL SYSIN DD statement to override the default record length.

If PowerExchange accesses Microsoft SQL Server on a Linux operating system, the LD_LIBRARY_PATH environment variable on the Linux system must specify the value

$PWX_HOME/ODBC7.1/lib

for the DTLUCBRG utility to run. For more information about setting the environment variable, see the

PowerExchange Installation and Upgrade Guide

.

The DTLUCBRG utility cannot create capture registrations for Oracle global temporary tables. PowerExchange cannot capture change data from these tables because the table data is not available in the Oracle redo logs. The data is stored in temporary tablespaces for private use and deleted when the database session ends. If you try to register a global temporary table with the DTLUCBRG utility, the utility produces no registration for the table.