101 lines
6.7 KiB
HTML
101 lines
6.7 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="task" />
|
||
|
|
<meta name="DC.Title" content="Make printer files DBCS capable" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdesigndbcsapps.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/ovrprtf.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbagsdbcscapprintfile" />
|
||
|
|
<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>Make printer files DBCS capable</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbagsdbcscapprintfile"><a name="rbagsdbcscapprintfile"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Make printer files DBCS capable</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"><p>When the data involved contains double-byte characters, the printer
|
||
|
|
file that is used to place the data into the spooled file must be capable
|
||
|
|
of processing double-byte data. A printer file is capable of processing double-byte
|
||
|
|
data when *YES is specified on the IGCDTA parameter for the file. In most
|
||
|
|
cases, the system recognizes the occurrence of double-byte data and takes
|
||
|
|
appropriate measures to ensure the printer file that is used is capable of
|
||
|
|
processing double-byte data.</p>
|
||
|
|
<p>In some cases, however, the system cannot
|
||
|
|
recognize the occurrence of double-byte data and might attempt to use a printer
|
||
|
|
file that is not capable of processing double-byte data. If this occurs, the
|
||
|
|
output at the display or printer may not be readable. This can happen when
|
||
|
|
object descriptions containing double-byte characters are to be displayed
|
||
|
|
or printed on an alphanumeric device.</p>
|
||
|
|
<p>To ensure that you receive correct
|
||
|
|
results when you display or print double-byte characters, some recommendations
|
||
|
|
should be followed. Action is required on your part if you have
|
||
|
|
a single-byte national language installed as a secondary language. Printer
|
||
|
|
files that are received as part of the DBCS version of a product are always
|
||
|
|
capable of processing DBCS data.</p>
|
||
|
|
<p>You should complete the following recommended
|
||
|
|
actions after the product or feature has been installed:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>If all printers and display devices attached to your system are
|
||
|
|
DBCS-capable, you can enable all printer files for double-byte data. For IBM-supplied
|
||
|
|
printer files that are received as part of a single-byte secondary language
|
||
|
|
feature, you can enable all printer files by issuing the following command:</span> <pre>CHGPRTF FILE(*ALL/*ALL) IGCDTA(*YES)</pre>
|
||
|
|
<p>After
|
||
|
|
this command has been completed, all printer files in all libraries will be
|
||
|
|
enabled for double-byte data. The change will be permanent.</p>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>If all printer and display devices attached to your system are
|
||
|
|
not DBCS-capable, it is recommended that you do not enable all IBM-supplied
|
||
|
|
printer files.</span> <p>Instead, use the library search capabilities
|
||
|
|
of the system to control which printer files will be used for any particular
|
||
|
|
job. When the potential exists that double-byte data will be encountered,
|
||
|
|
the library list for the job should be such that the printer files that are
|
||
|
|
DBCS-enabled will be found first in the library list. Conversely, if only
|
||
|
|
single-byte data is expected to be encountered, the library list should be
|
||
|
|
set up so the printer files that are not enabled for DBCS will be found first.
|
||
|
|
In this way, the printer file capabilities will match the type of data that
|
||
|
|
will be processed. The decision as to what type of printer file to use is
|
||
|
|
made on the basis of what type of data will be processed. The device that
|
||
|
|
will be used to actually display or print the data may also influence this
|
||
|
|
decision.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>In some cases it may be desirable to make the printer file only
|
||
|
|
temporarily DBCS-capable instead of making a permanent change. For a specific
|
||
|
|
job, you can make this temporary change by using the OVRPRTF command.</p>
|
||
|
|
<p>To
|
||
|
|
temporarily enable a specific printer file, you can use the following command:</p>
|
||
|
|
<pre>OVRPRTF FILE(filename) IGCDTA(*YES)</pre>
|
||
|
|
<p>Where <em>filename</em> is the name of the printer file you want to enable.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdesigndbcsapps.htm" title="Design your application programs for processing double-byte data in the same way you design application programs for processing alphanumeric data.">Develop applications that process DBCS data</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/ovrprtf.htm">Override with Printer File (OVRPRTF) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|