193 lines
11 KiB
HTML
193 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="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="Usage for display files (position 38)" />
|
||
|
|
<meta name="abstract" content="Use this position to specify that a named field is an output-only, input-only, input/output (both), hidden, program-to-system, or message field." />
|
||
|
|
<meta name="description" content="Use this position to specify that a named field is an output-only, input-only, input/output (both), hidden, program-to-system, or message field." />
|
||
|
|
<meta name="DC.subject" content="usage positional entry" />
|
||
|
|
<meta name="keywords" content="usage positional entry" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakcmstpsnent.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="pos38" />
|
||
|
|
<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>Usage for display files (position 38)</title>
|
||
|
|
</head>
|
||
|
|
<body id="pos38"><a name="pos38"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Usage for display files (position 38)</h1>
|
||
|
|
<div><p>Use this position to specify that a named field is an output-only,
|
||
|
|
input-only, input/output (both), hidden, program-to-system, or message field.</p>
|
||
|
|
<p>Make no entry in this position for a constant (unnamed) field.</p>
|
||
|
|
<div class="section"><p>The valid entries for display files are:</p>
|
||
|
|
<dl><dt><strong>Entry </strong></dt>
|
||
|
|
<dd><strong>Meaning</strong></dd>
|
||
|
|
<dt class="dlterm">Blank or O</dt>
|
||
|
|
<dd>Output only <p>Output-only fields pass data from a program to the device
|
||
|
|
when the program writes a record to a display. You can use the DFT (Default)
|
||
|
|
keyword to specify an initial value for a named output field if you also specify
|
||
|
|
the OVRDTA keyword for the field. If the OVRDTA keyword is not in effect,
|
||
|
|
the initial value for the field is used. If the OVRDTA keyword is in effect,
|
||
|
|
the data for the field is used. If the OVRDTA keyword is in effect, the data
|
||
|
|
for the field is taken from the output buffer.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">I</dt>
|
||
|
|
<dd>Input only <p>Input-only fields pass data from the device to a program
|
||
|
|
when the program reads a record. Input fields can be initialized with a default
|
||
|
|
value (specified on the DFT keyword). If you do not change the field and the
|
||
|
|
field is selected for input, the default value is passed to the program. Input
|
||
|
|
fields are, by default, underlined on the display. You can use the Change
|
||
|
|
Input Default (CHGINPDFT) keyword or the Display Attribute Underline (DSPATR(UL))
|
||
|
|
keyword to prevent underlining.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">B</dt>
|
||
|
|
<dd>Input/output (both) <p>Input/output fields are passed from a program when
|
||
|
|
the program writes a record to the display and are passed to a program when
|
||
|
|
the program reads a record from the display and the field is selected for
|
||
|
|
input. Input/output fields are typically used when the program displays data
|
||
|
|
that you can change. An initial value can be specified for the field on the
|
||
|
|
DFT keyword. When DFT is specified, the OVRDTA keyword is also required and
|
||
|
|
indicates whether the data displayed in the field is taken from the output
|
||
|
|
buffer (OVRDTA in effect) or from the DFT keyword (OVRDTA not in effect).
|
||
|
|
Input/output fields are, by default, underlined on the display.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">H</dt>
|
||
|
|
<dd>Hidden (special input/output field) <p>A hidden field is a named, numeric,
|
||
|
|
alphanumeric, date. time, or timestamp field that does not appear on the display.
|
||
|
|
Your program can send data to the field with an output operation, and it can
|
||
|
|
retrieve data from the field with an input operation, but you cannot see or
|
||
|
|
change the contents of the field.</p>
|
||
|
|
<div class="p">The following rules apply to hidden
|
||
|
|
fields: <ul><li>Hidden fields are always named.</li>
|
||
|
|
<li>Locations are not valid for hidden fields.</li>
|
||
|
|
<li>Specify length, data type, and decimal positions as
|
||
|
|
you do for other named fields.</li>
|
||
|
|
<li>You can specify more than one hidden field for a display file.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Since hidden fields are not displayed, they are not considered
|
||
|
|
input-capable or output-capable fields, even though your program can send
|
||
|
|
and receive data from them.</p>
|
||
|
|
<p> The DATFMT and DATSEP keywords can be used
|
||
|
|
on a date hidden field, and the TIMFMT and TIMSEP keywords can be used on
|
||
|
|
a time hidden field. However, no formatting is done by the system when the
|
||
|
|
record containing the hidden date or time field is written or read.</p>
|
||
|
|
<p>Hidden
|
||
|
|
fields are useful in applications involving subfiles. For example, a subfile
|
||
|
|
record can contain record key information in a hidden field. You cannot see
|
||
|
|
the hidden field, but the field is returned to the program with the subfile
|
||
|
|
record so that the program can return the record to the database.</p>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">M</dt>
|
||
|
|
<dd>Message (special output field) <p>A message field is a named, output-only,
|
||
|
|
character field.</p>
|
||
|
|
<div class="p">The following rules apply to message fields: <ul><li>You can use option indicators to select message fields, but during processing,
|
||
|
|
only one message can be displayed at a time. The message from the first message
|
||
|
|
field selected is displayed, and all others are ignored for that operation.</li>
|
||
|
|
<li>When a message field displays, all other fields you specify for that record
|
||
|
|
are processed in the normal manner. The device goes into an error condition
|
||
|
|
(locked keyboard, blinking cursor, and message displayed with the high intensity
|
||
|
|
(HI) display attribute). When you press the Reset key, normal processing continues.</li>
|
||
|
|
<li>The text of the message is established when your program moves a value
|
||
|
|
to the message field.</li>
|
||
|
|
<li>The location of the message on the display is the message line (the last
|
||
|
|
line on the display unless the MSGLOC keyword is in effect).</li>
|
||
|
|
<li>The length you specify for the message field should be less than 79 positions
|
||
|
|
for 24 x 80 workstations, or less than 131 positions for the 27 x 132 workstation.
|
||
|
|
Any message text that occupies more than 78 positions on the 24 x 80 workstations,
|
||
|
|
or more than 130 positions on a 27 x 132 workstation is truncated to fit the
|
||
|
|
message line.</li>
|
||
|
|
<li>The Help key is not supported for message fields. Message help for the
|
||
|
|
message is not displayed when Help is pressed.</li>
|
||
|
|
<li>Only the following keywords are valid for a message field:
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="void" border="0" rules="none"><tbody><tr><td valign="top" width="50%"><p>ALIAS<br />
|
||
|
|
INDTXT<br />
|
||
|
|
OVRDTA</p>
|
||
|
|
</td>
|
||
|
|
<td valign="top" width="50%"><p>REFFLD<br />
|
||
|
|
TEXT</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</li>
|
||
|
|
<li>You cannot specify M in position 38 for a field if the field is part of
|
||
|
|
the subfile record format.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> It is valid to send an input operation to a record that contains
|
||
|
|
no input-capable fields. This permits pressing a function key as a response
|
||
|
|
to an output record.</div>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">P</dt>
|
||
|
|
<dd>Program-to-system (special output field) <p>A program-to-system field
|
||
|
|
is a named, numeric, or alphanumeric output-only field that is used to pass
|
||
|
|
data between the program and the system; it does not appear on the display.
|
||
|
|
Your program can send data to the field with an output operation, but the
|
||
|
|
workstation user cannot see the contents of the field. Since program-to-system
|
||
|
|
fields are not displayed, they are not considered output-capable fields, even
|
||
|
|
though the program can send data to them.</p>
|
||
|
|
<div class="p">The following rules apply
|
||
|
|
to program-to-system fields in display files: <ul><li>Program-to-system fields are always named.</li>
|
||
|
|
<li>Locations are not valid for program-to-system fields.</li>
|
||
|
|
<li>Specify length, data-type, and decimal positions as
|
||
|
|
you do for other named fields.</li>
|
||
|
|
<li>The program-to-system field must be specified as a parameter on a CHCACCEL,
|
||
|
|
CHCCTL, CHKMSGID, CHOICE, ERRMSGID, GRDATR, GRDBOX, GRDCLR, GRDLIN, HTML,
|
||
|
|
MNUBARCHC, MSGID, PSHBTNCHC, SFLCHCCTL, SFLMSGID, SFLSIZ, WDWTITLE, or WINDOW
|
||
|
|
keyword within the same record format. The P-usage field is not valid as a
|
||
|
|
parameter on any other keyword. A severe error is sent if the field is not
|
||
|
|
specified on at least one of these keywords.</li>
|
||
|
|
<li>Unlike the P-usage fields in ICF files, P-usage fields in display files
|
||
|
|
can appear anywhere in the buffer. In ICF files, P-fields must be specified
|
||
|
|
after all the data fields (B-usage fields).</li>
|
||
|
|
<li>A P-usage field can be specified as the message-identifier, message-file,
|
||
|
|
or library name on a MSGID keyword, provided the field is defined with the
|
||
|
|
proper attributes, such as length.</li>
|
||
|
|
<li>The record containing the P-usage field must be written before the data
|
||
|
|
contained within the P-usage field is known to the system.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>The only keywords allowed on a program-to-system field are:</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="90%" frame="void" border="0" rules="none"><tbody><tr><td valign="top" width="50%"><p>ALIAS<br />
|
||
|
|
INDTXT</p>
|
||
|
|
</td>
|
||
|
|
<td valign="top" width="50%"><p>TEXT<br />
|
||
|
|
REFFLD</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<div class="note"><span class="notetitle">Notes:</span> <ol><li>Input-only and input/output fields are input-capable fields.</li>
|
||
|
|
<li>Output-only and input/output fields are output-capable fields.</li>
|
||
|
|
<li>Output-only is the default if you leave the position blank.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakcmstpsnent.htm" title="Use this information to specify the first 44 positions of the data description specifications (DDS) form for display files.">Positional entries for display files (positions 1 through 44)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|