When you map data to the ASE datetime datatype, be sure you understand the data type conversion that can occur between LTM for MVS date, time, and timestamp data and ASE datetime data.
Replication Server version 12.0 and later includes Heterogeneous Datatype
Support (HDS). This means that you can now use DB2 date, time, and timestamp datatypes
without having to map them to ASE datatypes. For more information
on setting up Replication Server and the HDS feature, see the Replication
Server Configuration Guide.
ASE datetime data is accurate only up to one thousandth of a second. For example, if you map a time column in your primary table that contains 10.02.30.006123 to the ASE datetime datatype, the conversion results in a loss of the last three digits: 10:02:30:006AM.
You can prevent this precision loss by:
Converting LTM for MVS date, time, and timestamp columns in your primary table to char format.
Setting the following LTM for MVS configuration parameter values:
Time_in_char=Y (time columns are sent as char(8) fields instead of mapping to the ASE datetime datatype.)
Date_in_char=Y (date columns are sent as char(10) fields instead of mapping to the ASE datetime datatype.)
Timestamp_in_char=Y (timestamp columns are sent as char(26) fields instead of mapping to the ASE datetime datatype.)
Writing a user exit to convert timestamp data to char format. This approach is ideal for handling subsets of source data.
See Appendix B, “Creating User Exits” in the Replication Agent for DB2 UBD Installation Guide for further information.
