72 lines
4.6 KiB
HTML
72 lines
4.6 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Specify COMP at the field level" />
|
||
|
|
<meta name="abstract" content="At the field level, COMP does not affect the physical or logical file you are describing." />
|
||
|
|
<meta name="description" content="At the field level, COMP does not affect the physical or logical file you are describing." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakbmstlcomp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakc/rzakcmstpos29.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakc/rzakcmstdfcomp.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="compfield" />
|
||
|
|
<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>Specify COMP at the field level</title>
|
||
|
|
</head>
|
||
|
|
<body id="compfield"><a name="compfield"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Specify COMP at the field level</h1>
|
||
|
|
<div><p>At the field level, COMP does not affect the physical or logical
|
||
|
|
file you are describing.</p>
|
||
|
|
<p>However, when you describe an input-capable field in a display file, you
|
||
|
|
can refer to the field you are describing by specifying R in position 29 and
|
||
|
|
the REF or REFFLD keyword. During display file creation, the operating system
|
||
|
|
copies the COMP keyword and other field attributes from the field in the logical
|
||
|
|
file into the field in the display file. You can override the COMP keyword
|
||
|
|
(as well as all other validity checking keywords and the CHKMSGID
|
||
|
|
keyword) by specifying any validity checking keyword for the field in the
|
||
|
|
display file.</p>
|
||
|
|
<p>You cannot specify a field name as a parameter value for a field-level
|
||
|
|
COMP keyword.</p>
|
||
|
|
<p>You cannot specify *NULL as a parameter value for a field level COMP keyword.</p>
|
||
|
|
<p>You cannot specify the COMP keyword on a floating-point field (F in position
|
||
|
|
35) or a hexadecimal field (H in position 35). Do not specify the COMP keyword
|
||
|
|
on a date, time, or timestamp field (L, T, or Z in position 35).</p>
|
||
|
|
<p>The rules for specifying this keyword in a physical or logical file are
|
||
|
|
the same as the rules for a display file.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Define a numeric field for physical and logical files</h4><p>When
|
||
|
|
a workstation user types in data, the operating system aligns the characters
|
||
|
|
typed in according to the number of decimal positions in the field. Leading
|
||
|
|
and trailing blanks are filled with zeros when the field is passed to your
|
||
|
|
program. If you do not type a decimal character, the operating system places
|
||
|
|
a decimal character to the right of the farthest right character typed. For
|
||
|
|
example, for a numeric field with a length of 5 (specified in position 34)
|
||
|
|
and 2 decimal positions (specified in position 37), 1.2 is interpreted as
|
||
|
|
001.20, and 100 is interpreted as 100.00.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakbmstlcomp.htm" title="Use this field-level keyword to specify validity checking for the field you are defining when it is referred to later during display file creation. For logical files, you can also specify this keyword at the select/omit-field level. COMP is equivalent to CMP.">COMP (Comparison) keyword for physical and logical files</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzakc/rzakcmstpos29.htm">Reference for display files (position 29)</a></div>
|
||
|
|
<div><a href="../rzakc/rzakcmstdfcomp.htm">COMP keyword for display files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|