Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ecognizes the occurrence of double-byte data and takes appropriate measures to<br />
ensure the printer file that is used is capable of processing double-byte data.<br />
In some cases, however, the system cannot recognize the occurrence of double-byte<br />
data and may attempt to use a printer file that is not capable of processing<br />
double-byte data. If this occurs, the output at the display or printer may not be<br />
readable. This can happen when object descriptions containing double-byte<br />
characters are to be displayed or printed on an alphanumeric device.<br />
To ensure that you receive correct results when you display or print double-byte<br />
characters, some recommendations should be followed. Action is required on your<br />
part if you have a single-byte national language installed as a secondary language.<br />
Printer files that are received as part of the DBCS version of a product are always<br />
capable of processing DBCS data.<br />
The following recommended actions should be performed after the product or<br />
feature has been installed:<br />
1. If all printers and display devices attached to your system are DBCS-capable,<br />
you can enable all printer files for double-byte data. For <strong>IBM</strong>-supplied printer<br />
files that are received as part of a single-byte secondary language feature, you<br />
can enable all printer files by issuing the following command:<br />
CHGPRTF FILE(*ALL/*ALL) IGCDTA(*YES)<br />
After this command has been completed, all printer files in all libraries will be<br />
enabled for double-byte data. The change will be a permanent change.<br />
2. If all printer and display devices attached to your system are not<br />
DBCS-capable, it is recommended that you do not enable all <strong>IBM</strong>-supplied<br />
printer files.<br />
Instead, use the library search capabilities of the system to control which<br />
printer files will be used for any particular job. When the potential exists that<br />
double-byte data will be encountered, the library list for the job should be such<br />
that the printer files that are DBCS-enabled will be found first in the library list.<br />
Conversely, if only single-byte data is expected to be encountered, the library<br />
list should be set up so the printer files that are not enabled for DBCS will be<br />
found first. In this way, the printer file capabilities will match the type of data<br />
that will be processed. The decision as to what type of printer file to use is<br />
made on the basis of what type of data will be processed. The device that will<br />
be used to actually display or print the data may also influence this decision.<br />
In some cases it may be desirable to make the printer file only temporarily<br />
DBCS-capable instead of making a permanent change. For a specific job, you<br />
can make this temporary change by using the OVRPRTF command.<br />
To temporarily enable a specific printer file, you can use the following<br />
command:<br />
OVRPRTF FILE(filename) IGCDTA(*YES)<br />
Where filename is the name of the printer file you want to enable.<br />
Appendix B. Double-byte character set support 207
Change language