ibm-information-center/dist/eclipse/plugins/i5OS.ic.rbam6_5.4.0.1/intmsg.htm

90 lines
5.6 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="concept" />
<meta name="DC.Title" content="Messages" />
<meta name="abstract" content="A message is a communication sent from one user, program, or procedure to another." />
<meta name="description" content="A message is a communication sent from one user, program, or procedure to another." />
<meta name="DC.subject" content="message description, definition, message, predefined, description, predefined message, message, immediate, immediate" />
<meta name="keywords" content="message description, definition, message, predefined, description, predefined message, message, immediate, immediate" />
<meta name="DC.Relation" scheme="URI" content="intro.htm" />
<meta name="DC.Relation" scheme="URI" content="intmsgd.htm" />
<meta name="DC.Relation" scheme="URI" content="intmsgq.htm" />
<meta name="DC.Relation" scheme="URI" content="wmsgs.htm" />
<meta name="DC.Relation" scheme="URI" content="../nls/rbagsglobalmain.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="intmsg" />
<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>Messages</title>
</head>
<body id="intmsg"><a name="intmsg"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Messages</h1>
<div><p>A message is a communication sent from one user, program, or procedure
to another.</p>
<p>System messages can report both status information and error conditions.
Most data processing systems provide communications between the system and
the operator to handle errors and other conditions that occur during processing. i5/OS™ also
provides message handling functions that support two-way communications between
programs and system users, between programs, between procedures within a program,
and between system users. Two types of messages are supported: </p>
<ul><li>Immediate messages, which are created by the program or system user when
they are sent and are not permanently stored in the system.</li>
<li>Predefined messages, which are created before they are used. These messages
are placed in a message file when they are created, and retrieved from that
file when they are used.</li>
</ul>
<p>Because messages can be used to provide communications between programs,
between procedures in a program, and between programs and users, using the i5/OS message
handling functions should be considered when developing applications. The
following concepts of message handling are important to application development:
</p>
<ul><li>Messages can be defined in messages files, which are outside the programs
that use them, and variable information can be provided in the message text
when a message is sent. Because messages are defined outside the programs,
the programs do not have to be changed when the messages are changed. This
approach also allows the same program to be used with message files containing
translations of the messages into different languages.</li>
<li>Messages are sent to and received from message queues, which are separate
objects on the system. A message sent to a queue can remain on the queue
until it is explicitly received by a program or workstation user.</li>
<li>A program can send messages to a user who requested the program regardless
of what workstation that user has signed on to. Messages do not have to be
sent to a specific device; one program can be used from different workstations
without change.</li>
</ul>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="intmsgd.htm">Message descriptions</a></strong><br />
A message description defines a message to i5/OS.</li>
<li class="ulchildlink"><strong><a href="intmsgq.htm">Message queues</a></strong><br />
When a message is sent to a procedure, a program, or a system user, it is placed on a message queue associated with that procedure, program, or user. The procedure, program, or user sees the message by receiving it from the queue.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="intro.htm" title="This describes how you can control the operation of the system using control language (CL), menu options, and system messages.">System operation control</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><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="relinfo"><strong>Related information</strong><br />
<div><a href="../nls/rbagsglobalmain.htm">Globalization</a></div>
</div>
</div>
</body>
</html>