64 lines
4.6 KiB
HTML
64 lines
4.6 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Data encoding" />
|
||
|
|
<meta name="abstract" content="Most operating systems, such as AIX and Linux, use ASCII character encoding. Most i5/OS functions use EBCDIC character encoding. You can specify a coded character set identifier (CCSID) value for some i5/OS object types to identify a specific encoding for character data in the object." />
|
||
|
|
<meta name="description" content="Most operating systems, such as AIX and Linux, use ASCII character encoding. Most i5/OS functions use EBCDIC character encoding. You can specify a coded character set identifier (CCSID) value for some i5/OS object types to identify a specific encoding for character data in the object." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalfinteract.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalffilesystems.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzalfdataconv" />
|
||
|
|
<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>Data encoding</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalfdataconv"><a name="rzalfdataconv"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Data encoding</h1>
|
||
|
|
<div><p>Most operating systems, such as AIX<sup>®</sup> and Linux<sup>®</sup>, use ASCII character encoding. Most <span class="keyword">i5/OS™</span> functions use EBCDIC character
|
||
|
|
encoding. You can specify a coded character set identifier (CCSID) value for
|
||
|
|
some <span class="keyword">i5/OS</span> object types
|
||
|
|
to identify a specific encoding for character data in the object.</p>
|
||
|
|
<p><span class="keyword">i5/OS</span> PASE byte stream
|
||
|
|
files have a CCSID attribute that is used by most system interfaces outside <span class="keyword">i5/OS</span> PASE to convert text data
|
||
|
|
read from or written to the file as needed. <span class="keyword">i5/OS</span> PASE
|
||
|
|
does not do CCSID conversion for data read from or written to stream files
|
||
|
|
(consistent with AIX), but it does set the CCSID attribute of any byte
|
||
|
|
stream file created by an <span class="keyword">i5/OS</span> PASE
|
||
|
|
program to the current <span class="keyword">i5/OS</span> PASE
|
||
|
|
CCSID value so other system functions can correctly handle ASCII text in the
|
||
|
|
file.</p>
|
||
|
|
<p>If you use AIX APIs
|
||
|
|
that are shipped in the <span class="keyword">i5/OS</span> PASE
|
||
|
|
shared libraries, <span class="keyword">i5/OS</span> PASE
|
||
|
|
handles most of the data conversion for you. <span class="keyword">i5/OS</span> PASE
|
||
|
|
programs can use <tt>iconv</tt> functions provided in shared library <tt>libiconv.a</tt> for
|
||
|
|
any character data conversions that are not handled automatically by <span class="keyword">i5/OS</span> PASE runtime. For example,
|
||
|
|
an <span class="keyword">i5/OS</span> PASE application
|
||
|
|
generally needs to convert character strings to EBCDIC before calling an <span class="keyword">i5/OS</span> API function (using either
|
||
|
|
_ILECALLX or _PGMCALL).</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalfinteract.htm" title="As you customize your i5/OS PASE programs to use i5/OS functions, you need to consider the ways in which your program will interact with them.">How i5/OS PASE programs interact with i5/OS</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzalffilesystems.htm" title="i5/OS PASE programs can access any file or resource that is accessible through the integrated file system, including objects in the QSYS.LIB and QOPT file systems.">File systems</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|