101 lines
5.9 KiB
HTML
101 lines
5.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="Handle unmonitored messages" />
|
||
|
|
<meta name="abstract" content="In an interactive debug job, when a function check occurs, the system provides default handling and gives you control instead of stopping the program." />
|
||
|
|
<meta name="description" content="In an interactive debug job, when a function check occurs, the system provides default handling and gives you control instead of stopping the program." />
|
||
|
|
<meta name="DC.subject" content="display, unmonitored message breakpoint, default handling, unmonitored message while testing, unmonitored, default handling, unmonitored message, handling, see='message queue'.message, breakpoint display, message, default handling while testing, testing, canceling request during, ENDRQS (End Request) command, End Request (ENDRQS) command, command, CL, ENDRQS (End Request), End Request (ENDRQS), request, ending, canceling, request while testing, call stack, removing request in error, stack, call" />
|
||
|
|
<meta name="keywords" content="display, unmonitored message breakpoint, default handling, unmonitored message while testing, unmonitored, default handling, unmonitored message, handling, see='message queue'.message, breakpoint display, message, default handling while testing, testing, canceling request during, ENDRQS (End Request) command, End Request (ENDRQS) command, command, CL, ENDRQS (End Request), End Request (ENDRQS), request, ending, canceling, request while testing, call stack, removing request in error, stack, call" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="opm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/endrqs.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="unmsg" />
|
||
|
|
<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>Handle unmonitored messages</title>
|
||
|
|
</head>
|
||
|
|
<body id="unmsg"><a name="unmsg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Handle unmonitored messages</h1>
|
||
|
|
<div><p>In an interactive debug job, when a function check occurs, the
|
||
|
|
system provides default handling and gives you control instead of stopping
|
||
|
|
the program. </p>
|
||
|
|
<div class="section"> <p>Normally, if a program receives an unmonitored escape message,
|
||
|
|
the system sends the function check message (CPF9999) to the program's program
|
||
|
|
message queue and the program stops processing. However, HLL program compilers
|
||
|
|
may insert monitors for the function check message or for messages that may
|
||
|
|
occur in the program. (An inquiry message is sent to the program messages
|
||
|
|
display.) This allows you to end the program the way you want. In an interactive
|
||
|
|
debug job, when a function check occurs, the system displays the following
|
||
|
|
on the unmonitored message display: </p>
|
||
|
|
<ul><li>The message</li>
|
||
|
|
<li>The MI instruction number and HLL statement identifier, if available,
|
||
|
|
to which the message was sent</li>
|
||
|
|
<li>The name and recursion level of the program to which the message was sent</li>
|
||
|
|
</ul>
|
||
|
|
<p>The following is an example of an unmonitored message breakpoint display:
|
||
|
|
</p>
|
||
|
|
<pre class="screen"> Display Unmonitored Message Breakpoint
|
||
|
|
|
||
|
|
Statement/Instruction . . . . . . . : 440 /0077
|
||
|
|
Program . . . . . . . . . . . . . . : TETEST
|
||
|
|
Recursion level . . . . . . . . . . : 1
|
||
|
|
|
||
|
|
Errors occurred on command.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
Press Enter to continue.
|
||
|
|
|
||
|
|
F3=Exit program F10=Command Entry
|
||
|
|
</pre>
|
||
|
|
<p>You can try to isolate the source of the error by using the testing
|
||
|
|
functions. However, the original request in error is still stopped at the
|
||
|
|
point where the error occurred. To remove the request in error from the call
|
||
|
|
stack, you must use the <span class="cmdname">End Request (ENDRQS)</span> command or
|
||
|
|
press F3 when the unmonitored message breakpoint display is shown. You can
|
||
|
|
let the usual function check processing continue by pressing the Enter key
|
||
|
|
when the unmonitored message breakpoint display is shown. If you press F10
|
||
|
|
to call the command entry display, you must press F3 to return to the unmonitored
|
||
|
|
message breakpoint display.</p>
|
||
|
|
<p>The following shows how a <span class="cmdname">End Request
|
||
|
|
(ENDRQS)</span> command works:</p>
|
||
|
|
<br /><img src="rbafn533.gif" alt="Illustrates how a ENDRQS command works." /><br /> <p>Program calls
|
||
|
|
are destroyed when a <span class="cmdname">End Request (ENDRQS)</span> command is entered.
|
||
|
|
(In the previous diagram, the program call of PGMA is destroyed.)</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="opm.htm" title="You can debug your OPM programs by using testing functions.">Debug OPM programs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../cl/endrqs.htm">End Request (ENDRQS) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|