Mapping source data to LTM for MVS datatypes

LTM for MVS datatypes are nearly identical to DB2 datatypes.

Table 2-1 lists valid LTM for MVS datatypes.

**Table 2-1: LTM for MVS datatypes and lengths**
LTM for MVS datatype	Description	Length (bytes)
binary	Binary.	1–254
char	Character, fixed length.	1–255
char for bit data	Character, fixed length. Replication Agent replicates char for bit data as binary data. In this case, the target datatype must be binary or varbinary. The data is not transformed from EBCDIC to ASCII format, but is replicated as is (in binary format).	1–254
varchar	Character, varying length. Actual length = maximum + 2.	1–255
integer	Integer.	4
smallint	Integer.	2
decimal	Packed decimal. The length indicates the number of decimal digits, where the actual length = ((number of digits +1)÷2), rounded up.	1–16
float4	Floating decimal. 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.	4
float8	Floating decimal.	8
date	Date.	10
time	Time.	8
timestamp	Date and time.	26
db2 graphic	DB2 graphic is replicated as binary. LTM for MVS truncates GRAPHIC fields at 127 characters (binary data contains 2 bytes per character).	254
db2 vargraphic	DB2 graphic is replicated as binary. LTM for MVS truncates graphic fields at 127 characters (binary data contains 2 bytes per character).	1–254
long varchar	Long character, varying length.	1–32704*
Replication Agent limits long varchar* field lengths to 32704 bytes when Minimal_cols=N. When Minimal_cols=Y, Replication Agent limits varchar fields to 250 bytes and long varchar fields to 32700 bytes.