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.
There is usually some performance impact when you use
these parameters. You should review the full description of a parameter
in the Replication Agent for DB2 UDB Installation Guide for
OS/390 before using it.
If you need additional tracing to help debug the information passed to a Replication Agent user exit, you can 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 MVS 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.
No replication takes place when the value of the LTL_test_only parameter
is Y.
The Suppress_col_names configuration parameter determines whether LTM for MVS suppresses column names from the LTL that is sent to Replication Server.
If you are tracing LTL output, setting the value of this parameter to N ensures that column names are present in the generated LTL.
The trace=1,4 configuration parameter traces Sybase Log Extract calls to the Replication API and sends the output to SYSPRINT. Set the value of the trace=1,4 parameter to Y to turn on this trace.
The trace=1,11 configuration parameter writes LTL that is passed to Replication Server to LTLOUT. Set the value of the trace=1,11 parameter to Y to turn on this trace.
The trace=1,11 trace option
continues to send LTL to the primary Replication Server, whereas
the LTL_test_only option does
not.
The Use_repdef configuration parameter allows LTM for MVS 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.