User exit memory management |
The exit routine must not free any space passed through the parameter list. The user exit manages all memory it allocates. Sybase recommends that you use the provided work area (the APWKAREA attribute of the user exit communications area), instead of allocating additional memory. |
What to avoid when using a user exit |
Avoid performing physical input and output operations. These operations significantly impair Replication Agent performance. Do not allocate storage that you do not maintain. |
User exits and Replication Server |
Avoid circumventing Replication Server by using a user exit to replicate into another database on z/OS. This task involves issues beyond the scope of Replication Agent. |
Considerations for working with the LE Command structure (LE_CMD) |
Do not remove nodes from the LE Command structure. Do not rearrange the sequence of columns defined by the sequence of @RPTCOL nodes in the LE Command structure. The user exit does not change the value of the @LECOL pointer in the LE_CMD node. The user exit does not change the value of the @RPTCOL_NEXT pointer in the @RPTCOL nodes, except when you use a user exit to add columns. In this case, the exit changes the value of the @RPTCOL_NEXT pointer from null to a valid address of the added column in the last @RPTCOL node in the @RPTCOL list. |
