Use the output in the APICOM file to monitor Replication Extract’s calls to the Replication API in the following cases:
When a user exit is not installed
When a user exit is installed, but before it is invoked
Use the UELECMD file to examine the manner in which the user exit altered the LE Command structure.
Set the value of API_com_test to Y or O, depending on whether you want to process transaction operations while debugging. Use the output in the APICOM file to monitor Replication Extract’s calls to the Replication API without a user exit installed or before it is invoked, if a user exit is installed. Use the UELECMD file to examine Replication Extract’s calls to the Replication API after the user exit is invoked.
When you set the value of the API_com_test to N, Replication Agent does not write output to the APICOM or UELECMD files, but it allows Replication Agent to connect to Replication Server.
When the API_com_test parameter is set to Y, memory allocations and file input and output result. Sybase recommends that you set the API_com_test parameter to N for normal operation. The correct space allocation depends on the amount of data involved.
If you set the value of API_com_test to Y or O, uncomment the APICOM DD statement in the JCL that starts the LTM for MVS started task on MVS:
//APICOM DD DSN=hlq.APICOM,DISP=(,CATLG), // UNIT=SYSDA,DCB=(LRECL=4096,RECFM=VB), // SPACE=(CYL,(1,1))
Uncomment the UELECMD DD statement only if you installed a user exit in the JCL that starts the LTM for MVS task on MVS:
//UELECMD DD DSN=hlq.UELECMD,DISP=(,CATLG), // UNIT=SYSDA,DCB=(LRECL=4092,RECFM=VB), // SPACE=(CYL,(1,1))
See “Creating User Exits” in the Replication Agent for DB2 UBD User’s and Troubleshooting Guide for z/OS for information about using a user exit to replace binary zeros.
See Appendix B, “Creating User Exits” in the Replication Agent for DB2 UBD Installation Guide
