81 lines
5.0 KiB
HTML
81 lines
5.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 status messages" />
|
||
|
|
<meta name="abstract" content="You can monitor for status messages that are sent by the commands in your CL procedure or by the programs or procedures it calls." />
|
||
|
|
<meta name="description" content="You can monitor for status messages that are sent by the commands in your CL procedure or by the programs or procedures it calls." />
|
||
|
|
<meta name="DC.subject" content="status message, monitoring, message, status, description" />
|
||
|
|
<meta name="keywords" content="status message, monitoring, message, status, description" />
|
||
|
|
<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="ssmsg" />
|
||
|
|
<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 status messages</title>
|
||
|
|
</head>
|
||
|
|
<body id="ssmsg"><a name="ssmsg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Monitor for status messages</h1>
|
||
|
|
<div><p>You can monitor for status messages that are sent by the commands
|
||
|
|
in your CL procedure or by the programs or procedures it calls.</p>
|
||
|
|
<div class="section"> <p> Status messages tell your procedure the status of the work performed
|
||
|
|
by the sender. By monitoring for status messages, you can prevent the sending
|
||
|
|
program or procedure from proceeding with any more processing.</p>
|
||
|
|
<p>No message
|
||
|
|
information is stored in a message queue for status messages. Therefore, a
|
||
|
|
status message cannot be received.</p>
|
||
|
|
<p>If a status message is not monitored
|
||
|
|
for, it is percolated like escape and notify messages are. If the activation
|
||
|
|
group boundary is reached without a <span class="cmdname">Monitor Message (MONMSG)</span> command
|
||
|
|
being found, action on the message is considered complete and control is returned
|
||
|
|
to the sender of the message to continue processing. Status messages are often
|
||
|
|
sent to communicate normal conditions that have been detected where processing
|
||
|
|
can continue.</p>
|
||
|
|
<p>Status messages sent to the external message queue are
|
||
|
|
shown on the interactive display, informing the user of a function in progress.
|
||
|
|
For example, the <span class="cmdname">Copy File (CPYF)</span> command sends a message
|
||
|
|
informing the user that a copy operation is in progress.</p>
|
||
|
|
<p>Only predefined
|
||
|
|
messages can be sent as status messages; immediate messages cannot be sent.
|
||
|
|
You can use the system-supplied message ID, CPF9898, and supply message data
|
||
|
|
to send a status message if you do not have an existing message description.</p>
|
||
|
|
<p>When
|
||
|
|
the function is completed, your procedure or program should remove the status
|
||
|
|
message from the interactive display. The message cannot be removed using
|
||
|
|
a command, but sending another status message to *EXT with a blank message
|
||
|
|
gives the appearance of removing the message. The system-supplied message
|
||
|
|
ID CPI9801 can be used for this purpose. When control returns to the i5/OS™ program,
|
||
|
|
the *STATUS message may be cleared from line 24, without sending the CPI9801
|
||
|
|
message. The following example shows a typical application of message IDs
|
||
|
|
CPF9898 and CPI9801: </p>
|
||
|
|
<pre>SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) +
|
||
|
|
MSGDTA('Function xxx being performed') +
|
||
|
|
TOPGMQ(*EXT) MSGTYPE(*STATUS)
|
||
|
|
•
|
||
|
|
• /* Your processing function */
|
||
|
|
•
|
||
|
|
SNDPGMMSG MSGID(CPI9801) MSGF(QCPFMSG) +
|
||
|
|
TOPGMQ(*EXT) MSGTYPE(*STATUS)</pre>
|
||
|
|
</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>
|