71 lines
4.7 KiB
HTML
71 lines
4.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="Use the command as a base" />
|
||
<meta name="abstract" content="To use the program or procedure that runs the Send Program Message (SNDPGMMSG) command as the base call stack entry, you can use the TOPGMQ parameter." />
|
||
<meta name="description" content="To use the program or procedure that runs the Send Program Message (SNDPGMMSG) command as the base call stack entry, you can use the TOPGMQ parameter." />
|
||
<meta name="DC.subject" content="example, TOPGMQ(*PRV*)" />
|
||
<meta name="keywords" content="example, TOPGMQ(*PRV*)" />
|
||
<meta name="DC.Relation" scheme="URI" content="callid.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="callid.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="callcmdbase" />
|
||
<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>Use the command as a base</title>
|
||
</head>
|
||
<body id="callcmdbase"><a name="callcmdbase"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Use the command as a base</h1>
|
||
<div><p>To use the program or procedure that runs the <span class="cmdname">Send Program
|
||
Message (SNDPGMMSG)</span> command as the base call stack entry, you can
|
||
use the TOPGMQ parameter.</p>
|
||
<div class="p">If the TOPGMQ parameter specifies either TOPGMQ(*SAME *) or TOPGMQ(*PRV *),
|
||
the entry for the procedure using the <span class="cmdname">Send Program Message (SNDPGMMSG)</span> command
|
||
is used as the base. If TOPGMQ(*SAME *) is specified, the procedure will send
|
||
a message to itself. If TOPGMQ(*PRV *) is specified, the procedure will
|
||
send a message to its caller. <div class="note"><span class="notetitle">Note:</span> You should be aware of the following
|
||
information when a procedure sends a message to the caller by specifying TOPGMQ(*PRV *).
|
||
<ul><li>When CLPROC4 and CLPROC2 send a message back to the callers, the message
|
||
does not leave the containing program. The message is sent between procedures
|
||
that are within the same program. If the objective is to send a message to
|
||
CLPGM1 which is the caller of the CLPGM2, specifying TOPGMQ(*PRV *) is
|
||
not the right choice to use.</li>
|
||
<li>When CLPROC1 sends its message back to the caller, the Program Entry Procedure
|
||
is skipped. The message is sent to CLPGM1 even though the caller is the PEP.
|
||
When TOPGMQ(*PRV *) is specified, the PEP entry is <em>not visible</em> and
|
||
not included in the send operation. If TOPGMQ is specified in some other way,
|
||
the PEP is <em>visible</em> to the sender.</li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<p>The figure illustrates the results when CLPROC1, CLPROC2, and CLPROC4 each
|
||
send a message previous of their procedure.</p>
|
||
<div class="fignone" id="callcmdbase__sndfig2"><a name="callcmdbase__sndfig2"><!-- --></a><span class="figcap">Figure 1. Example of TOPGMQ(*PRV *)</span><br /><img src="rbafn564.gif" alt="" /><br /></div>
|
||
<div class="note"><span class="notetitle">Note:</span> The PEP is not visible to (*PRV *), so the message from
|
||
CLPROC1 will be sent to CLPGM1.</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="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>
|
||
</body>
|
||
</html> |