145 lines
11 KiB
HTML
145 lines
11 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="Define message descriptions" />
|
|
<meta name="abstract" content="Predefined messages are stored in a message file." />
|
|
<meta name="description" content="Predefined messages are stored in a message file." />
|
|
<meta name="DC.subject" content="immediate message, predefined message, message, handling, type, immediate, predefined, IBM-supplied file, message queue, file, IBM-supplied, IBM-supplied message file, message queue, creating, working with, message file, changing, message description, adding, message description, removing, sending, break message, program message, user message, function, displaying, command options, inquiry message, informational message, informational, inquiry, completion, notify, request, diagnostic, status, definition, reply, escape, completion message, notify message, defining, request message, diagnostic message, status message, reply message, escape message" />
|
|
<meta name="keywords" content="immediate message, predefined message, message, handling, type, immediate, predefined, IBM-supplied file, message queue, file, IBM-supplied, IBM-supplied message file, message queue, creating, working with, message file, changing, message description, adding, message description, removing, sending, break message, program message, user message, function, displaying, command options, inquiry message, informational message, informational, inquiry, completion, notify, request, diagnostic, status, definition, reply, escape, completion message, notify message, defining, request message, diagnostic message, status message, reply message, escape message" />
|
|
<meta name="DC.Relation" scheme="URI" content="wmsgs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="cmsgf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="amsgf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="vmsgf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="smfs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="monms.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="allor.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="check.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../clfinder/finder.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="msghd" />
|
|
<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>Define message descriptions</title>
|
|
</head>
|
|
<body id="msghd"><a name="msghd"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Define message descriptions</h1>
|
|
<div><p>Predefined messages are stored in a message file.</p>
|
|
<div class="section"> <p>You can create your own message files and message descriptions.
|
|
By creating predefined messages, you can use the same message in several procedures
|
|
or programs but define it only once. You can also change and translate predefined
|
|
messages into languages other than English (based on the user viewing the
|
|
messages) without affecting the procedures and programs that use them. If
|
|
the messages were defined in the procedure or program, the module
|
|
or program would have to be recompiled when you change the messages.</p>
|
|
<p>In
|
|
addition to creating your own messages and message files, the system message
|
|
handling function allows you to: </p>
|
|
<ul><li>Create and change message queues (<span class="cmdname">Create Message Queue (CRTMSGQ)</span>, <span class="cmdname">Change
|
|
Message Queue (CHGMSGQ)</span>, and <span class="cmdname">Work with Message Queues (WRKMSGQ)</span> commands)</li>
|
|
<li>Create and change message files (<span class="cmdname">Create Message File (CRTMSGF)</span>, <span class="cmdname">Change
|
|
Message File (CHGMSGF)</span> commands)</li>
|
|
<li>Add message descriptions (<span class="cmdname">Add Message Description (ADDMSGD)</span> command)</li>
|
|
<li>Change message descriptions (<span class="cmdname">Change Message Description (CHGMSGD)</span> command)</li>
|
|
<li>Remove message descriptions (<span class="cmdname">Remove Message Description (RMVMSGD)</span> command)</li>
|
|
<li>Send immediate messages (<span class="cmdname">Send Message (SNDMSG)</span>, <span class="cmdname">Send
|
|
Break Message (SNDBRKMSG)</span>, <span class="cmdname">Send Program Message (SNDPGMMSG)</span>,
|
|
and <span class="cmdname">Send User Message (SNDUSRMSG)</span> commands)</li>
|
|
<li>Display messages in a message queue (<span class="cmdname">Display Messages (DSPMSG)</span> and <span class="cmdname">Work
|
|
with Messages (WRKMSG)</span>) </li>
|
|
<li>Display message descriptions in a message file (<span class="cmdname">Display Message
|
|
Description (DSPMSGD)</span> and <span class="cmdname">Work with Message Descriptions
|
|
(WRKMSGD)</span> commands)</li>
|
|
<li>Use a CL procedure or program to: <ul><li>Send a message to a workstation user or the system operator (<span class="cmdname">Send
|
|
User Message (SNDUSRMSG)</span> command)</li>
|
|
<li>Send a message to a message queue (<span class="cmdname">Send Program Message (SNDPGMMSG)</span> command)</li>
|
|
<li>Receive a message from a message queue (<span class="cmdname">Receive Message (RCVMSG)</span> command)</li>
|
|
<li>Send a reply for a message to a message queue (<span class="cmdname">Send Reply (SNDRPY)</span> command)</li>
|
|
<li>Retrieve a message from a message file (<span class="cmdname">Retrieve Message (RTVMSG)</span> command)</li>
|
|
<li>Remove a message from a message queue (<span class="cmdname">Remove Message (RMVMSG)</span> command)</li>
|
|
<li>Monitor for escape, notify, and status messages that are sent to a call
|
|
message queue (<span class="cmdname">Monitor Message (MONMSG)</span> command)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Use the system reply list to specify the replies for predefined inquiry
|
|
messages sent by a job (<span class="cmdname">Add Reply List Entry (ADDRPYLE)</span>, <span class="cmdname">Change
|
|
Reply List Entry (CHGRPYLE)</span>, <span class="cmdname">Remove Reply List Entry (RMVRPYLE)</span>,
|
|
and <span class="cmdname">Work with Reply List Entry (WRKRPYLE)</span> commands)</li>
|
|
</ul>
|
|
<p>When a message is sent, it is defined as one of the following types:
|
|
</p>
|
|
<ul><li>Informational (*INFO). A message that conveys information about the condition
|
|
of a function.</li>
|
|
<li>Inquiry (*INQ). A message that conveys information but also asks for
|
|
a reply.</li>
|
|
<li>Notify (*NOTIFY). A message that describes a condition for which a procedure
|
|
or program requires corrective action or a reply from its calling procedure
|
|
or program. A procedure or program can monitor for the arrival of notify messages
|
|
from the programs or procedures it calls.</li>
|
|
<li>Reply (*RPY). A message that is a response to a received inquiry or notify
|
|
message.</li>
|
|
<li>Sender's copy (*COPY). A copy of an inquiry or notify message that is
|
|
kept by the sender.</li>
|
|
<li>Request (*RQS). A message that requests a function from the receiving
|
|
procedure or program. (For example, a CL command is a request message.)</li>
|
|
<li>Completion (*COMP). A message that conveys completion status of work.</li>
|
|
<li>Diagnostic (*DIAG). A message about errors in the processing of a system
|
|
function, in an application program, or in input data.</li>
|
|
<li>Status (*STATUS). A message that describes the status of the work done
|
|
by a procedure or program. A procedure or program can monitor for the arrival
|
|
of status messages from the program or procedure it calls, but the status
|
|
message will not appear in a job log. Status messages sent to the external
|
|
message queue (*EXT) are shown at the display station and can be used to inform
|
|
the display station user of an operation in progress.</li>
|
|
<li>Escape (*ESCAPE). A message that describes a condition for which a procedure
|
|
or program must end abnormally. A procedure or program can monitor for the
|
|
arrival of escape messages from the program or procedure it calls or from
|
|
the machine. Control does not return to the sending program after an escape
|
|
message is sent.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="cmsgf.htm">Create a message file</a></strong><br />
|
|
To create your own predefined messages, you must first create the message file into which the messages are to be placed.</li>
|
|
<li class="ulchildlink"><strong><a href="amsgf.htm">Add messages to a file</a></strong><br />
|
|
You use the <span class="cmdname">Add Message Description (ADDMSGD)</span> command
|
|
to describe your predefined messages and to add them to the message file you
|
|
created.</li>
|
|
<li class="ulchildlink"><strong><a href="vmsgf.htm">View messages</a></strong><br />
|
|
You can view or print messages and exception messages.</li>
|
|
<li class="ulchildlink"><strong><a href="smfs.htm">Search for message file</a></strong><br />
|
|
The system searches for the message file from which the message description is retrieved.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="wmsgs.htm" title="This discusses some of the ways that messages can be used to communicate between users and programs.">Messages</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="allor.htm" title="Objects are allocated on the system to guarantee integrity and to promote the highest possible degree of concurrency.">Allocate resources</a></div>
|
|
<div><a href="check.htm" title="Before attempting to use an object in a program, check to determine if the object exists and if you have the authority to use it.">Check for the existence of an object</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="monms.htm" title="The Monitor Message (MONMSG) command is used to monitor for escape, notify, or status messages sent to the call stack of the procedure in which the Monitor Message (MONMSG) command is used.">Monitor Message (MONMSG) Command</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../clfinder/finder.htm">CL command finder</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |