97 lines
5.7 KiB
HTML
97 lines
5.7 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="Identify the base entry by name" />
|
||
|
|
<meta name="abstract" content="You can identify the base call stack entry by providing the name of the OPM program or ILE procedure running in that entry." />
|
||
|
|
<meta name="description" content="You can identify the base call stack entry by providing the name of the OPM program or ILE procedure running in that entry." />
|
||
|
|
<meta name="DC.subject" content="example, using complex name" />
|
||
|
|
<meta name="keywords" content="example, using complex name" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="callid.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="msgcl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/sndpgmmsg.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="callidbyname" />
|
||
|
|
<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>Identify the base entry by name</title>
|
||
|
|
</head>
|
||
|
|
<body id="callidbyname"><a name="callidbyname"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Identify the base entry by name</h1>
|
||
|
|
<div><p>You can identify the base call stack entry by providing the name
|
||
|
|
of the OPM program or ILE procedure running in that entry. </p>
|
||
|
|
<p>The name provided is either a simple name (one part) or a complex name
|
||
|
|
(two or three parts). Following are descriptions of the simple and complex
|
||
|
|
names: </p>
|
||
|
|
<ul><li>Simple name <p>A simple name is used to identify an OPM program or an
|
||
|
|
ILE procedure. If the simple name you provide is 10 characters or less in
|
||
|
|
length, it is determined by the system that the name is either an OPM program
|
||
|
|
or an ILE procedure. The base is identified as the most recently called OPM
|
||
|
|
program or ILE procedure by that name.</p>
|
||
|
|
<p>If the name is longer than 10
|
||
|
|
characters in length, it is determined by the system that the name is for
|
||
|
|
an ILE procedure (OPM program names cannot be longer than 10 characters).
|
||
|
|
The base is identified as the entry for the most recently called procedure
|
||
|
|
by that name. Entries running OPM programs are not considered.</p>
|
||
|
|
<p>See the
|
||
|
|
first figure for an example of sending a message using a simple
|
||
|
|
name. In this example, CLPROC4 is sending a message to CLPROC2 and CLPROC2
|
||
|
|
is sending a message to CLPGM1.</p>
|
||
|
|
</li>
|
||
|
|
<li>Complex name <p>A complex name consists of two or three parts. They
|
||
|
|
are: </p>
|
||
|
|
<ul><li>module name <p>The module name is the name of the module into which the
|
||
|
|
procedure was compiled.</p>
|
||
|
|
</li>
|
||
|
|
<li>program name <p>The program name is the name of the program into which
|
||
|
|
the procedure was bound.</p>
|
||
|
|
</li>
|
||
|
|
<li>procedure name</li>
|
||
|
|
</ul>
|
||
|
|
<p>When you want to uniquely identify the procedure to which you want
|
||
|
|
to send the message, a complex name can be used in one of the following combinations:</p>
|
||
|
|
<ul><li>procedure name, module name, program name</li>
|
||
|
|
<li>procedure name and module name</li>
|
||
|
|
<li>procedure name and program name <p>You must specify the module name as
|
||
|
|
*NONE.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you use a complex name, the base being identified cannot be running
|
||
|
|
an OPM program.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>See the figure below for an example of sending a message using a complex
|
||
|
|
name. In this example, CLPROC4 is sending a message to CLPROC1 using a two
|
||
|
|
part name consisting of (procedure name, program name).</p>
|
||
|
|
<p>Rather than using the full OPM program name or the full ILE procedure name,
|
||
|
|
you may use partial names.</p>
|
||
|
|
<div class="fignone" id="callidbyname__sndfig3"><a name="callidbyname__sndfig3"><!-- --></a><span class="figcap">Figure 1. Example of using a simple name as a base</span><br /><img src="rbafn565.gif" alt="" /><br /></div>
|
||
|
|
<div class="fignone" id="callidbyname__sndfig4"><a name="callidbyname__sndfig4"><!-- --></a><span class="figcap">Figure 2. Example of using a complex name as a base</span><br /><img src="rbafn566.gif" alt="" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="callid.htm" title="If a CL procedure is to send a message to an OPM program or another ILE procedure, you must identify the call stack entry to which the message is sent.">Identify a call stack entry</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="msgcl.htm" title="Various message types are described in this topic. Use the Send Program Message (SNDPGMMSG) command or the Send User Message (SNDUSRMSG) command to send a message from a CL procedure or program.">Send messages from a CL program</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/sndpgmmsg.htm">Send Program Message (SNDPGMMSG) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|