|
|
|
Use the parameters below to specify the characteristics of the file and the data involved in the transfer. For information about using custom character conversion sets rather than the CA XCOM Data Transport defaults, see Create Custom Character Sets for File Conversion in this chapter.
CA XCOM Data Transport uses internal character conversion sets to handle different data encoding methods when files are sent or received. These default conversion sets are stored in files as conversion tables. When executing a non-binary file transfer that requires an ASCII/EBCDIC conversion, CA XCOM Data Transport uses these tables by default (INTERNAL_CONVERSION_TABLES=YES).
The default conversion tables are as follows:
%XCOM_HOME%\CONVTAB\ATOE.TAB
%XCOM_HOME%\CONVTAB\ETOA.TAB
Note: %XCOM_HOME% is an environment variable.
Example 1:
In the following example, the XCOM62 command is used. An EBCDIC text file is being transferred:
XCOM62 -f CARRIAGE_FLAG=YES CODE_FLAG=EBCDIC
All other necessary parameters are read from the default configuration file, XCOM.CNF.
Example 2:
In the following example, the XCOMTCP command is used. An EBCDIC text file is being transferred:
XCOMTCP -f CARRIAGE_FLAG=YES CODE_FLAG=EBCDIC
All other necessary parameters are read from the default configuration file, XCOM.CNF.
| Copyright © 2012 CA. All rights reserved. |
|