58 lines
4.0 KiB
HTML
58 lines
4.0 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="Monitor for notify messages" />
|
|
<meta name="abstract" content="You can monitor for notify 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 the programs and procedures it calls." />
|
|
<meta name="description" content="You can monitor for notify 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 the programs and procedures it calls." />
|
|
<meta name="DC.subject" content="notify message, monitoring, message, notify" />
|
|
<meta name="keywords" content="notify message, monitoring, message, notify" />
|
|
<meta name="DC.Relation" scheme="URI" content="monmg.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="ntmsg" />
|
|
<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>Monitor for notify messages</title>
|
|
</head>
|
|
<body id="ntmsg"><a name="ntmsg"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Monitor for notify messages</h1>
|
|
<div><p>You can monitor for notify 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 the programs and procedures it calls. </p>
|
|
<div class="section"> <p>Notify messages are sent to tell your procedure or program of
|
|
a condition that is not typically an error. By monitoring for notify messages,
|
|
you can specify an action different from what you would specify if the condition
|
|
had not been detected. Very few IBM-supplied commands send notify messages.</p>
|
|
<p>Monitoring
|
|
for and handling notify messages is similar to monitoring for and handling
|
|
escape messages. The difference is in what happens if you do not monitor
|
|
for and handle notify messages. Notify messages are also percolated from
|
|
procedure to procedure within the boundary of the activation group. If the
|
|
activation group boundary is reached without a <span class="cmdname">Monitor Message (MONMSG)</span> command
|
|
being found for it, the default reply is automatically returned to the sender
|
|
of the notify message and the sender is allowed to continue processing. Unlike
|
|
escape messages, unmonitored notify messages are not considered an indication
|
|
of an error in your procedure or program.</p>
|
|
</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>
|
|
</body>
|
|
</html> |