|
|
|
CA XCOM Data Transport uses internal character conversion sets to handle different file formats 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.
For conversions, when transferring text files for transfers that are initiated on a UNIX or Linux system, CARRIAGE_FLAG is set to YES and CODE_FLAG is set to EBCDIC.
Example 1
In the following example, the xcom62 command is used. An EBCDIC text file is being transferred:
xcom62 -c1 -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 -c1 -f CARRIAGE_FLAG=YES CODE_FLAG=EBCDIC
All other necessary parameters are read from the default configuration file, xcom.cnf.
| Copyright © [set copyright date variable] CA. All rights reserved. |
|