ibm-information-center/dist/eclipse/plugins/i5OS.ic.dds_5.4.0.1/rbafpmstsyntax.htm

122 lines
7.2 KiB
HTML
Raw Permalink 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="Rules for DDS keywords and parameter values" />
<meta name="abstract" content="When you code DDS entries, follow these conventions for entering keywords and their parameters." />
<meta name="description" content="When you code DDS entries, follow these conventions for entering keywords and their parameters." />
<meta name="DC.subject" content="rules for keywords and parameter values, syntax, keywords and parameter values, rules" />
<meta name="keywords" content="rules for keywords and parameter values, syntax, keywords and parameter values, rules" />
<meta name="DC.Relation" scheme="URI" content="coderules.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="syntax" />
<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>Rules for DDS keywords and parameter values</title>
</head>
<body id="syntax"><a name="syntax"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Rules for DDS keywords and parameter values</h1>
<div><p>When you code DDS entries, follow these conventions for entering
keywords and their parameters.</p>
<p>The DDS coding syntax for keywords and their parameter values is similar
to the CL syntax. The DDS syntax rules are:</p>
<ul><li>Code all DDS entries in uppercase except for character values enclosed
in single quotation marks and extended names enclosed in quotation marks.</li>
<li>Code keywords on the same (or subsequent) line as the entry with which
they are associated.</li>
<li>Separate multiple keywords with at least one blank. Parameter values for
keywords must be enclosed in parentheses. The initial parenthesis must immediately
follow the keyword. For example: <pre>KEYWORD(VALUE)</pre>
<p>This
rule is slightly different from that in control language. When coding control
language, the parameter values can be positional. Syntax for DDS requires
that the keyword be specified, except when specifying either a constant or
the parameter value for the DFT (Default) keyword.</p>
</li>
<li>Separate multiple parameter values for the same keyword with at least
one blank. For example: <pre>KEYWORD(VALUEA VALUEB)</pre>
</li>
<li>A parameter expression consists of a set of values surrounded by left
and right parentheses. Generally, the first value within the expression is
a special value. The special value begins with an asterisk and must immediately
follow the left parenthesis. One or more parameter values follow the special
value. Separate the special value and the parameter value(s) by at least one
blank. The last parameter value must immediately precede the right parenthesis.
A parameter expression represents one parameter value and must be separated
from other parameter values by at least one blank. For example: <pre>KEYWORD(VALUEA (*special-value VALUEB) VALUEC)</pre>
</li>
<li>Use single quotation marks to enclose character values. Numeric values
appear without single quotation marks. See the coding examples for COMP, RANGE,
and VALUES keywords. Character values can appear in two places in the syntax:
<ul><li>As a parameter value for some keywords. For example, TEXT (all types
of files) and COLHDG (database files) require character strings as text description.
Other keywords, such as CAnn and CFnn, use character strings as text descriptions
for response indicators.</li>
<li>As the default value of a constant field (either with or without the DFT
keyword) for display and printer files only. In display files, a character
constant can also be specified for named fields. Even if you do not specify
the DFT keyword, specifying a character constant implies the DFT keyword.</li>
</ul>
</li>
<li>To specify a single quotation mark within a character string, specify
two single quotation marks so that one single quotation mark appears in the
output. For example: <pre>KEYWORD('Customer''s name')</pre>
<div class="p">appears
as <pre>Customer's name</pre>
</div>
</li>
<li>Use a plus (+) or a minus () sign as a continuation character when a
keyword and its parameter values do not fit on a single line. The sign must
be the last nonblank character in the functions field. A single statement
can be continued for a maximum of 5000 character positions. <ul><li>A <strong>minus () sign</strong> means that the continuation begins
in position 45 of the next line (the first position in the functions field).</li>
<li>A <strong>plus (+) sign</strong> means that the continuation begins with the first
nonblank (first significant) character in the functions field on the next
line.</li>
</ul>
<p>If you specify a continuation character within a parameter value,
any blanks preceding the continuation character are included in the parameter
value.</p>
</li>
<li>Specify a plus (+) sign as the last nonblank character on a line to continue
conditioning for keywords specified on the next line. This is helpful when
a condition includes several option indicators and applies to several keywords.</li>
<li>The operating system continues a DDS statement until you specify one of
the following fields: <ul><li>A record format name (R in position 17).</li>
<li>A field specification (field name or location).</li>
<li>For physical or logical files, a key field specification (K in position
17).</li>
<li>For logical files, a select or omit specification (S or O in position
17).</li>
<li>For join logical files, a join specification (J in position 17).</li>
<li>For display files, a help specification (H in position 17).</li>
<li>For device files, an option indicator or condition name that conditions
a keyword, field, or field location.</li>
<li>The maximum length of a DDS statement (5000 characters). The fixed length
entries (positions 1 through 44) of the first line are included in the statement,
so the maximum space available for keywords is 4956.</li>
</ul>
</li>
</ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="coderules.htm" title="When you describe data attributes with DDS, you need to be aware of specific coding rules, naming conventions, and terminology.">DDS coding rules, conventions, and terms</a></div>
</div>
</div>
</body>
</html>