XCOM transfer from z/OS to Windows vertical bar/pipe "|" translated to "ñ"
search cancel

XCOM transfer from z/OS to Windows vertical bar/pipe "|" translated to "ñ"

book

Article ID: 399057

calendar_today

Updated On:

Products

XCOM Data Transport - z/OS XCOM Data Transport - Windows XCOM Data Transport - Linux PC XCOM Data Transport

Issue/Introduction

Using an XCOM proxy server setup:

  1. XCOM on Mainframe transfers file to XCOM proxy server running under AIX.

  2. A 2nd transfer on the proxy server to the final XCOM for destination Windows server is executed via a post-processing Perl script (xcompp.pl) launched at the end of the 1st transfer. The 2nd transfer uses the same CODE parameter value as the 1st transfer.

When using parameter value CODE=EBCDIC on Mainframe the character vertical bar/pipe "|" in the file gets translated on the final destination Windows server to character n with a tilde i.e. "ñ"

Environment

XCOM™ Data Transport® for z/OS
XCOM™ Data Transport® for UNIX/Linux PC
XCOM™ Data Transport® for Windows

Resolution

This can be resolved via 2 options:

  1. Use custom XCOM translation tables on AIX proxy or final destination Windows server.
    Related doc. pages:
    XCOM Data Transport for UNIX/Linux 11.6.1 > Using > Creating Custom Character Sets for File Conversion
    XCOM™ Data Transport® for Windows 12.0 > Using > Use the Command-Line Interface to Perform XCOM Functions > Create Custom Character Sets for File Conversion

  2. Take advantage of the latest UNICODE support which is the suggested option as it is easier to configure and custom translation tables do not need to be maintained.
    Related article: Unicode and Multi-Byte Character Set Support for Translation for XCOM
    This option was used.
    Using CODE=UTF8 for both transfers resolved the vertical bar/pipe "|" mistranslation.