Mapping LTM for MVS datatypes to ASE datatypes

Replication Server requires your data to be compatible with ASE datatypes. Specify ASE datatypes for target table columns as needed when you create replication definitions on Replication Server.

Figure 2-1 illustrates the process of mapping your LTM for MVS data to ASE datatypes.

Figure 2-1: Mapping LTM for MVS datatypes to ASE datatypes

Table 2-2 shows the ASE datatypes you can specify in replication definitions.

**Table 2-2: LTM for MVS to ASE datatype conversion**
LTM for MVS datatype and example	Length (bytes)	ASE datatype and example
binary	250 or less	binary(), varbinary()
char hello	250 or less	char(), varchar() hello
char for bit data x‘F1F2F3’	250 or less Truncates after 250 characters.	char(), varchar() 123
varchar hello	250 or less Truncates after 250 characters.	varchar() hello
smallint 22	2	smallint, int 22
integer -22	4	int -22
float 1.2E3	Either: 4 (single precision) 8 (double precision)	float 1.2E3 LTM for MVS working with Replication Server can guarantee a precision of 15 digits for float. Depending on your system hardware, the 16th digit of float rounds unpredictably.
decimal 1.200	31 or less	float or decimal 1.200
date 1994-01-01	10 Map dates below 1753 to char.	datetime + default time Jan 1 1994 12:00AM See “Support for heterogeneous datatypes” for additional information on mapping the date datatype.
time 10:02:30	8	datetime + default date Jan 1 1990 10:02:30AM See “Support for heterogeneous datatypes” for additional information on mapping the time datatype.
timestamp 1994-01-01-10.02.30.006123	26	datetime Jan 1 1994 10:02:30:006AM See “Support for heterogeneous datatypes” for additional information on mapping the timestamp datatype.

See Appendix A, “LTM for MVS Configuration Parameters,” for information about the replace_null_in_char and Codepage configuration parameters.