There are following functional differences compared with TF-MDPORT when you use Data Converter.
Latin alphabet characters and the code pages are supported in Data Converter, but proprietary character codes (e.g. Fujitsu JEF, IBM Kanji) and multi-byte character codes except for UNICODE (e.g SJIS, EUC) are not supported.
Item definition cannot be automatically generated from the C language include files.
Data Converter does not provide DDL generate function.
Command operands, date and time are not logged to the event log when you execute in batch mode.
The related resources created by TF-MDPORT cannot be used for Data Converter.
"YPS include specifications" cannot be specified for a type of the format file.
It does not support that co-operation with Interstage Charset Manager.
No functional differences compared with TF-MDPORT but the execution file name specified by the batch mode is different.
No functional differences compared with TF-MDPORT but the extension of the conversion instruction file is different.
No functional differences compared with TF-MDPORT but Operators specified by the data component selection are different.
