88 lines
5.8 KiB
HTML
88 lines
5.8 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="National Language Support considerations for FTP" />
|
||
|
|
<meta name="abstract" content="This topic provides several points that you need to be aware of when using File Transfer Protocol (FTP) in an environment with different primary languages." />
|
||
|
|
<meta name="description" content="This topic provides several points that you need to be aware of when using File Transfer Protocol (FTP) in an environment with different primary languages." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqreferencedt8.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqreferencedt8a.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiqreferencedt8c" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>National Language Support considerations for FTP</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqreferencedt8c"><a name="rzaiqreferencedt8c"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">National Language Support considerations for FTP</h1>
|
||
|
|
<div><p>This topic provides several points that you need to be aware of
|
||
|
|
when using File Transfer Protocol (FTP) in an environment with different primary
|
||
|
|
languages.</p>
|
||
|
|
<div class="section"><ul><li>When data is transferred using TYPE E (or EBCDIC), the data is stored
|
||
|
|
as is and therefore will be in the EBCDIC code page of the file that it came
|
||
|
|
from. This can result in the stored file being tagged with an inappropriate
|
||
|
|
CCSID value when the primary language of the two iSeries™ servers is different. <p>For
|
||
|
|
example, when data in code page 237 is sent using TYPE E to the QSYS.LIB file
|
||
|
|
system on a machine where the file does not exist, the data is stored as is
|
||
|
|
in a new file tagged with CCSID 65535. If the receiving file already exists,
|
||
|
|
then the data will be received as is and tagged with the existing file CCSID
|
||
|
|
which can not be 237.</p>
|
||
|
|
<p>To avoid incorrect CCSID tagging, you can use
|
||
|
|
the TYPE C CCSID subcommand (for example, TYPE C 237) to specify the CCSID
|
||
|
|
of the data being transferred. When a CCSID is specified on a transfer and
|
||
|
|
the data is written to an existing file, the data is converted to the CCSID
|
||
|
|
of the existing file. If no target file exists before the transfer, a file
|
||
|
|
is created and tagged with the specified CCSID.</p>
|
||
|
|
<p>In the preceding example,
|
||
|
|
if the target file does not exist, a file with a CCSID of 237 is created on
|
||
|
|
the receiving system. When the target file already exists, the data is converted
|
||
|
|
from CCSID 237 to the CCSID of the target file.</p>
|
||
|
|
</li>
|
||
|
|
<li>When starting the FTP client, message TCP3C14: <samp class="codeph">Unable to convert
|
||
|
|
data from CCSID &1 to CCSID &2</samp>, may be displayed. This occurs
|
||
|
|
if no character conversion is available between the EBCDIC CCSID specified
|
||
|
|
by your job and the ASCII CCSID specified for the this FTP session. <p>You
|
||
|
|
can change the ASCII CCSID by specifying a value for the coded character set
|
||
|
|
identifier parameter of the STRTCPFTP CL command. CCSID 850, which contains
|
||
|
|
the IBM<sup>®</sup> Personal
|
||
|
|
Computer Latin-1 coded character set, is an ASCII CCSID for which character
|
||
|
|
conversions are available to all valid job CCSID values.</p>
|
||
|
|
</li>
|
||
|
|
<li>When using FTP in ASCII mode between two EBCDIC systems, the data on the
|
||
|
|
system sending the file is converted from its stored EBCDIC code page to ASCII,
|
||
|
|
and then from ASCII to the EBCDIC code page of the receiving system. Typically
|
||
|
|
this does not present a problem because the 7-bit ASCII code page used by
|
||
|
|
the two systems is the same unless the EBCDIC characters on the sending system
|
||
|
|
are not defined in the ASCII code page. Also, some characters in the ASCII
|
||
|
|
code page might be mapped differently between the two different EBCDIC code
|
||
|
|
pages. This might occur if some of the ASCII characters are variant (the character
|
||
|
|
occupies a different hexadecimal code point in an EBCDIC code page). The variant
|
||
|
|
character might be interpreted differently on the receiving system if the
|
||
|
|
EBCDIC code page is different from that of the system sending the file.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqreferencedt8.htm" title="iSeries uses Coded Character Set Identifier (CCSID) information to interpret the input data and provide the output data in the proper format for display.">Coded Character Set Identifier conversions</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaiqreferencedt8a.htm" title="For File Transfer Protocol (FTP) client, the ASCII mapping tables are specified in the FTP command. For FTP server this is done in the Change FTP Attributes (CHGFTPA) command.">Specify mapping tables</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|