158 lines
9.4 KiB
HTML
158 lines
9.4 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="CAnn (Command Attention) keyword for display files" />
|
||
|
|
<meta name="abstract" content="Use this file- or record-level keyword to specify that the function key specified in the keyword (CA01 through CA24) is available for use." />
|
||
|
|
<meta name="description" content="Use this file- or record-level keyword to specify that the function key specified in the keyword (CA01 through CA24) is available for use." />
|
||
|
|
<meta name="DC.subject" content="CAnn (Command Attention) keyword, Command Attention (CAnn) keyword" />
|
||
|
|
<meta name="keywords" content="CAnn (Command Attention) keyword, Command Attention (CAnn) keyword" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakcmstkeyent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="s36retkeyretcmd.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="rzakcmstdfcann" />
|
||
|
|
<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>CAnn (Command Attention) keyword for display files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakcmstdfcann"><a name="rzakcmstdfcann"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">CAnn (Command Attention) keyword for display files</h1>
|
||
|
|
<div><p>Use this file- or record-level keyword to specify that the function
|
||
|
|
key specified in the keyword (CA01 through CA24) is available for use.</p>
|
||
|
|
<div class="section"><p>It is to be used as a command attention (CA) key. No input data
|
||
|
|
is transmitted from the device. Response indicators 01 through 99 are valid.</p>
|
||
|
|
<p>See
|
||
|
|
the <a href="s36env.htm">System/36 environment considerations for display files</a> topic for special considerations when
|
||
|
|
you specify the CAnn keyword in files that are used in the System/36™ environment.</p>
|
||
|
|
<div class="p">The
|
||
|
|
format of the keyword is: <pre>CAnn[(response-indicator ['text'])]</pre>
|
||
|
|
</div>
|
||
|
|
<div class="p">If you specify this keyword and the display station user
|
||
|
|
presses the specified function key, the following situation happens: <ul><li>All other function key response indicators in the input buffer are set
|
||
|
|
off (hex F0).</li>
|
||
|
|
<li>The response indicator, if specified with the CAnn keyword, is set on
|
||
|
|
(hex F1).</li>
|
||
|
|
<li>The <span class="keyword">i5/OS™</span> data management
|
||
|
|
feedback area is updated.</li>
|
||
|
|
<li>Data already in the input buffer remains unchanged except that the response
|
||
|
|
indicator (if specified) is set on.</li>
|
||
|
|
<li>Control is returned to your program.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>If you specify a response indicator and the key is pressed, the
|
||
|
|
response indicator is set on and returned to your program. (The text information
|
||
|
|
is associated with the indicator and is used by high-level language compilers
|
||
|
|
to help in program documentation.)</p>
|
||
|
|
<p>If the display station user presses
|
||
|
|
a function key and you have not specified it as either a command function
|
||
|
|
(CF) key or a command attention key, the <span class="keyword">i5/OS</span> operating
|
||
|
|
system displays a message to the display station user indicating that the
|
||
|
|
key is not valid at that time.</p>
|
||
|
|
<p>You can use combinations of CA and CF
|
||
|
|
keywords within the same display file, but you cannot specify the same key
|
||
|
|
number as both CA and CF keys. For example, CA02 and CF02 are not valid in
|
||
|
|
the same display file. </p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> File level CA and CF keys are extended to
|
||
|
|
the record level. This must be considered when assigning key numbers. For
|
||
|
|
example, if CA02 is specified at file level and CF02 is specified at record
|
||
|
|
level, CF02 is an error.</div>
|
||
|
|
<p>If you specify a key in the range 1 through
|
||
|
|
9, you must supply the leading zero in the keyword (for example, CA04).</p>
|
||
|
|
<p>Option
|
||
|
|
indicators are valid for this keyword.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Validity checking</h4><p>When the display station user
|
||
|
|
presses a CF key, the data from fields with their MDT set on is placed into
|
||
|
|
the input buffer before validity checking is done. Any errors in the data
|
||
|
|
are then detected, and the appropriate error messages are sent to the display.
|
||
|
|
Because validity checking is not done until after the data is placed in the
|
||
|
|
input buffer, pressing a valid CA key after the CF key can cause incorrect
|
||
|
|
data to be returned to your program. This condition is not a problem as long
|
||
|
|
as your program does not process the input data when the CA key is pressed.</p>
|
||
|
|
<div class="p">This
|
||
|
|
condition can be prevented in either of two ways: <ul><li>Do not allow the use of CA keys. Specify CF keys, which cause validity
|
||
|
|
checking to be done on the data.</li>
|
||
|
|
<li>Do not specify any of the following validity checking keywords if CA keys
|
||
|
|
are allowed: <p>CHECK(M10)<br />
|
||
|
|
CHECK(M11)<br />
|
||
|
|
CHECK(VN)<br />
|
||
|
|
CHECK(VNE)<br />
|
||
|
|
COMP (EQ, NE, LT, NL, GT, NG, LE, GE)<br />
|
||
|
|
RANGE<br />
|
||
|
|
VALUES</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Function keys valid for command attention keys at processing
|
||
|
|
time</h4><p>As a general rule, the last output operation
|
||
|
|
determines which function keys are valid. However, the following list shows
|
||
|
|
exceptions to this rule:</p>
|
||
|
|
<ul><li>When an operation sends no data to the display, the validity of various
|
||
|
|
function keys is not changed. Such operations include: <ul><li>An output operation to a subfile record</li>
|
||
|
|
<li>An update to a subfile record</li>
|
||
|
|
<li>An output operation to a subfile control record that only clears, deletes,
|
||
|
|
or initializes a subfile without displaying the subfile or the subfile control
|
||
|
|
record</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>An output operation that displays an error message by selecting ERRMSG
|
||
|
|
(Error Message) or ERRMSGID (Error Message ID) can also select a CA or CF
|
||
|
|
key to be valid while the error message is displayed.</li>
|
||
|
|
<li>If MNUCNL (Menu Cancel), MNUBARSW (Menu Bar Switch), or SFLDROP (Subfile
|
||
|
|
Drop) is specified for a subfile, the validity of the CA or CF key specified
|
||
|
|
for the SFLDROP keyword is determined by the last output operation. However,
|
||
|
|
as long as the subfile is displayed, the CA or CF key, when valid, acts only
|
||
|
|
as a Drop key.</li>
|
||
|
|
<li>If SFLFOLD (Subfile Fold) is specified for a subfile, the validity of
|
||
|
|
the CA or CF key specified for the SFLFOLD keyword is determined by the last
|
||
|
|
output operation. However, as long as the subfile is displayed, the CA or
|
||
|
|
CF key, when valid, acts only as a Fold key.</li>
|
||
|
|
<li>If two subfiles using SFLDROP or SFLFOLD are displayed at one time, the
|
||
|
|
same function key should be specified on both the SFLDROP and SFLFOLD keywords.
|
||
|
|
If they are different, only the key specified for the most recently displayed
|
||
|
|
subfile is in effect. Pressing the function key affects the subfile containing
|
||
|
|
the cursor. If the cursor is not positioned in a subfile, the function key
|
||
|
|
affects the upper subfile.</li>
|
||
|
|
<li>If two subfiles using SFLENTER (Subfile Enter) are displayed at the same
|
||
|
|
time, the only CA or CF key in effect as an Enter key is the CA or CF key
|
||
|
|
specified for the SFLENTER keyword on the most recently displayed subfile.
|
||
|
|
The cursor position at the time the Enter key is pressed determines which
|
||
|
|
subfile is affected.</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The following keywords function like CA keys: CLEAR, HELP, HOME,
|
||
|
|
and PRINT (with response indicator specified).</div>
|
||
|
|
</div>
|
||
|
|
<div class="example"><h4 class="sectiontitle">Example</h4><p>The following example shows how to specify
|
||
|
|
the CAnn keyword.</p>
|
||
|
|
<pre>|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8
|
||
|
|
00011A CA01(91 'End of Program')
|
||
|
|
00012A CA02(92)
|
||
|
|
00013A CA03
|
||
|
|
A</pre>
|
||
|
|
</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="s36retkeyretcmd.htm" title="Use these record-level keywords to indicate that function keys, command function (CFnn) keys, or command attention (CAnn) keys, which were enabled on a display, should be retained when the record you are defining is displayed.">RETKEY (Retain Function Keys) and RETCMDKEY (Retain Command Keys) keywords</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|