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

246 lines
16 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="reference" />
<meta name="DC.Title" content="DSPSIZ (Display Size) keyword for display files" />
<meta name="abstract" content="Use this file-level keyword to specify the display size to which your program can open this display file." />
<meta name="description" content="Use this file-level keyword to specify the display size to which your program can open this display file." />
<meta name="DC.subject" content="DSPSIZ (Display Size) keyword, Display Size (DSPSIZ) keyword" />
<meta name="keywords" content="DSPSIZ (Display Size) keyword, Display Size (DSPSIZ) keyword" />
<meta name="DC.Relation" scheme="URI" content="rzakcmstkeyent.htm" />
<meta name="DC.Relation" scheme="URI" content="pos3944.htm" />
<meta name="DC.Relation" scheme="URI" content="pos716.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="rzakcmstdfdspsz" />
<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>DSPSIZ (Display Size) keyword for display files</title>
</head>
<body id="rzakcmstdfdspsz"><a name="rzakcmstdfdspsz"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">DSPSIZ (Display Size) keyword for display files</h1>
<div><p>Use this file-level keyword to specify the display size to which
your program can open this display file.</p>
<div class="section"><p>The formats of the keyword are:</p>
<pre>DSPSIZ(*DSw [*DSx])
DSPSIZ(lines positions[condition-name-1][lines positions[condition-name-2]])</pre>
<p>The
DSPSIZ keyword is optional. If you do not specify it for a display file, the
display file can be opened only to display devices with a 24 x 80 display
size. You can specify this keyword in one of two ways:</p>
<ul><li>Using IBM-supplied display size condition names. Specify up to two parameter
values as *DS3 or *DS4 in any order. At least one parameter value is required.
You cannot specify a parameter value twice.</li>
<li>Specifying lines and positions to permit user-defined display size condition
names. Instead of the IBM-supplied display size condition names, specify the
display size in lines and positions (only 24 x 80, and 27 x 132 are valid).
(See examples 1, 2, and 3, in this topic.) <p>Optionally, you can also define
a display size condition name other than *DS3 or *DS4. The display size condition
name you define must be from 2 to 8 characters long, and the first character
must be an asterisk (*). You can specify these user-defined condition names
in positions 7 through 16 (conditioning) on subsequent DDS statements at the
field level. (See example 2, in this topic.) If you do not specify user-defined
display size condition names, you must use IBM-supplied display size condition
names to condition the location of fields.</p>
<p>If you specify more than
one parameter value, see <a href="#rzakcmstdfdspsz__dfpsss">Primary and
secondary display sizes</a> in this topic.</p>
</li>
</ul>
<p>Option indicators are not valid for this keyword.</p>
</div>
<div class="section" id="rzakcmstdfdspsz__dfpsss"><a name="rzakcmstdfdspsz__dfpsss"><!-- --></a><h4 class="sectiontitle">Primary and secondary display sizes</h4><p>Whether you use IBM-supplied display
size condition names or specify lines and positions directly, the first display
size you specify is the <em>primary display size</em>. The second display size,
if specified, is the <em>secondary display size</em>. <a href="#rzakcmstdfdspsz__exsiz">Figure 1</a> shows
an example of primary and secondary display size specification.</p>
</div>
<div class="example"> <div class="fignone" id="rzakcmstdfdspsz__exsiz"><a name="rzakcmstdfdspsz__exsiz"><!-- --></a><span class="figcap">Figure 1. Use DSPSIZ to specify primary
and secondary display sizes</span><br /><img src="rsll664.gif" alt="The figure shows the keyword&#xA;specified as DSPSIZ(24 80 27 132). The primary display size is 24 by 80; the&#xA;secondary display size is 27 by 132." /><br /></div>
<p>When you specify more than one display size for DSPSIZ, you can specify
display size condition names in positions 7 through 16 on subsequent DDS statements
at the record and field levels. These display size condition names are then
used to condition keywords and the locations of fields. When both a primary
and secondary display are specified, the display file will be validated for
both sizes.</p>
<div class="note"><span class="notetitle">Note:</span> If you specify user-defined display size condition names
for DSPSIZ, you cannot use IBM-supplied display size condition names for conditioning.</div>
<p>The
capability to display in the 27 x 132 mode is allowed only on a 3180-2, or
a 3197 Model D1, D2, W1, or W2 device attached locally to a 6040 or 6041 controller
or remotely to a 5294 or 5394 controller. The display size for the 27 x 132
mode will be ignored for DSPSIZ unless these controllers are used.</p>
<p>The
following table shows the valid display sizes.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="33.33333333333333%" id="d0e87">Display sizes</th>
<th valign="top" width="33.33333333333333%" id="d0e89">Display device</th>
<th valign="top" width="33.33333333333333%" id="d0e91">Meaning</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="33.33333333333333%" headers="d0e87 ">*DS3 or 24 x 80</td>
<td valign="top" width="33.33333333333333%" headers="d0e89 ">3179 3180 3196 3197 3476 3486 3487 (Models HA, HC, HG, and HW) 3488
5251 (Models 11 and 12) 5291 5292</td>
<td valign="top" width="33.33333333333333%" headers="d0e91 ">24 lines x 80 positions 1920 positions total</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e87 ">*DS4 or 27 x 132</td>
<td valign="top" width="33.33333333333333%" headers="d0e89 ">3180 3197 (Models D1, D2, W1, and W2) 3477 (Models FA, FC, FD, and
FG) 3487 (Models HA, HC, HG, and HW) 3488 (Use 6040 or 6041 controller locally,
or 5294 or 5394 controller remotely for 27 x 132 display capability.)</td>
<td valign="top" width="33.33333333333333%" headers="d0e91 ">27 lines x 132 positions 3564 positions total</td>
</tr>
</tbody>
</table>
</div>
<p>The display size designated as the primary display size should
be the one with which the display file will most often be used. Additional
processing is performed when the actual display size is the secondary display
size.</p>
<p>The display size condition names let you improve the use of a
single display file for any size display. For example, when you are using
subfiles, you can specify 24 records per page for a 27 x 132 display and 22
records per page for a 24 x 80 display.</p>
</div>
<div class="section"><h4 class="sectiontitle">Special cases you might encounter when specifying DSPSIZ</h4><p>You
might encounter the following special cases you when specifying DSPSIZ:</p>
<ul><li>DSPSIZ(*DS3 *DS4). All field locations for display size *DS4 are the same
as for display size *DS3.</li>
<li>All fields of a record can be defined such that none fit on the display
size to which the file is opened. In this case, no fields are displayed. The
record is handled as it does for a larger display where the fields fit. The
record remains active until it is deleted or overlaid. Active records can
be read by your program. The input request is sent to the display device,
and the workstation user must respond to satisfy the request.</li>
<li>All fields of a subfile record must fit within the specified subfile page,
and the complete page must always fit (vertically) on the display size on
which it is displayed at processing time. Specify valid display sizes by conditioning
the SFLPAG (Subfile Page) keyword with display size condition names.</li>
<li>The following records occupy no display space: <ul><li>Records with no fields defined (this is different from none selected)</li>
<li>Records with only hidden, message, or program-to-system fields</li>
<li>Records that have the CLRL keyword specified and that have no input-capable
fields. (These records can remain on the display, but are not recognized by
the <span class="keyword">i5/OS™</span> operating system
for input operations, or they can be cleared through the use of the ERASE
keyword.)</li>
</ul>
<p>For implementation and programming purposes, these records are assumed
to be located at 00 (from line 0 to line 0). On an output operation, any record
located at 00 overlays a record at that location. When an overlap occurs,
the previous record is disregarded and no longer considered active. The new
record at location 00 is active and can be read by your program.</p>
</li>
<li>If two fields in a record format have the same display location (line/position),
they are treated as overlapping fields. Overlapping fields are not displayed
at operation time. The <span class="keyword">i5/OS</span> operating
system checks each field as it is processed to ensure that it does not overlap
a previously processed field. <p>If a field does overlap, it is treated as
an optioned field and not selected. To allow this processing-time checking,
data description specifications must ensure all fields within a record are
in primary location sequence, even when condition names are specified. For
example, assume only one input field is specified for a record format and,
according to the field location specification, this field overlaps a preceding
output field. The workstation user cannot enter any data because the input
field is never displayed.</p>
</li>
</ul>
<div class="note"><span class="notetitle">Note:</span> The primary location sequence as it is seen in the display file
must not be changed by specifying a different location sequence for the secondary
display size. (A severe error occurs and the file is not created.)</div>
</div>
<div class="example"><h4 class="sectiontitle">Example 1</h4><p>The following example shows how to specify
primary and secondary display sizes using the DSPSIZ keyword.</p>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A*
00020A* <strong>1</strong> <strong>2</strong>
00030A DSPSIZ(27 132 24 80)
00040A R RECORDA
00050A FIELDA 10 0 1 2
00060A FIELDB 10 0 1 81
00070A FIELDC 10 0 25 1
A</pre>
<p>In this example, the primary display size <strong>1</strong> is
27 x 132 and the secondary display size <strong>2</strong> is 24 x 80. FIELDB is beyond
position 80 and FIELDC is beyond line 24, so the data description processor
gives them a location of *NOLOC in the expanded source printout for secondary
display size 24 x 80.</p>
<p>If the data description processor assigns *NOLOC
to an input-capable field, that field is processed at run time to the point
of setting up the input buffer data to be returned in the user's input buffer.
The field itself is not displayed. The workstation user cannot enter into
or change these fields. No processing of any kind is done for output-only
fields.</p>
<p><a href="#rzakcmstdfdspsz__excomp1">Figure 2</a> shows a compiler
listing for the above example.</p>
<div class="fignone" id="rzakcmstdfdspsz__excomp1"><a name="rzakcmstdfdspsz__excomp1"><!-- --></a><span class="figcap">Figure 2. Compiler listing</span><br /><img src="rsll911.gif" alt="A figure of the compiler&#xA;listing produced for example 1." /><br /></div>
</div>
<div class="example"><h4 class="sectiontitle">Example 2</h4><p>The following example is another example
of specifying the primary and secondary display sizes using the DSPSIZ keyword.</p>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A DSPSIZ(27 132 *WIDE 24 80 *NORMAL)
00020A R RECORDA
00030A FIELDA 10 0 1 2
00040A FIELDB 10 0 1 81
00050A *NORMAL 1 50
00060A FIELDC 10 0 25 1
00070A *NORMAL 23 1
A</pre>
<p>This example is similar to example 1 in that it specifies
for FIELDB (line 1, position 50) and for FIELDC (line 23, position 1) on the
secondary display size (user-defined as *NORMAL).</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 3</h4><p>The following example shows how to reposition
a field when the file is opened to different display sizes.</p>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A DSPSIZ(24 80 27 132)
00020A R RECORDA
00030A FIELD1 10 0 23 2
00040A
00050A
00060A *DS4 26 2
A</pre>
<p>In this example, FIELD1 has valid locations on both display
sizes. It appears on the next to the last line on each display size.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 4</h4><p>The following example shows that if you
do not specify a display size condition name, the display location of a field
can still be display size dependent as the result of the <em>plus</em> feature
of DDS.</p>
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
00010A DSPSIZ(*DS4 *DS3)
00020A R RECORD1
00030A FIELD1 21 2 70
00040A FIELD2 10 +10
A</pre>
<p>In this example, a line and a position for each field
is calculated for each display size specified on the DSPSIZ keyword. If the
plus value extends the field location beyond position 80, the field location
is dependent on the display size. <a href="#rzakcmstdfdspsz__excomp2">Figure 3</a> is
a compiler listing for the above example.</p>
<div class="fignone" id="rzakcmstdfdspsz__excomp2"><a name="rzakcmstdfdspsz__excomp2"><!-- --></a><span class="figcap">Figure 3. Compiler
list</span><br /><img src="rsll912.gif" alt="A figure of the compiler&#xA;listing produced for example 4." /><br /></div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakcmstkeyent.htm" title="You type the keyword entries that define display files in positions 45 through 80 (functions).">DDS keyword entries for display files (positions 45 through 80)</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><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><a href="pos716.htm" title="Positions 7 through 16 are a multiple-field area in which you can specify option indicators.">Conditioning for display files (positions 7 through 16)</a></div>
</div>
</div>
</body>
</html>