File Management - IBM
File Management - IBM File Management - IBM
DBCS device file support 204 File Management V4R5 v On displays, the system displays the undefined character where it would otherwise display extended characters. v On printed output, the system prints the undefined character where it would otherwise print extended characters. v The extended characters, though not displayed or printed, are stored correctly in the system. The following sections describe DBCS-capable device files and special considerations for working with DBCS-capable device files. Data description specifications (DDS), a language used to describe files, can be used with DBCS-capable device files. For information about using DDS, refer to the DDS Reference. What a DBCS file is A DBCS file is a file that contains double-byte data or is used to process double-byte data. Other files are called alphanumeric files. The following types of device files can be DBCS files: v Display v Printer v Tape v Diskette v ICF When to indicate a DBCS file You should indicate that a file is DBCS in one or more of the following situations: v The file receives input, or displays or prints output, which has double-byte characters. v The file contains double-byte literals. v The file has double-byte literals in the DDS that are used in the file at processing time (such as constant fields and error messages). v The DDS of the file includes DBCS keywords. See the DDS Reference for information on these keywords. v The file stores double-byte data (database files). How to indicate a DBCS file You must indicate that a device file is a DBCS file in order for the system to process double-byte data properly. You can do this in one of the following ways: v Through DDS – DDS provides fields of the following data types. - DBCS-only fields: display and accept only double-byte characters. Double-byte characters in a DBCS-only field are enclosed in shift-out and shift-in characters that have to be paired.
- DBCS-open fields: display and accept both single-byte and double-byte characters. Double-byte characters are enclosed in shift-out and shift-in characters that have to be paired. - DBCS-either fields: display and accept either single-byte or double-byte characters, but not both. Double-byte characters are enclosed in shift-out and shift-in character pairs. - DBCS-graphic fields: display and accept only double-byte characters. Characters in a DBCS-graphic field do not have shift-out and shift-in characters. The AS/400 DBCS-graphic field is equivalent to a System/370 DBCS field. – In ICF files, by defining fields with DBCS-open data type (type O). – In printer files, by defining fields with DBCS-open data type (type O) and DBCS-graphic data type (type G). – In display files, by defining fields with DBCS-only data type (type J), DBCS-either data type (type E), DBCS-open data type (type O), or DBCS-graphic data type (type G). – By using a double-byte literal that is used with the file at processing time, such as literals specified with the Default (DFT) and Error Message (ERRMSG) DDS keywords. Note: You may also use double-byte literals as text and comments in a file, such as with the DDS keyword TEXT. However, the system does not consider a file, whose only DBCS usage is that it has double-byte comments, to be a DBCS file. – By specifying the Alternative Data Type (IGCALTTYP) DDS keyword in display and printer files. This keyword lets you use display and printer files with both alphanumeric and double-byte applications. When you put the IGCALTTYP keyword into effect, you can use double-byte data with the file. Put the IGCALTTYP keyword into effect by creating, changing, or overriding display and printer files with the IGCDTA(*YES) value. You can put the IGCALTTYP keyword into effect for display and printer files by specifying IGCDTA(*YES) on the following device file commands: - Create Display File (CRTDSPF) - Create Printer File (CRTPRTF) - Change Display File (CHGDSPF) - Change Printer File (CHGPRTF) - Override with Display File (OVRDSPF) - Override with Printer File (OVRPRTF) When you specify IGCDTA(*NO), the IGCALTTYP keyword is not in effect and you can use only alphanumeric data with the file. Changing or overriding the file to put the IGCALTTYP keyword into effect does not change the DDS of the file. Except when using the IGCALTTYP function, you do not need to specify IGCDTA(*YES) on the file creation command if you have already specified DBCS functions in the DDS. Instead, specify IGCDTA(*YES) when the file has DBCS functions that are not indicated in the DDS. For example, specify IGCDTA(*YES) on the file creation command if the file is intended to contain double-byte data. v By specifying IGCDTA(*YES) on the following device file creation commands: – Create Diskette File (CRTDKTF) Appendix B. Double-byte character set support 205
- Page 164 and 165: Default system output queues 154 Fi
- Page 166 and 167: Spooling writers 156 File Managemen
- Page 168 and 169: value of *OWNER indicates that only
- Page 170 and 171: 160 File Management V4R5 You can us
- Page 172 and 173: 162 File Management V4R5 QFNC Finan
- Page 174 and 175: 164 File Management V4R5 If a job b
- Page 176 and 177: Spooling subsystem 166 File Managem
- Page 178 and 179: 168 File Management V4R5 the DLTSPL
- Page 180 and 181: Table 20. Open Feedback Area (conti
- Page 182 and 183: Table 20. Open Feedback Area (conti
- Page 184 and 185: Table 21. Device Definition List (c
- Page 186 and 187: Table 21. Device Definition List (c
- Page 188 and 189: Table 21. Device Definition List (c
- Page 190 and 191: Table 23. Common I/O Feedback Area
- Page 192 and 193: Table 23. Common I/O Feedback Area
- Page 194 and 195: Table 23. Common I/O Feedback Area
- Page 196 and 197: Table 24. I/O Feedback Area for ICF
- Page 198 and 199: Table 24. I/O Feedback Area for ICF
- Page 200 and 201: Table 26. I/O Feedback Area for Dat
- Page 202 and 203: Table 27. Get Attributes (continued
- Page 204 and 205: Table 27. Get Attributes (continued
- Page 206 and 207: Table 27. Get Attributes (continued
- Page 208 and 209: (SBCS) A B 1 2 1-Byte Code X’C1
- Page 210 and 211: 200 File Management V4R5 Table 28.
- Page 212 and 213: Invalid double-byte code and undefi
- Page 216 and 217: 206 File Management V4R5 - Create D
- Page 218 and 219: DBCS display support 208 File Manag
- Page 220 and 221: 210 File Management V4R5 When you c
- Page 222 and 223: DBCS font tables 212 File Managemen
- Page 224 and 225: 214 File Management V4R5 CPYIGCTBLI
- Page 226 and 227: DBCS font files DBCS sort tables 21
- Page 228 and 229: Finding out if a DBCS sort table ex
- Page 230 and 231: 220 File Management V4R5 v When you
- Page 232 and 233: User-created dictionary for DBCS 22
- Page 234 and 235: Work with DBCS conversion dictionar
- Page 236 and 237: another alphanumeric entry in the e
- Page 238 and 239: Figure 22. Display Produced by the
- Page 240 and 241: 230 File Management V4R5 1. Positio
- Page 242 and 243: Figure 23. Example Screen 1 Positio
- Page 244 and 245: Figure 27. Example Screen 5 234 Fil
- Page 246 and 247: 236 File Management V4R5 - If you t
- Page 248 and 249: contains information on data descri
- Page 250 and 251: 240 File Management V4R5
- Page 252 and 253: CHGWTR (Change Writer) command 157
- Page 254 and 255: command, CL 160, 212 (continued) Tr
- Page 256 and 257: DBCS conversion dictionary (continu
- Page 258 and 259: file object authority 8 file proces
- Page 260 and 261: output queue (continued) changing 1
- Page 262 and 263: estriction DBCS files 206 deleting
DBCS device file support<br />
204 <strong>File</strong> <strong>Management</strong> V4R5<br />
v On displays, the system displays the undefined character where it would<br />
otherwise display extended characters.<br />
v On printed output, the system prints the undefined character where it would<br />
otherwise print extended characters.<br />
v The extended characters, though not displayed or printed, are stored correctly in<br />
the system.<br />
The following sections describe DBCS-capable device files and special<br />
considerations for working with DBCS-capable device files. Data description<br />
specifications (DDS), a language used to describe files, can be used with<br />
DBCS-capable device files. For information about using DDS, refer to the DDS<br />
Reference.<br />
What a DBCS file is<br />
A DBCS file is a file that contains double-byte data or is used to process<br />
double-byte data. Other files are called alphanumeric files.<br />
The following types of device files can be DBCS files:<br />
v Display<br />
v Printer<br />
v Tape<br />
v Diskette<br />
v ICF<br />
When to indicate a DBCS file<br />
You should indicate that a file is DBCS in one or more of the following situations:<br />
v The file receives input, or displays or prints output, which has double-byte<br />
characters.<br />
v The file contains double-byte literals.<br />
v The file has double-byte literals in the DDS that are used in the file at processing<br />
time (such as constant fields and error messages).<br />
v The DDS of the file includes DBCS keywords. See the DDS Reference for<br />
information on these keywords.<br />
v The file stores double-byte data (database files).<br />
How to indicate a DBCS file<br />
You must indicate that a device file is a DBCS file in order for the system to<br />
process double-byte data properly. You can do this in one of the following ways:<br />
v Through DDS<br />
– DDS provides fields of the following data types.<br />
- DBCS-only fields: display and accept only double-byte characters.<br />
Double-byte characters in a DBCS-only field are enclosed in shift-out and<br />
shift-in characters that have to be paired.
Change language