You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
- DBCS-open fields: display and accept both single-byte and double-byte<br />
characters. Double-byte characters are enclosed in shift-out and shift-in<br />
characters that have to be paired.<br />
- DBCS-either fields: display and accept either single-byte or double-byte<br />
characters, but not both. Double-byte characters are enclosed in shift-out<br />
and shift-in character pairs.<br />
- DBCS-graphic fields: display and accept only double-byte characters.<br />
Characters in a DBCS-graphic field do not have shift-out and shift-in<br />
characters. The AS/400 DBCS-graphic field is equivalent to a System/370<br />
DBCS field.<br />
– In ICF files, by defining fields with DBCS-open data type (type O).<br />
– In printer files, by defining fields with DBCS-open data type (type O) and<br />
DBCS-graphic data type (type G).<br />
– In display files, by defining fields with DBCS-only data type (type J),<br />
DBCS-either data type (type E), DBCS-open data type (type O), or<br />
DBCS-graphic data type (type G).<br />
– By using a double-byte literal that is used with the file at processing time,<br />
such as literals specified with the Default (DFT) and Error Message<br />
(ERRMSG) DDS keywords.<br />
Note: You may also use double-byte literals as text and comments in a file,<br />
such as with the DDS keyword TEXT. However, the system does not<br />
consider a file, whose only DBCS usage is that it has double-byte<br />
comments, to be a DBCS file.<br />
– By specifying the Alternative Data Type (IGCALTTYP) DDS keyword in<br />
display and printer files. This keyword lets you use display and printer files<br />
with both alphanumeric and double-byte applications. When you put the<br />
IGCALTTYP keyword into effect, you can use double-byte data with the file.<br />
Put the IGCALTTYP keyword into effect by creating, changing, or overriding<br />
display and printer files with the IGCDTA(*YES) value. You can put the<br />
IGCALTTYP keyword into effect for display and printer files by specifying<br />
IGCDTA(*YES) on the following device file commands:<br />
- Create Display <strong>File</strong> (CRTDSPF)<br />
- Create Printer <strong>File</strong> (CRTPRTF)<br />
- Change Display <strong>File</strong> (CHGDSPF)<br />
- Change Printer <strong>File</strong> (CHGPRTF)<br />
- Override with Display <strong>File</strong> (OVRDSPF)<br />
- Override with Printer <strong>File</strong> (OVRPRTF)<br />
When you specify IGCDTA(*NO), the IGCALTTYP keyword is not in effect<br />
and you can use only alphanumeric data with the file. Changing or<br />
overriding the file to put the IGCALTTYP keyword into effect does not<br />
change the DDS of the file.<br />
Except when using the IGCALTTYP function, you do not need to specify<br />
IGCDTA(*YES) on the file creation command if you have already specified<br />
DBCS functions in the DDS. Instead, specify IGCDTA(*YES) when the file has<br />
DBCS functions that are not indicated in the DDS. For example, specify<br />
IGCDTA(*YES) on the file creation command if the file is intended to contain<br />
double-byte data.<br />
v By specifying IGCDTA(*YES) on the following device file creation commands:<br />
– Create Diskette <strong>File</strong> (CRTDKTF)<br />
Appendix B. Double-byte character set support 205
Change language