ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakc_5.4.0.1/rzakcoverlfield.htm

74 lines
4.9 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Overlapping fields" />
<meta name="abstract" content="Within a record format, you can define fields to overlap portions of other fields or their attribute characters; however, only one of those fields is shown on the display at a time." />
<meta name="description" content="Within a record format, you can define fields to overlap portions of other fields or their attribute characters; however, only one of those fields is shown on the display at a time." />
<meta name="DC.Relation" scheme="URI" content="pos3944.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="rzakcoverlfield" />
<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>Overlapping fields</title>
</head>
<body id="rzakcoverlfield"><a name="rzakcoverlfield"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Overlapping fields</h1>
<div><p>Within a record format, you can define fields to overlap portions
of other fields or their attribute characters; however, only one of those
fields is shown on the display at a time.</p>
<p>At run time, when processing overlapping fields within a record, the <span class="keyword">i5/OS™</span> program looks at the fields
in line and position sequence. When the <span class="keyword">i5/OS</span> operating
system finds a field whose conditioning is satisfied or that does not have
an option indicator specified, it selects that field for display and ignores
the remaining overlapping fields. The first overlapping field that does not
have an option indicator specified always stops the search, and any subsequent
overlapping fields are never displayed. In the following example, if indicator
01 is set on, FIELD1 is the only field displayed. If indicator 01 is off and
indicator 02 is on, FIELD2 is the only field displayed. FIELD3 is displayed
when neither of the others is selected.</p>
<p><a href="#rzakcoverlfield__overlap">Figure 1</a> shows how to define overlapping
fields.</p>
<div class="fignone" id="rzakcoverlfield__overlap"><a name="rzakcoverlfield__overlap"><!-- --></a><span class="figcap">Figure 1. Specify overlapping fields</span><pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A 01 FIELD1 10 1 5TEXT('ONE')
00020A 02 FIELD2 5 1 5TEXT('TWO')
00030A FIELD3 2 0 1 5TEXT('THREE')
A</pre>
</div>
<p>If used incorrectly, this capability can result in problems in user and
program communication. In the following example, only one input field (FIELD4)
is specified for the record, and according to the field location specification,
this field overlaps a preceding output field. The workstation user is not
able to type in any data because FIELD1 is always the field selected for display.
The other three fields, including FIELD4, are never displayed.</p>
<p><a href="#rzakcoverlfield__nondisp">Figure 2</a> shows an example of incorrect
field specification entry.</p>
<div class="fignone" id="rzakcoverlfield__nondisp"><a name="rzakcoverlfield__nondisp"><!-- --></a><span class="figcap">Figure 2. Incorrect field specification</span><pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A FIELD1 10 1 5TEXT('ONE')
00020A 21 FIELD2 5 1 5TEXT('TWO')
00030A 12 FIELD3 2 0 1 5TEXT('THREE')
00040A FIELD4 5Y 2I 1 5TEXT('FOUR')
A</pre>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="pos3944.htm" title="Use these positions to specify the exact location on the display where each field begins.">Location for display files (positions 39 through 44)</a></div>
</div>
</div>
</body>
</html>