111 lines
6.9 KiB
HTML
111 lines
6.9 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="task" />
|
|
<meta name="DC.Title" content="CL handling for unmonitored messsages" />
|
|
<meta name="abstract" content="The system provides default monitoring and handling of any messages you do not monitor." />
|
|
<meta name="description" content="The system provides default monitoring and handling of any messages you do not monitor." />
|
|
<meta name="DC.subject" content="default handling, handling, default" />
|
|
<meta name="keywords" content="default handling, handling, default" />
|
|
<meta name="DC.Relation" scheme="URI" content="monmg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="esmsg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="esmsg.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="dfthd" />
|
|
<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>CL handling for unmonitored messsages</title>
|
|
</head>
|
|
<body id="dfthd"><a name="dfthd"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">CL handling for unmonitored messsages</h1>
|
|
<div><p>The system provides default monitoring and handling of any messages
|
|
you do not monitor.</p>
|
|
<div class="section"> <p>Many escape messages can be sent to a procedure that calls commands,
|
|
programs, and procedures. You may want to monitor and handle the escape messages
|
|
which pertain to the function of your procedure. However, you will not want
|
|
to monitor and handle all of the messages.</p>
|
|
<p>Default handling assumes
|
|
that an error has been detected in a procedure. If you are debugging the procedure,
|
|
the message is sent to your display station. You can then enter commands to
|
|
analyze and correct the error. If you are not debugging the procedure, the
|
|
system performs a message percolation function.</p>
|
|
<p>Message percolation
|
|
is a two-step function that does the following: </p>
|
|
<ul><li>Moves the escape message one step earlier in the call stack.</li>
|
|
<li>Checks to see if the procedure has a <span class="cmdname">Monitor Message (MONMSG)</span> command
|
|
for the escape.</li>
|
|
</ul>
|
|
<p>If the procedure has a <span class="cmdname">Monitor Message (MONMSG)</span> command
|
|
for the escape, the message percolation action stops, and the system takes
|
|
the action that is specified by the <span class="cmdname">Monitor Message (MONMSG)</span> command.
|
|
Message percolation continues until either finding a <span class="cmdname">Monitor Message
|
|
(MONMSG)</span> command, or until finding the nearest control boundary.
|
|
This means that the escape message does not percolate across control boundaries.</p>
|
|
<p>The
|
|
function check processing begins by finding the control boundary before finding
|
|
a procedure with a <span class="cmdname">Monitor Message (MONMSG)</span> command which
|
|
applies to the message. The system considers action on the original escape
|
|
exception complete. The system then sends the function check message (CPF9999)
|
|
to the procedure that was the target of the original escape. If that procedure
|
|
has a <span class="cmdname">Monitor Message (MONMSG)</span> for the function check message,
|
|
then it takes the action that is specified by that command. Otherwise, the
|
|
system sends an inquiry message to the workstation operator if the job is
|
|
an interactive job. The workstation operation can reply with one of the following
|
|
replies: </p>
|
|
<dl><dt class="dlterm">R</dt>
|
|
<dd>Retry the failing command in the procedure.</dd>
|
|
<dt class="dlterm">I</dt>
|
|
<dd>Ignore the message. Continue processing at the next command in the procedure.</dd>
|
|
<dt class="dlterm">C</dt>
|
|
<dd>Cancel the procedure and percolate the function check to the next previous
|
|
procedure on the call stack.</dd>
|
|
<dt class="dlterm">D</dt>
|
|
<dd>Dump the call stack entry for the failing procedure, cancel the procedure,
|
|
and percolate the function check to the next previous procedure on the call
|
|
stack. This is the default action if entering no reply, or if the job is a
|
|
batch job.</dd>
|
|
</dl>
|
|
<p>The system does not percolate the function check across
|
|
the control boundary. If any reply causes the function check to move across
|
|
an activation group boundary, this stops further action on the function check.
|
|
The system cancels all procedures up to the activation group boundary, and
|
|
sends the escape message CEE9901 to the prior call stack entry.</p>
|
|
<p>You
|
|
can monitor for function-check escape messages so that you can either: </p>
|
|
<ul><li>Clean up and end the procedure</li>
|
|
<li>Continue with some other aspect of your procedure</li>
|
|
</ul>
|
|
<div class="note"><span class="notetitle">Note:</span> If the message description for the unmonitored escape specifies
|
|
a default action, the default handling program is called before the function
|
|
check message is sent. When the default handling program returns, function
|
|
check processing begins.</div>
|
|
<p>The following diagram shows how CL monitors
|
|
for messages and notifies the workstation user of a function check for default
|
|
handling.</p>
|
|
<div class="fignone"><br /><img src="rv3w196.gif" alt="REQTEXT" /><br /></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="monmg.htm" title="You can monitor for exception messages. Exception messages include escape, notify, and status messages that are sent to your CL procedure's or program's call message queue by the commands in your procedure or program or by commands in another procedure or program. Diagnostic messages cannot be monitored.">Monitor for messages in a CL program or procedure</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="esmsg.htm" title="For each message you create that can be sent as an escape message, you can set up a default message handling action to be used if the message, when sent, is not handled any other way.">Specify default message handling for escape messages</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |