ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahb_5.4.0.1/rzahbqueuesman.htm

127 lines
7.7 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="concept" />
<meta name="DC.Title" content="Manage message queues" />
<meta name="abstract" content="You can manage your message queues in several ways." />
<meta name="description" content="You can manage your message queues in several ways." />
<meta name="DC.Relation" scheme="URI" content="rzahbmsh.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahbcreatequeue.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahbseverequeue.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahbattributequeues.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahbchangequeue.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahbprintqueue.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="rzahbqueuesman" />
<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>Manage message queues</title>
</head>
<body id="rzahbqueuesman"><a name="rzahbqueuesman"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Manage message queues</h1>
<div><p>You can manage your message queues in several ways.</p>
<p>The operations you can use to manage your message queues include:</p>
<ul><li>Create message queues</li>
<li>Change the attributes of message queues</li>
<li>Change the message queue for a printer</li>
<li>Print all messages in the message queue</li>
</ul>
<div class="p">The following details are how these examples can be implemented using the
MSGQ function. <ul><li>You are a small-sized customer who has one LAN line and very few users:
There are no changes that need to be made; all messages will remain in QSYSOPR,
or the configured message queue.</li>
<li>You are a medium-sized customer who has a couple of LAN lines: In this
instance, you will need to change the QCFGMSGQ system value to the system-supplied
message queue, QSYS/QCFGMSGQ. As a result, all communications messages for
the object types that support the MSGQ configuration parameter will go to
this one queue.</li>
<li>You are a large-sized customer who has many LAN lines and many WAN lines,
with many users on each line. You want to set up the message queues so that
messages are separated as the following ways: <ul><li>The messages for the Ethernet LAN will go to ETHMSGQ: On this line, the
system configures all the controllers automatically.</li>
<li>The messages for the token-ring LAN will go to TRNMSGQ: On this line,
the system configures most controllers; however, some controllers must be
configured manually.</li>
<li>All messages for workstation users will go to the WSMSGQ: This includes
local workstations, remote workstations, pass-through, and telnet.</li>
<li>All other communications messages will go to QCFGMSGQ. </li>
</ul>
</li>
</ul>
<ul><li>You are an experienced operator who has written a program that helps the
operator know which message queues are the important ones. Here is how to
configure this example: <ul><li>Change the system value QCFGMSGQ to QSYS/QCFGMSGQ.</li>
<li>Create the Ethernet line description with MSGQ(ETHMSGQ): The system creates
all controllers (and thus devices) on this line. This means the system will
send their messages to the message queue defined in the line ETHMSGQ.</li>
<li>Create the token-ring line description with MSGQ(TRNMSGQ): The automatically
created controllers and devices on this line will have their messages sent
to TRNMSGQ. Controllers that are manually created on this line are created
with the MSGQ(TRNMSGQ) parameter.</li>
<li>Create the X.25 line description with MSGQ(V25MSGQ): All controllers that
are created for this X.25 line description must be created using the MSGQ(X25MSGQ)
parameter on the CRTCTLxxx command.</li>
<li>You can set up the workstation controller descriptions as the following
ways: <ul><li>The local workstation controller, which the system automatically created,
was changed to MSGQ(WSMSGQ). <div class="note"><span class="notetitle">Notes:</span> <ol><li>Create all printer devices attached to the workstation controller with
MSGQ(*CTLD). Messages for display devices always go to the message queue that
is defined in the associated controller. Thus, changing the message queue
of the controller results in the messages for the devices that go to the messages
queue defined in the controller description.</li>
<li>It is possible for the user to use a CHGCMDDFT command and have the message
queue default to a different queue. This means that the automatic creation
of the local workstation controller will use the different message queue.</li>
</ol>
</div>
</li>
<li>Create the virtual controllers for pass-through and Telnet with MSGQ(WSMSGQ). <p>Like
the local workstation controllers above, the devices attached to the virtual
workstation controllers will have their messages sent to the queue defined
in the virtual controller. The same logic works for remote workstation controllers
and their attached devices.</p>
</li>
</ul>
</li>
</ul>
</li>
<li>You are a large-sized customer that is now only using TCP/IP and want
to have the line and workstation messages logged to the QTCP message queue:
You can manage this configuration by changing the system value QCFGMSGQ to
QSYS/QTCP.</li>
</ul>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzahbcreatequeue.htm">Create message queues</a></strong><br />
You can create message queues to store messages within a particular library.</li>
<li class="ulchildlink"><strong><a href="rzahbseverequeue.htm">Create message queue QSYSMSG for severe messages</a></strong><br />
You can create an optional message queue, QSYSMSG, to hold specific severe system messages.</li>
<li class="ulchildlink"><strong><a href="rzahbattributequeues.htm">Change the attributes of message queues</a></strong><br />
Your server has several message queues that hold messages with helpful information for finding and reporting problems.</li>
<li class="ulchildlink"><strong><a href="rzahbchangequeue.htm">Change the message queue for a printer</a></strong><br />
You can change the location of the message queue that stores messages that are associated with each printer. Changing this location allows you to separate your printing messages from system, user, or error messages.</li>
<li class="ulchildlink"><strong><a href="rzahbprintqueue.htm">Print all messages in the message queue</a></strong><br />
Sometimes a problem has many messages associated with it.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahbmsh.htm" title="Use this topic to find out details on the different types of message queues and the several ways to manage message queues.">Details: Message queues</a></div>
</div>
</div>
</body>
</html>