83 lines
5.2 KiB
HTML
83 lines
5.2 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="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<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="Improperly indicated DBCS files" />
|
||
|
|
<meta name="abstract" content="If you do not properly indicate that a file is a DBCS file, some errors might occur." />
|
||
|
|
<meta name="description" content="If you do not properly indicate that a file is a DBCS file, some errors might occur." />
|
||
|
|
<meta name="DC.subject" content="DBCS file, restrictions, restriction, DBCS files" />
|
||
|
|
<meta name="keywords" content="DBCS file, restrictions, restriction, DBCS files" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3fsup.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3makpfilecap.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbal3iidf" />
|
||
|
|
<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>Improperly indicated DBCS files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal3iidf"><a name="rbal3iidf"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Improperly indicated DBCS files</h1>
|
||
|
|
<div><p>If you do not properly indicate that a file is a DBCS file, some
|
||
|
|
errors might occur.</p>
|
||
|
|
<div class="section"><ul><li>For printer files, printer data management assumes the output data to
|
||
|
|
the printer does not contain double-byte data. The end result depends on
|
||
|
|
the type of printer the data is printed on and the status of the replace unprintable
|
||
|
|
character parameter for the printer file you are using. <p>If the replace-unprintable-character
|
||
|
|
option is selected, printer data management interprets shift-control characters
|
||
|
|
as unprintable characters and replaces them with blanks. The double-byte
|
||
|
|
data itself is interpreted as alphanumeric data, and the printer attempts
|
||
|
|
to print it as such. The printed double-byte data does not make sense.</p>
|
||
|
|
<p>If
|
||
|
|
the replace-unprintable-character option is not selected and the printer is
|
||
|
|
an alphanumeric printer, the double-byte data, including the control characters,
|
||
|
|
is sent as is to the printer. On most alphanumeric printers, the shift-control
|
||
|
|
characters are not supported, and an error will occur at the printer.</p>
|
||
|
|
<p>If
|
||
|
|
the replace-unprintable-character option is not selected and the printer is
|
||
|
|
a DBCS printer, the double-byte data is printed with the exception of extended
|
||
|
|
characters. Because the file was not indicated as a DBCS file, the server
|
||
|
|
will not perform extended character processing. The extended characters are
|
||
|
|
printed with the symbol for undefined double-byte characters.</p>
|
||
|
|
</li>
|
||
|
|
<li>For display files, display data management assumes that the output data
|
||
|
|
to the display does not contain double-byte data. The end result depends
|
||
|
|
on whether the display is an alphanumeric or DBCS display. <p>If the display
|
||
|
|
is an alphanumeric display, the double-byte data is interpreted as alphanumeric
|
||
|
|
data. The shift-control characters appear as anks. The displayed double-byte
|
||
|
|
data does not make sense.</p>
|
||
|
|
<p>If the display is a DBCS display, the double-byte
|
||
|
|
data is displayed with the exception of extended characters. The server does
|
||
|
|
not perform extended character processing on the data. Therefore, extended
|
||
|
|
characters are displayed with the symbol for undefined double-byte characters.</p>
|
||
|
|
</li>
|
||
|
|
<li>The server does not recognize literals with DBCS text as double-byte literals
|
||
|
|
if the source file is not specified as a DBCS file.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbal3makpfilecap.htm">Make printer files capable of DBCS</a></strong><br />
|
||
|
|
In many cases, printer files are used by the server to produce data that will eventually be printed or displayed. In these cases, the data is first placed into a spooled file using one of the IBM-supplied printer files. The data is then taken from the spooled file and is displayed or printed based on the request of the user.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3fsup.htm" title="This section describes DBCS-capable device files and special considerations for working with DBCS-capable device files.">DBCS device file support</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|