77 lines
5.5 KiB
HTML
77 lines
5.5 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="Command label" />
|
||
|
|
<meta name="abstract" content="Command labels identify particular commands for branching purposes in a CL program. Labels can also be used to identify statements in CL programs that are being debugged. They can identify statements used either as breakpoints or as starting and ending statements for tracing purposes." />
|
||
|
|
<meta name="description" content="Command labels identify particular commands for branching purposes in a CL program. Labels can also be used to identify statements in CL programs that are being debugged. They can identify statements used either as breakpoints or as starting and ending statements for tracing purposes." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6comparts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6uniquenamerules.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6nameincom.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6commnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6names.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6pathnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6snames.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="rbam6label" />
|
||
|
|
<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>Command label</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbam6label"><a name="rbam6label"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Command label</h1>
|
||
|
|
<div><p>Command labels identify particular commands for branching purposes
|
||
|
|
in a CL program. Labels can also be used to identify statements in CL programs
|
||
|
|
that are being debugged. They can identify statements used either as breakpoints
|
||
|
|
or as starting and ending statements for tracing purposes.</p>
|
||
|
|
<div class="section"><p> The label is typed just before the command name. The standard
|
||
|
|
rules for specifying simple names (*SNAME) apply. The label is immediately
|
||
|
|
followed by a colon. Blanks are allowed, though not required, between the
|
||
|
|
colon and the command name. The label can contain as many as 10 characters,
|
||
|
|
in addition to the colon. START: and TESTLOOP: are examples of command labels.</p>
|
||
|
|
<p>Command
|
||
|
|
labels are not required, but a label can be placed on any command. For labels
|
||
|
|
that are placed on commands that cannot be run (for example, the <span class="cmdname">Declare
|
||
|
|
CL Variable (DCL)</span> command), when the program branches to that label,
|
||
|
|
the next command following the label is run. If the command following the
|
||
|
|
label cannot be run, the program will move to the next command that can be
|
||
|
|
run. Similarly, you can specify only one label on a line. If a command is
|
||
|
|
not located on that line, the program will jump to the next command that can
|
||
|
|
be run.</p>
|
||
|
|
<p>To specify multiple labels, each additional label must be on
|
||
|
|
a separate line preceding the command as shown:</p>
|
||
|
|
<pre>LABEL1:
|
||
|
|
LABEL2: CMDX</pre>
|
||
|
|
<p>No continuation character (+ or -) is allowed on the preceding
|
||
|
|
label lines.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbam6comparts.htm" title="The parts of a command include a command label (optional), a command name (mnemonic), and one or more parameters. The parameter includes a keyword and a value.">Command parts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbam6uniquenamerules.htm" title="This describes additional rules involving special characters for object naming.">Additional rules for unique names</a></div>
|
||
|
|
<div><a href="rbam6nameincom.htm" title="You can use only specific characters for naming within commands.">Naming within commands</a></div>
|
||
|
|
<div><a href="rbam6commnames.htm" title="This describes the rules for creating communication names.">Communication names (*CNAME)</a></div>
|
||
|
|
<div><a href="rbam6names.htm" title="This describes the rules for creating basic names and basic names in quoted form.">Names (*NAME)</a></div>
|
||
|
|
<div><a href="rbam6pathnames.htm" title="A path name is a character string that can be used to locate objects in the integrated file system.">Path names (*PNAME)</a></div>
|
||
|
|
<div><a href="rbam6snames.htm" title="This describes the difference between simple names and basic names, and the circumstances when simple names should be used.">Simple Names (*SNAME)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|