ibm-information-center/dist/eclipse/plugins/i5OS.ic.rbam6_5.4.0.1/dqnam.htm

80 lines
5.3 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="task" />
<meta name="DC.Title" content="Define a qualified name" />
<meta name="abstract" content="A qualified name is the name of an object preceded by the name of the library in which the object is stored." />
<meta name="description" content="A qualified name is the name of an object preceded by the name of the library in which the object is stored." />
<meta name="DC.subject" content="defining, qualified name, command, CL, command definition, statement, QUAL, use of qualified name, QUAL (Qualifier) statement, use, Qualifier (QUAL) statement, parameter, using qualified name, passing, parameter value to CPP, qualifier (QUAL) statement, example" />
<meta name="keywords" content="defining, qualified name, command, CL, command definition, statement, QUAL, use of qualified name, QUAL (Qualifier) statement, use, Qualifier (QUAL) statement, parameter, using qualified name, passing, parameter value to CPP, qualifier (QUAL) statement, example" />
<meta name="DC.Relation" scheme="URI" content="dflst.htm" />
<meta name="DC.Relation" scheme="URI" content="defqlclhll.htm" />
<meta name="DC.Relation" scheme="URI" content="qnrx.htm" />
<meta name="DC.Relation" scheme="URI" content="defpr.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="dqnam" />
<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>Define a qualified name</title>
</head>
<body id="dqnam"><a name="dqnam"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Define a qualified name</h1>
<div><p>A qualified name is the name of an object preceded by the name
of the library in which the object is stored. </p>
<div class="section"> <p>If a parameter value or list item is a qualified name, you must
define the name separately using Qualifier (QUAL) statements. Each part of
the qualified name must be defined with a QUAL statement. The parts of a qualified
name must be described in the order in which they occur in the qualified name.
You must specify *NAME or *GENERIC in the first QUAL statement. The associated
PARM or ELEM statement must identify the label that refers to the first QUAL
statement for the qualified name.</p>
<p>The following command definition statements
define the most common qualified name. A qualified object consists of the
library name which contains an object followed by the name of the object itself.
The QUAL statements must appear in the order in which they are to occur in
the qualified name.</p>
<br /><img src="rbafn518.gif" alt="This command definition statements define the most common qualified name. A qualified object consists of the library name which contains an object followed by the name of the object itself. The QUAL statements must appear in the order in which they are to occur in the qualified name." /><br /><p>Many of the parameters that
can be specified for the QUAL statement are the same as those described for
the PARM statement. However, only the following values can be
specified for the TYPE parameter: </p>
<ul><li>*NAME</li>
<li>*GENERIC</li>
<li>*CHAR</li>
<li>*INT2</li>
<li>*INT4</li>
</ul>
<p>When a qualified name is passed to the command processing program,
the format varies depending on whether you are using CL or HLL, or REXX.</p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="defqlclhll.htm">Use CL or HLL for a qualified name</a></strong><br />
This describes the format in a qualified name is passed when a command is run using CL or a high-level language.</li>
<li class="ulchildlink"><strong><a href="qnrx.htm">Use REXX for a qualified name</a></strong><br />
This describes the format in a qualified name is passed when a command is run using REXX.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dflst.htm" title="You can define a parameter to accept a list of values instead of just a single value.">Define lists for parameters</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="defpr.htm" title="To define a parameter, you must use the PARM statement.">Define parameters</a></div>
</div>
</div>
</body>
</html>