You can use the configuration parameters described in this section to obtain additional information that is not normally presented by Replication Agent for DB2 UDB.
To print the log record identifier for each log record, and additional messages received from the DB2 API, enter Logtrace = Y in the LTMCFG file.
There is usually some performance impact when you use
these parameters. Review the full description of a parameter in
the Replication Agent for DB2 UDB Installation Guide before
using it.
If you need additional tracing to help debug the information passed to a Replication Agent user exit, set the value of the API_com_test configuration parameter to Y. You can also use this trace when no exit is being used.
The LTL_test_only configuration parameter controls whether LTM for z/OS connects to Replication Server and sends transaction operations for replication. When the value of the LTL_test_only parameter is Y, LTL that would normally be sent to Replication Server is written to the LTLOUT file instead.
The Replication Agent for DB2 UDB is “not corrected
to” the Replication Server when the value of the LTL_test_only parameter
is Y.
The trace=LTLebcdic configuration parameter writes EBCDIC LTL that is passed to Replication Server to LTLOUT. If you are replicating a table that contains ASCII data, set the trace = LTLASCII to write the ASCII characters to the LTLOUT data set. You must set the value of these parameters to Y to turn on this trace.
The Use_repdef configuration parameter allows LTM for z/OS to send LTL to Replication Server that contains only the columns specified in the replication definition.
Setting the value of the Use_repdef parameter to N may increase the amount of information provided in an LTL trace.
The suppress_col_names configuration parameter determines whether LTM for z/OS suppresses column names from the LTL that is sent to Replication Server.
If you are tracing LTL output, set the value of suppress_col_names to N to ensure that column names are present in the generated LTL.
