ibm-information-center/dist/eclipse/plugins/i5OS.ic.dm_5.4.0.1/rbal3howindicate.htm

120 lines
11 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="How to indicate a DBCS file" />
<meta name="abstract" content="You must indicate that a device file is a DBCS file in order for the server to process double-byte data properly. You can indicate a DBCS file in the ways described in this topic." />
<meta name="description" content="You must indicate that a device file is a DBCS file in order for the server to process double-byte data properly. You can indicate a DBCS file in the ways described in this topic." />
<meta name="DC.subject" content="DBCS file, specifying, data description specifications (DDS), DBCS capabilities, alternative data type (IGCALTTYP) keyword, command, CL, CRTDSPF (Create Display File), indicating DBCS files, Create Display File (CRTDSPF) command, indicating DBCS files, CRTDSPF (Create Display File) command, Create Display File (CRTDSPF), display file, creating, CRTPRTF (Create Printer File), Create Printer File (CRTPRTF) command, CRTPRTF (Create Printer File) command, Create Printer File (CRTPRTF), printer file, CHGDSPF (Change Display File), CHGDSPF (Change Display File) command, Change Display File (CHGDSPF) command, command, CL, CHGDSPF (Change Display File), Change Display File (CHGDSPF), changing, display file, control character, shift, inserting, Change Display File (CHGDSPF) command, CHGPRTF (Change Printer File), CHGPRTF (Change Printer File) command, Change Printer File (CHGPRTF) command, CHGPRTF (Change Printer File), Change Printer File (CHGPRTF), printer file, Change Printer File (CHGPRTF) command, OVRDSPF (Override with Display File), indicating DBCS files, Override with Display File (OVRDSPF) command, OVRDSPF (Override with Display File) command, Override with Display File (OVRDSPF) command, Override with Display File (OVRDSPF), overriding with, overriding with, OVRPRTF (Override with Printer File), IGCALTTYP keyword, Override with Printer File (OVRPRTF), IGCALTTYP keyword, Override with Printer File (OVRPRTF) command, OVRPRTF (Override with Printer File) command, DBCS file, diskette file, Create Display File (CRTDSPF) command, putting IGCALTTYP keyword into effect, Create Printer File (CRTPRTF) command, putting IGCALTTYP keyword into effect, CRTTAPF (Create Tape File), Create Tape File (CRTTAPF) command, CRTTAPF (Create Tape File) command, Create Tape File (CRTTAPF) command, CRTTAPF (Create Tape File), Create Tape File (CRTTAPF), tape file, tape file, CRTPF (Create Physical File), Create Physical File (CRTPF) command, CRTPF (Create Physical File) command, Create Physical File (CRTPF) command, CRTPF (Create Physical File), Create Physical File (CRTPF), physical file, CRTSRCPF (Create Source Physical File), Create Source Physical File (CRTSRCPF) command, CRTSRCPF (Create Source Physical File) command, Create Source Physical File (CRTSRCPF) command, CRTSRCPF (Create Source Physical File), Create Source Physical File (CRTSRCPF), source physical file" />
<meta name="keywords" content="DBCS file, specifying, data description specifications (DDS), DBCS capabilities, alternative data type (IGCALTTYP) keyword, command, CL, CRTDSPF (Create Display File), indicating DBCS files, Create Display File (CRTDSPF) command, indicating DBCS files, CRTDSPF (Create Display File) command, Create Display File (CRTDSPF), display file, creating, CRTPRTF (Create Printer File), Create Printer File (CRTPRTF) command, CRTPRTF (Create Printer File) command, Create Printer File (CRTPRTF), printer file, CHGDSPF (Change Display File), CHGDSPF (Change Display File) command, Change Display File (CHGDSPF) command, command, CL, CHGDSPF (Change Display File), Change Display File (CHGDSPF), changing, display file, control character, shift, inserting, Change Display File (CHGDSPF) command, CHGPRTF (Change Printer File), CHGPRTF (Change Printer File) command, Change Printer File (CHGPRTF) command, CHGPRTF (Change Printer File), Change Printer File (CHGPRTF), printer file, Change Printer File (CHGPRTF) command, OVRDSPF (Override with Display File), indicating DBCS files, Override with Display File (OVRDSPF) command, OVRDSPF (Override with Display File) command, Override with Display File (OVRDSPF) command, Override with Display File (OVRDSPF), overriding with, overriding with, OVRPRTF (Override with Printer File), IGCALTTYP keyword, Override with Printer File (OVRPRTF), IGCALTTYP keyword, Override with Printer File (OVRPRTF) command, OVRPRTF (Override with Printer File) command, DBCS file, diskette file, Create Display File (CRTDSPF) command, putting IGCALTTYP keyword into effect, Create Printer File (CRTPRTF) command, putting IGCALTTYP keyword into effect, CRTTAPF (Create Tape File), Create Tape File (CRTTAPF) command, CRTTAPF (Create Tape File) command, Create Tape File (CRTTAPF) command, CRTTAPF (Create Tape File), Create Tape File (CRTTAPF), tape file, tape file, CRTPF (Create Physical File), Create Physical File (CRTPF) command, CRTPF (Create Physical File) command, Create Physical File (CRTPF) command, CRTPF (Create Physical File), Create Physical File (CRTPF), physical file, CRTSRCPF (Create Source Physical File), Create Source Physical File (CRTSRCPF) command, CRTSRCPF (Create Source Physical File) command, Create Source Physical File (CRTSRCPF) command, CRTSRCPF (Create Source Physical File), Create Source Physical File (CRTSRCPF), source physical file" />
<meta name="DC.Relation" scheme="URI" content="rbal3fsup.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3howindicate" />
<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>How to indicate a DBCS file</title>
</head>
<body id="rbal3howindicate"><a name="rbal3howindicate"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How to indicate a DBCS file</h1>
<div><p>You must indicate that a device file is a DBCS file in order for
the server to process double-byte data properly. You can indicate a DBCS file
in the ways described in this topic.</p>
<div class="section"><ul><li>Through DDS: <ul><li>DDS provides fields of the following data types. <ul><li><em>DBCS-only fields:</em> 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 must be paired.</li>
<li><em>DBCS-open fields:</em> display and accept both single-byte and double-byte
characters. Double-byte characters are enclosed in shift-out and shift-in
characters that must be paired.</li>
<li><em>DBCS-either fields:</em> display and accept <em>either</em> single-byte
or double-byte characters, but not <em>both</em>. Double-byte characters are
enclosed in shift-out and shift-in character pairs.</li>
<li><em>DBCS-graphic fields:</em> display and accept only double-byte characters.
Characters in a DBCS-graphic field do not have shift-out and shift-in characters.
The <span class="keyword">iSeries™</span> DBCS-graphic field
is equivalent to a System/370™ DBCS field.</li>
</ul>
</li>
<li>In ICF files, by defining fields with DBCS-open data type (type O).</li>
<li>In printer files, by defining fields with DBCS-open data type (type O)
and DBCS-graphic data type (type G).</li>
<li>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).</li>
<li>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. <div class="note"><span class="notetitle">Note:</span> You can also use double-byte literals as text
and comments in a file, such as with the DDS keyword TEXT. However, the server
does not consider a file, whose only DBCS usage is that it has double-byte
comments, to be a DBCS file.</div>
</li>
<li>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. <div class="p">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: <ul><li><a href="../cl/crtdspf.htm">Create Display
File (CRTDSPF)</a></li>
<li><a href="../cl/crtprtf.htm">Create Printer
File (CRTPRTF)</a></li>
<li><a href="../cl/chgdspf.htm">Change Display
File (CHGDSPF)</a></li>
<li><a href="../cl/chgprtf.htm">Change Printer
File (CHGPRTF)</a></li>
<li><a href="../cl/ovrdspf.htm">Override with
Display File (OVRDSPF)</a></li>
<li><a href="../cl/ovrprtf.htm">Override with
Printer File (OVRPRTF)</a></li>
</ul>
</div>
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. <p>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.</p>
</li>
</ul>
</li>
<li>By specifying IGCDTA(*YES) on the following device file creation commands: <ul><li><a href="../cl/crtdspf.htm">Create Display
File (CRTDSPF)</a></li>
<li><a href="../cl/crtprtf.htm">Create Printer
File (CRTPRTF)</a></li>
<li><a href="../cl/crttapf.htm">Create Tape
File (CRTTAPF)</a></li>
</ul>
</li>
<li>By specifying IGCDTA(*YES) on the following database file creation commands: <ul><li><a href="../cl/crtpf.htm">Create Physical
File (CRTPF)</a></li>
<li><a href="../cl/crtsrcpf.htm">Create Source
Physical File (CRTSRCPF)</a></li>
</ul>
</li>
</ul>
</div>
</div>
<div>
<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>