IBM WebsphereMQ User Guide
IBM WebsphereMQ User Guide
IBM WebsphereMQ User Guide
®
IBM
Version 3.7.0
SC31-6888-00
12
2
Tivoli IBM Tivoli OMEGAMON XE for WebSphere MQ
®
IBM
Version 3.7.0
SC31-6888-00
12
Note
Before using this information and the product it supports, read the information in “Notices” on page 185.
This edition applies to version 3.7.0 of IBM® Tivoli® OMEGAMON® XE for WebSphere® MQ (product number 5724-L34
on Windows, UNIX, OS/400®, and HP NonStop Kernel; product number 5698-A57 on z/OS®) and to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 1996, 2005. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
2
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Chapter 4. Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
About Workspaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Application Debugging (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Application Statistics (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Buffer Pool Statistics (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Channel Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Channel Initiator Status (z/OS only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Channel Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Cluster Queue Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Dead-Letter Queue Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Error Log (non-z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Log Manager Performance (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Message Manager Performance (z/OS only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
MQSeries Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Page Set Statistics (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Queue Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Contents 5
Queue Manager Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Queue Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Queue-Sharing Group (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Queue Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Message Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
P
IBM® Tivoli® OMEGAMON® XE for WebSphere® Monitoring is a component product
of IBM Tivoli OMEGAMON XE for WebSphere MQ which is a component product of the
IBM Tivoli OMEGAMON XE for WebSphere Business Integration package. The IBM
Tivoli OMEGAMON XE for WebSphere MQ Monitoring software lets you easily collect
and analyze WebSphere MQ-specific data for all your remote and local queue managers
from a single vantage point.
This book describes the features and capabilities of IBM Tivoli OMEGAMON XE for
WebSphere MQ Monitoring, and explains how to use it to monitor your WebSphere MQ
network.
Preface 7
About This Book
Related publications
This section lists other useful publications in the IBM Tivoli OMEGAMON XE for
WebSphere Business Integration library and in the OMEGAMON Platform library.
The installation and configuration instructions in the following books are a prerequisite to
the instructions in Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring:
I
Windows and UNIX:
– Installing and Setting up OMEGAMON Platform and CandleNet® Portal on
Windows and UNIX, SC32-1768
– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business
Integration on Windows and UNIX, SC31-6885
I
z/OS®:
– Configuring Candle Management Server on z/OS, GC32-9414
– Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on
z/OS, SC31-6884
I OS/400®:
– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere MQ on
OS/400, SC31-6886
I
HP NonStop Kernel
– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere MQ on HP
NonStop Kernel, SC31-6887
These books explain how to use the other component products of IBM Tivoli
OMEGAMON XE for WebSphere Business Integration:
I Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, SC31-6889
I Using IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers, SC31-6890
I Using IBM Tivoli OMEGAMON XE for WebSphere InterChange Server, SC31-6891
The following documents also provide useful information:
I Administering OMEGAMON Products: CandleNet® Portal, GC32-9180, describes the
support tasks and functions required for the OMEGAMON Platform, including
CandleNet Portal user administration.
I Using OMEGAMON Products: CandleNet Portal, GC32-9182, describes the features
of CandleNet Portal and how to use them with your IBM Tivoli OMEGAMON XE
products.
I Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products,
GC32-9429, describes the process of collecting historical data and either warehousing
it or converting it to delimited flat files for reporting purposes.
I IBM Tivoli Candle Products Messages, 5 vols. SC32-9416–SC32-9420, lists messages
issued by the OMEGAMON Platform components.
The online glossary for the CandleNet Portal includes definitions for many of the technical
terms related to OMEGAMON XE software.
Ordering publications
You can order many Tivoli publications online at the following Web site:
Preface 9
About This Book
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi
You can also order by telephone by calling one of these numbers:
I In the United States: 800-879-2755
I In Canada: 800-426-4968
In other countries, see the following Web site for a list of telephone numbers:
http://www.ibm.com/software/tivoli/order-lit
Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
I
Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
I Obtaining fixes: You can locate the latest fixes that are already available for your
product.
I Contacting IBM Software Support: If you still cannot solve your problem, and you
need to work with someone from IBM, you can use a variety of ways to contact IBM
Software Support.
For more information about these three ways of resolving problems, see “Support
Information” on page 179.
Documentation Conventions
Overview
This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths.
Required blanks
The slashed-b (!) character in examples represents a required blank. The following
example illustrates the location of two required blanks.
!eBA*ServiceMonitor!
!0990221161551000
Revision bars
Revision bars (|) may appear in the left margin to identify new or updated material.
Symbols
The following symbols may appear in command syntax:
Symbol Usage
| The “or” symbol is used to denote a choice. Either the argument on the left or
the argument on the right may be used. Example:
YES | NO
In this example, YES or NO may be specified.
[] Denotes optional arguments. Those arguments not enclosed in square brackets
are required. Example:
APPLDEST DEST [ALTDEST]
In this example, DEST is a required argument and ALTDEST is optional.
Preface 11
Documentation Conventions
Symbol Usage
{} Some documents use braces to denote required arguments, or to group
arguments for clarity. Example:
COMPARE {workload} -
REPORT={SUMMARY | HISTOGRAM}
The workload variable is required. The REPORT keyword must be specified
with a value of SUMMARY or HISTOGRAM.
_ Default values are underscored. Example:
COPY infile outfile - [COMPRESS={YES | NO}]
In this example, the COMPRESS keyword is optional. If specified, the only
valid values are YES or NO. If omitted, the default is YES.
W
This product has a new name
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring (formerly OMEGAMON XE
for WebSphere MQ Monitoring) has been renamed because it is now produced by the
Tivoli Software Group of IBM.
Its companion product, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration
(formerly OMEGAMON XE for WebSphere MQ Configuration) has also been renamed.
These two component products together are called IBM Tivoli OMEGAMON XE for
WebSphere MQ which is a component product of the IBM Tivoli OMEGAMON XE for
WebSphere Business Integration package.
1 for WebSphere MQ
Monitoring
Introduction
This chapter introduces you to IBM Tivoli OMEGAMON XE for WebSphere MQ
Monitoring, its facilities, and the environment in which it operates.
Chapter contents
About IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring . . . . . . . . . . . . . . 16
OMEGAMON Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Investigating an Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
15
About IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
I workspaces that contain various types of information whose format and content you
can customize. When a condition you are monitoring exceeds thresholds you define,
an alert appears in the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
workspace to let you know. The following is an example of such an alert.
I attributes you can use to create situations that monitor areas of particular interest
and issue alerts when specified conditions are met.
I
predefined situations you can either use as shipped to begin monitoring
immediately or copy then modify to monitor your specific environment.
17
OMEGAMON Platform
OMEGAMON Platform
IBM Tivoli OMEGAMON XE for WebSphere MQ is one of a suite of IBM products that
assist you in monitoring your mainframe and distributed systems and applications. IBM
Tivoli OMEGAMON XE products share a common agent-server-client architecture.(see
Figure 1).
OMEGAMON XE agents
OMEGAMON XE monitoring agents collect system or application data from monitored,
or managed, systems. The IBM Tivoli OMEGAMON XE for WebSphere MQ monitoring
agents, for example, let you easily collect and analyze WebSphere MQ-specific data for all
your remote and local queue managers from a single vantage point. The data are passed
to the Candle Management Server, and displayed in the CandleNet Portal client.
CandleNet Portal
Clients
Monitoring Agents
OMEGAMON XE monitoring agents can also compare the current values of monitored
properties against a set of defined conditions, and trigger alerts or actions when
conditions warrant. They can accept and execute requested actions relayed to them from
CandleNet Portal clients by the Candle Management Server.
OMEGAMON configuration agents can create and configure objects. The configuration
agents associated with IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration
can configure objects such as WebSphere MQ queue managers and all their components
(queues, channels, processes, and so on).
sends the data it receives from the agents to CandleNet Portal clients, where it is displayed
in tabular or graphic views in a set of predefined or customized workspaces. The CMS
also accepts requests for information or action from CandleNet Portal clients and
distributes them to the agents for execution.
19
OMEGAMON Platform
Policy Management
The CandleNet Portal Policy Management solution incorporates all the features of IBM
Tivoli OMEGAMON DE and adds automation capabilities by means of the Workflow
editor. The Workflow editor enables you to design sets of automated system processes,
called policies, to resolve system problems. A policy performs actions, schedules work
tobe performed by users, or automates manual tasks.
Key Features
What is a workspace?
CandleNet Portal displays information in workspaces. A workspace is the working area of
the CandleNet Portal application window and is made up of one or more views. A view is
a pane in the workspace, typically a chart or table showing data collected from a
OMEGAMON monitoring agent, such as the process detail running on the UNIX
operating system.
A workspace may be linked to other workspaces. A link may be context-sensitive,
whereby you right-click a row in a table or a data series in a chart to link to more detailed
information about one of the attributes in the row or data series.
As you select items in the Navigator, the workspace presents views pertinent to your
selection. Every workspace has at least one view, and every workspace has a set of
properties associated with it. You can customize the workspace by working in the
Properties editor to change the style and content of each view. Another way to customize
the workspace is to change the type of view or to add views to the workspace.
Predefined workspaces
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring is shipped with predefined
workspaces that you can use as shipped or modify by using the Properties editor.
Predefined workspaces make it easy for you to quickly start using IBM Tivoli
OMEGAMON XE for WebSphere MQ Monitoring effectively to monitor your
environment.
A high-level overview of the types of workspaces included with this product is provided in
“Workspaces” on page 77.
For a complete list of the predefined workspaces included with this product, see the IBM
Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of the CandleNet Portal
online help.
For information about creating and customizing views and workspaces, see the
CandleNet Portal online help.
What is a situation?
A situation is a logical expression involving one or more system conditions. Situations are
used to monitor the condition of systems in your network. You can manage situations
from CandleNet Portal by using the Situation editor.
For detailed information about situations and about using the Situation editor, see the
CandleNet Portal online help.
21
Key Features
Predefined situations are precoded to check for system conditions common to many
enterprises. Using predefined situations can improve the speed with which you can begin
using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring. You can examine
and, if necessary, change the conditions or values being monitored by a predefined
situation to those best suited to your enterprise.
Note: IBM suggests that if you choose to modify a predefined situation, you first use
CandleNet Portal’s “Create another situation” function to make a copy of the
original situation. This ensures that you can fall back if necessary.
For a list of the predefined situations provided with this product, together with the
situations’ descriptions and formulas, see the IBM Tivoli OMEGAMON XE for WebSphere
MQ Monitoring section of the CandleNet Portal online help.
For a complete description of the predefined Take Action commands provided with this
product, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of
the CandleNet Portal online help. For detailed information about creating and using Take
Action commands, see the CandleNet Portal online help.
23
Investigating an Event
Investigating an Event
ENTERPRISE
UNIX Systems
myhost
MQSERIES - Default
Channel Definitions
Channel Performance
Cluster Queue Manager
Dead-Letter Queue Messages
Error Log
MQSeries Events
Queue Definitions
Queue Manager Status
MQSeries_Queue_Manager_Problem
Queue Statistics
When you see an alert icon overlaying a Navigator icon, open the Event workspace and
drill down to investigate the cause of the alert. The following is an example Event
workspace for IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring.
Looking at this workspace, you can determine the situation that raised the event and the
attributes whose values are contributing to the alert. You can also review available advice
and take appropriate actions.
Acknowledgment
When you see an event indicator in the Navigator, you can create an acknowledgment.
An acknowledgment notifies other users that you have taken ownership of the problem
related to the event and are working on it. When you acknowledge an event, a blue
checkmark appears next to the situation in the event flyover list and, if you opened the
event workspace, over the situation item in the Navigator. If the situation is still true when
the acknowledgment expires, the indicator changes accordingly. You can also cancel the
acknowledgment before it has expired. This changes the indicator so that users can see
that the acknowledgment has been removed even though the situation remains true.
25
Investigating an Event
2
Introduction
This chapter describes all monitoring options associated with IBM Tivoli OMEGAMON
XE for WebSphere MQ Monitoring and how to change them on the supported platforms.
The commands are summarized below.
Chapter contents
Monitoring Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
What are monitoring options?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Create a queue manager group: SET GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Specify queue managers: SET MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Specify queues: SET QUEUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Specify channels: SET CHANNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specify the event log: SET EVENTLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Specify event queues: SET EVENTQIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Share event queue data with other applications: SET EVENTQOUT . . . . . . . . . . 42
Include external customization commands: PERFORM INCLUDE . . . . . . . . . . . . 44
Start monitoring: PERFORM STARTMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Specify agent hostname: SET AGENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Monitor applications: SET APPL (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Monitor applications: SET MQIMONITOR (z/OS only) . . . . . . . . . . . . . . . . . . . . . 52
Queue sharing group monitoring: SET QSG (z/OS only) . . . . . . . . . . . . . . . . . . . 54
Changing Monitoring Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Monitoring Options
Description
The SET GROUP command defines a group of queue managers that have common
monitoring characteristics. Within the group, you can override like-named parameters for
specific queue managers using the SET MANAGER command.
At least one SET GROUP command is required.
Syntax
SET GROUP NAME(group-name)
[DEFAULT(YES|NO)]
[AGGRHIST(aggregation-samples)]
[COMMAND(YES|NO)]
[ERRLOGCYCLE(sampling-interval)]
[ERRLOGMAX(max-messages-in-memory)]
[EVENTS(REMOVE|BROWSE|NO)]
[HLQ(high-level-qualifier)]
[ICYCLE(interval-cycle )]
[LIKE(like-group-name)]
[MSGACCESS(NONE|DESC|RETRY|DATA|DELETE)]
[RETAINHIST(historical-retention-value)]
[RQMODEL(reply-to-queue’s-model-queue)]
Parameters
NAME(group-name)
1–48 character group name. Subsequent commands refer to the group and its
parameter settings by this name. This parameter is required.
DEFAULT(YES|NO)
Specifies whether or not this is the default group. If YES, the settings on this
command apply to any SET MANAGER statement that omits the GROUP parameter.
The IBM-provided default group is named DEFAULT.
AGGRHIST(aggregation-samples)
Number of samples to maintain in recent history for all queue managers in this group.
The default value is 15.
COMMAND(YES|NO)
Controls the MQ Command feature. For more details, see the same parameter in
“Specify queue managers: SET MANAGER” on page 31.
ERRLOGCYCLE(sampling-interval)
Specifies, in seconds, the interval of the error log collection cycle. For more details,
see the same parameter in “Specify queue managers: SET MANAGER” on page 31.
ERRLOGMAX(max-messages-in-memory)
Specifies the maximum number of error messages that are held in memory and
displayed in the Error Log workspace. For more details, see the same parameter in
“Specify queue managers: SET MANAGER” on page 31.
EVENTS(REMOVE|BROWSE|NO)
Specifies how to access system event queues. For more details, see the same
parameter in “Specify queue managers: SET MANAGER” on page 31.
HLQ(high-level-qualifier)
Specifies the high-level qualifier for product-created queue names. The default is
KMQ. For more details, see the same parameter in “Specify queue managers: SET
MANAGER” on page 31.
ICYCLE(interval-cycle)
Specifies the number of sample interval cycles to wait before gathering queue
manager performance data. For more details, see the same parameter in “Specify
queue managers: SET MANAGER” on page 31.
LIKE(like-group-name)
Name of a previously defined manager group. Like-named parameter values are
copied from the values in the named group definition.
MSGACCESS(NONE|DESC|RETRY|DATA|DELETE)
Level of user access to messages in queues. For more details, see the same parameter
in “Specify queue managers: SET MANAGER” on page 31.
RETAINHIST(historical-retention-value)
Number of minutes that historical data is displayed for queue manger objects (such as
channels and queues). The default value is 1440 (24 hours).
RQMODEL(reply-to-queue’s-model-queue)
Specifies the 1–48 character name of a model queue to use as a model for this
product's reply-to queue. If not specified, the standard system default model is used.
For more details, see the same parameter in “Specify queue managers: SET
MANAGER” on page 31.
Example
To define a manager group named MYGROUP with new values for aggregation and
historical retention, specify:
SET GROUP NAME(MYGROUP) LIKE(DEFAULT) -
AGGRHIST(20) RETAINHIST(2400)
Description
The SET MANAGER command specifies queue managers to be monitored.
Syntax
SET MANAGER NAME(manager-name-mask)
[GROUP(group-name)]
[ACTIVE(YES|NO)]
[AGGRHIST(aggregation-samples)]
[COMMAND(YES|NO)]
[ERRLOGCYCLE(sampling-interval)]
[ERRLOGMAX(max-messages-in-memory)]
[EVENTS(REMOVE|BROWSE|NO)]
[HLQ(high-level-qualifier)]
[ICYCLE(interval-cycle )]
[LIKE(like-manager-name)]
[MSGACCESS(NONE|DESC|RETRY|DATA|DELETE)]
[NICKNAME(nickname)]
[RETAINHIST(historical-retention-value)]
[RQMODEL(reply-to-queue’s-model-queue)]
[STATUS(ADD|DELETE|RESET)]
[SYSNAME(z/OS-system-id)]
Parameters
NAME(manager-name-mask)
On z/OS, this is the 1–4 character specific or generic queue manager name to
monitor. To specify a generic name, enter a character string followed by an asterisk
(*). For example, to monitor all z/OS queue managers, specify NAME(*). This
parameter is required on z/OS.
On distributed platforms, this parameter can be (), in which case the default queue
manager is monitored, or is the name of the one queue manager this invocation of
the monitoring agent is to monitor.
GROUP(group-name)
Previously defined group whose parameters apply to this queue manager. The name
must exactly match the name specified on a prior SET GROUP statement. The
IBM-provided default group is named DEFAULT.
ACTIVE(YES|NO)
Indicates whether or not to actively monitor this queue manager. YES is the default.
AGGRHIST(aggregation-samples)
Number of samples to maintain in recent history for this queue manager.
COMMAND(YES|NO)
Controls the MQ Command feature, as follows:
YES - Enables the MQ Command feature, which allows the user to pass WebSphere
MQ commands to the queue manager from CandleNet Portal. YES is the default.
where hlq is the value specified by the HLQ parameter of the SET MANAGER or the
SET GROUP command.
Otherwise, if you do not predefine queues with the names described above, this
product creates dynamic queues using the model queue specified by the RQMODEL
parameter of the SET MANAGER or the SET GROUP command. In this case, the
names of the dynamic queues are as follows.
On z/OS:
hlq.COMMAND.REPLY.dynamicsuffix
hlq.REPLY.dynamicsuffix
On non-z/OS:
hlq.IRA.AGENT.QUEUE.dynamicsuffix
where hlq is the value specified using the HLQ parameter of the SET MANAGER or
the SET GROUP command, and dynamicsuffix is the standard dynamic suffix
provided by WebSphere MQ.
ICYCLE(interval-cycle)
This parameter applies only to z/OS.
This optional parameter specifies the number of sample interval cycles to wait before
gathering queue manager performance data for the specified queue manager(s). It is
intended for special cases when you want to effectively lengthen the sampling interval
for specific queue managers and groups of queue managers. The ICYCLE value can
be used to reduce the impact of monitoring a less critical queue manager. For
example, if 60 is set as the sample interval and 5 is set as the interval cycle value for a
queue manager, interrogative processing for that queue manager will only be done
every fifth cycle, every five minutes instead of every minute.
If ICYCLE is not specified or is not specified on a prior SET GROUP statement, the
default is 1; meaning queue manager data is gathered once every sample interval
(SAMPINT).
LIKE(like-manager-name)
Name or nickname of a previously defined manager. Like-named but unspecified
parameter values are copied from the corresponding values for this queue manager.
MSGACCESS(NONE|DESC|RETRY|DATA|DELETE)
Controls the level of user access to messages in queues for the specified queue
managers.
NONE - Allows no access to message functions for this queue manager, including the
ability to list messages on a queue or collect message statistics.
DESC - Allows message descriptor browse for either message summary workspaces,
message detail workspaces, or message statistics workspaces and situations. This is
the default level.
RETRY - Allows DLQ retry and message descriptor browse.
DATA - Allows message data (contents) browse, message descriptor browse, and DLQ
retry.
RESET - Resets the monitoring parameters associated with this queue manager to
their original values (as defined on the original SET MANAGER command for this
manager name).
SYSNAME(z/OS-system-id)
This parameter applies only to z/OS.
SMF system ID where this queue manager runs. If omitted, this SET MANAGER
command applies to any z/OS system.
Examples
I To monitor all z/OS queue managers whose names begin with MQM, specify:
SET MANAGER NAME(MQM*)
I To monitor the queue manager named PAYROLL, specify:
SET MANAGER NAME(PAYROLL)
I To set the number of recent samples to 30 and the retention interval for historical
displays to 10 hours for queue manager MGRA, specify:
SET MANAGER NAME(MGRA) AGGRHIST(30) RETAINHIST(600)
I To sample the error log every 20 seconds and display up to 200 error log events for
the queue manager named QMGRA, specify:
SET MANAGER NAME(QMGRA) ERRLOGCYCLE(20) ERRLOGMAX(200)
I This example specifies three queue managers with nicknames. Since the GROUP,
AGGRHIST, and RETAINHIST keywords are omitted, the values specified on the SET
GROUP command for the default group are in effect for those parameters. Each
manager defines a different access to the system event queues.
SET MANAGER NAME(MGRD) NICKNAME(DALLAS) EVENTS(REMOVE)
SET MANAGER NAME(MGRA) NICKNAME(ATLANTA) EVENTS(NO)
SET MANAGER NAME(MGRS) NICKNAME(SANFRAN) EVENTS(BROWSE)
I To specify an effective sample interval of one minute for z/OS queue manager QM01
and five minutes for z/OS queue manager QM02, specify:
SET MANAGER NAME(QM01)
SET MANAGER NAME(QM02) ICYCLE(5)
PERFORM STARTMON SAMPINT(60)
Description
The SET QUEUE command specifies the queues to be monitored. IBM Tivoli
OMEGAMON XE for WebSphere MQ Monitoring always monitors the dead-letter queue.
To monitor other system or application queues, specify them with the SET QUEUE
command.
Syntax
SET QUEUE NAME(queue-name-mask)
MGRNAME(manager-name) | GROUP(group-name)
[QDEFTYPE(PREDEFINED|PERMDYN|TEMPDYN|ALL)]
[STATISTICS(YES|NO)]
[STATUS(ADD|DELETE)]
Parameters
NAME(queue-name-mask)
Defines the 1–48 character specific or generic queue name to monitor. To specify a
generic name, enter a string of characters followed by an asterisk (*). This parameter
is required.
MGRNAME(manager-name)
Associates this SET QUEUE command with a queue manager defined on a previous
SET MANAGER command. You can use the name or nickname of the manager. The
name must exactly match the name specified on the corresponding SET MANAGER
command. This parameter is required if GROUP is not specified.
GROUP(group-name)
Associates this SET QUEUE statement with a group of queue managers defined on a
previous SET GROUP statement. The name must exactly match the name specified
on the corresponding SET GROUP statement. This parameter is required if
MGRNAME is not specified.
QDEFTYPE(PREDEFINED|PERMDYN|TEMPDYN|ALL)
Indicates which kinds of queues to monitor. Specify any or all of these definition
types:
PREDEFINED - Monitors only predefined queues matching the specific or generic
queue name.
PERMDYN - Monitors only permanent dynamic queues matching the specific or
generic queue name.
TEMPDYN - Monitors only temporary dynamic queues matching the specific or
generic queue name.
ALL - Monitors all queues matching the specific or generic queue name. This is the
default.
STATISTICS(YES|NO)
Specifies whether or not to collect queue statistics using WebSphere MQ Reset Queue
Statistics command processing.
YES - Collect statistics using Reset Queue Statistics command processing for queues
matching the specific or generic queue name.
NO - Do not collect statistics using Reset Queue Statistics command processing for
queues matching the specific or generic queue name. This is the default. See “Queue
Statistics Feature” on page 71 for a description of the Queue Statistics feature which
includes requirements and restrictions.
STATUS(ADD|DELETE)
Specifies what to do if this SET QUEUE command was previously specified with the
same name.
If omitted, the queue definition is added if it is a new name, or modified if the same
name was specified previously.
ADD - Creates a new queue definition. If this SET QUEUE command was previously
specified with the same name then it will not be modified and an error message will
be issued.
DELETE - Deletes a queue definition and all associated historical data.
Examples
I To monitor all queues managed by queue manager MGRA, specify:
SET QUEUE NAME(*) MGRNAME(MGRA)
I To monitor a queue named ACCOUNTS, specify:
SET QUEUE NAME(ACCOUNTS) MGRNAME(MGRA)
I To monitor and collect statistics using Reset Queue Statistics command processing for
all queues managed by QMGRA, specify:
SET QUEUE NAME(*) MGRNAME(QMGRA) STATISTICS(YES)
I To monitor permanent dynamic queues starting with the characters PAYR, specify:
SET QUEUE NAME(PAYR*) MGRNAME(MGRA) QDEFTYPE(PERMDYN)
I To monitor predefined and temporary dynamic queues for queue manager MGRC
whose names start with MARCH, specify:
SET QUEUE NAME(MARCH*) MGRNAME(MGRC) -
QDEFTYPE(PREDEFINED,TEMPDYN)
Description
The SET CHANNEL command specifies channels to be monitored.
Syntax
SET CHANNEL NAME(channel-name-mask)
MGRNAME(manager-name) | GROUP(group-name)
[STATUS(ADD|DELETE)]
Parameters
NAME(channel-name-mask)
Defines the 1–20 character specific or generic channel name to monitor. To specify a
generic name, enter a string of characters followed by an asterisk (*). This field is
required.
MGRNAME(manager-name)
Associates this SET CHANNEL statement with a queue manager defined on a
previous SET MANAGER statement. You can use the name or nickname of the
manager. The name must exactly match the name specified on the corresponding
SET MANAGER statement. This parameter is required if GROUP is not specified.
GROUP(group-name)
Associates this SET CHANNEL statement with a group of queue managers defined
on a previous SET GROUP statement. The name must exactly match the name
specified on the corresponding SET GROUP statement. This parameter is required if
MGRNAME is not specified.
STATUS(ADD|DELETE)
Specifies what to do if this SET CHANNEL command was previously specified with
the same name.
If omitted, the result is the same as if ADD is specified.
ADD - Creates a new channel definition. If this SET CHANNEL command was
previously specified with the same name then it will not be modified and an error
message will be issued.
DELETE - Deletes a channel definition and all associated historical data.
Example
To monitor a channel named MONTANA owned by queue manager SMONICA, specify:
SET CHANNEL NAME(MONTANA) MGRNAME(SMONICA)
Description
The SET EVENTLOG command specifies the size, location, and other attributes of the
event log.
All parameters are optional; but, if the SET EVENTLOG statement is coded, at least one
parameter must be coded as well.
This command applies to all platforms except z/OS.
Syntax
SET EVENTLOG
[SIZE(n)]
[DIR(dir_name)]
[ARCHIVEFILE(arch_filename)]
[ARCHIVEOPTS( krarloff_options)]
Parameters
SIZE(n)
where n is the maximum event log file size in megabytes. If SIZE is not specified, the
default is 10. Specify SIZE(0) to disable the event log.
DIR(dir_name)
The directory to write the event log file to. If DIR is not specified, the default is the
value assigned to the ctira_hist_dir variable (@logpath@ — normally
C:\Candle\Cma\Logs).
ARCHIVEFILE(arch_filename)
The archive directory and file name. If ARCHIVEFILE is not specified, the default is
@logpath@\Qmeventh.arc. If this file already exists, krarloff appends the new data to
it.
ARCHIVEOPTS(krarloff_options)
If ARCHIVEOPTS is not specified, all krarloff defaults will be taken. See the Historical
Data Collection Guide for IBM Tivoli OMEGAMON XE Products for details of the
krarloff (kra rolloff) command.
Description
The SET EVENTQIN command identifies the queue manager event queue, channel
event queue, performance event queue, and configuration event queue for a queue
manager or group of queue managers.
If no SET EVENTQIN command applies to a queue manager, the following default
WebSphere MQ names are used:
I SYSTEM.ADMIN.QMGR.EVENTS
I SYSTEM.ADMIN.CHANNEL.EVENTS
I SYSTEM.ADMIN.PERFM.EVENTS
I SYSTEM.ADMIN.CONFIG.EVENT (Configuration events are present on WebSphere
MQ for z/OS version 5.3 and above only.)
Syntax
SET EVENTQIN
MGRNAME(manager-name) | GROUP(group-name)
[QMGRQ(queue-name)]
[CHANNELQ(queue-name)]
[PERFMQ(queue-name)]
[CONFIGQ(queue-name)]
Parameters
MGRNAME(manager-name)
The queue manager that owns the specified event queue(s). You can use the name or
nickname of the queue manager. The name must exactly match the name specified
on the corresponding SET MANAGER statement. This parameter is required if
GROUP is not specified.
GROUP(group-name)
A group of queue managers (as specified on a previous SET GROUP statement),
each of which owns the specified event queue(s). The name must exactly match the
name specified on the corresponding SET GROUP statement. This parameter is
required if MGRNAME is not specified.
QMGRQ(queue-name)
Specifies the name of the queue manager event queue to monitor.
CHANNELQ(queue-name)
Specifies the name of the channel event queue to monitor.
PERFMQ(queue-name)
Specifies the name of the performance event queue to monitor.
CONFIGQ(queue-name)
Specifies the name of the configuration event queue to monitor.
Examples
I To read events from a performance event queue named
PERFORMANCE.EVENTS.IN instead of from the default WebSphere MQ
performance event queue, SYSTEM.ADMIN.PERFM EVENTS, specify:
SET EVENTQIN MGRNAME(MQM3) PERFMQ(PERFORMANCE.EVENTS.IN)
The example above could apply to two possible scenarios:
– An application is reading from the default WebSphere MQ performance event
queue, and it is copying events to PERFORMANCE.EVENTS.IN.
– Your site has changed the default WebSphere MQ performance queue name from
SYSTEM.ADMIN.PERFM.EVENTS to PERFORMANCE.EVENTS.IN
I To read events from a channel event queue called CHANNEL.EVENTS.IN and copy
these events to a queue called CHANNEL.EVENTS.OUT, specify:
SET EVENTQIN MGRNAME(MQM2) CHANNELQ(CHANNEL.EVENTS.IN)
Description
Once IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring has read an event
message from an event queue, it deletes the message to ensure that it is processed only
once. If another application running at your site requires access to event messages, you
can define an output queue where these messages are copied and point the other
application to that queue.
The SET EVENTQOUT command identifies the output queue(s) where queue manager
event information, channel event information, performance event information, and
configuration event information will be copied.
If no SET EVENTQOUT command applies to a queue manager, the event information is
discarded after being processed.
Syntax
SET EVENTQOUT
MGRNAME(manager-name) | GROUP(group-name)
[QMGRQ(queue-name)]
[CHANNELQ(queue-name)]
[PERFMQ(queue-name)]
[CONFIGQ(queue-name)]
Parameters
MGRNAME(manager-name)
The queue manager that owns the specified output queue(s). You can use the name
or nickname of the queue manager. The name must exactly match the name specified
on the corresponding SET MANAGER statement. This parameter is required if
GROUP is not specified.
GROUP(group-name)
The group of queue managers (as specified on a previous SET GROUP statement),
each of which owns the specified event queue(s). The name must exactly match the
name specified on the corresponding SET GROUP statement. This parameter is
required if MGRNAME is not specified.
QMGRQ(queue-name)
Specifies the name of the local queue where queue manager events are copied after
being processed. This queue must exist when the SET EVENTQOUT command is
processed.
CHANNELQ(queue-name)
Specifies the name of the local queue where channel events are copied after being
processed. This queue must exist when the SET EVENTQOUT command is
processed.
PERFMQ(queue-name)
Specifies the name of the local queue where performance events are copied after
being processed. This queue must exist when the SET EVENTQOUT command is
processed.
CONFIGQ(queue-name)
Specifies the name of the local queue where configuration events are copied after
being processed. This queue must exist when the SET EVENTQOUT command is
processed. Configuration events are present on WebSphere MQ for z/OS version 5.3
and above only.
Examples
I To read events from the default WebSphere MQ queue manager event queue,
SYSTEM.ADMIN.QMGR.EVENTS, and copy them to a queue named
QMGR.EVENTS.OUT, specify:
SET EVENTQOUT MGRNAME(MQM1) QMGRQ(QMGR.EVENTS.OUT)
I To read events from a channel event queue called CHANNEL.EVENTS.IN and copy
these events to a queue called CHANNEL.EVENTS.OUT, specify:
SET EVENTQIN MGRNAME(MQM2) CHANNELQ(CHANNEL.EVENTS.IN)
Description
The PERFORM INCLUDE command points to an external file containing customization
commands. To execute the commands in this file, specify PERFORM INCLUDE in your
startup file.
Syntax
PERFORM INCLUDE LIST( file-ID)
Parameter
LIST(file-ID)
Name of the file containing the list of IBM Tivoli OMEGAMON XE for WebSphere
MQ Monitoring customization commands. On z/OS, file-ID must be a member of the
RKANCMD dataset. This parameter is required.
Examples
I
To execute a set of external commands in file remote.txt, specify:
PERFORM INCLUDE LIST(remote.txt)
I To execute a set of external commands in member MYSET of the RKANCMD dataset
on z/OS, specify:
PERFORM INCLUDE LIST(MYSET)
Description
The PERFORM STARTMON command initiates monitoring of WebSphere MQ objects,
specifies the sampling interval for collecting WebSphere MQ data, and specifies whether
or not historical data will be collected.
The PERFORM STARTMON command is required.
Syntax
PERFORM STARTMON
SAMPINT(sample-interval)
HISTORY (YES|NO)
[ACTIVEONLY(YES|NO)]
[ROWLIM(limit)]
[SVRCONN(YES|NO)]
[QSGCHKINTERVAL(sss)]
[GRPNAME(KMQQSG|gggggggg)]
Parameter
SAMPINT(sample-interval)
How often, in seconds, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring
samples your queue manager(s) for performance data. The default is 60 seconds.
The minimum is 10 seconds.
If your site is monitoring large numbers of queues or channels, you may experience a
degradation in performance. If that occurs, IBM recommends that you increase the
value of SAMPINT to improve performance.
If your site is monitoring queue-sharing groups on z/OS, the sample interval should be
the same interval for all agents that monitor queue managers in queue-sharing
groups.
See also, ICYCLE.
HISTORY(YES|NO)
Defines whether or not historical data will be collected. On distributed platforms, the
value pre-configured for you by the installation/configuration process is NO. On z/OS,
the value pre-configured for you by the Configuration tool is YES. The default, if not
otherwise specified by the installation/configuration process, is NO. (For information
about using the historical data collection function see the CandleNet Portal online
help and the Historical Data Collection Guide for IBM Tivoli OMEGAMON XE
Products.)
ACTIVEONLY(YES|NO)
This parameter applies only to z/OS.
This optional parameter indicates whether or not to monitor only active queue
managers.
YES - Only queue managers that are running at agent startup time, or become active
while the agent is running, are referenced in situations and displayed in the Navigator
physical view. This parameter is intended for environments where a large number of
queue managers are defined but only some of them are in use.
NO - All defined queue managers, active or not, are referenced in situations and
displayed in the Navigator physical view. The default if not specified is NO.
Do not use this parameter if you want to monitor only a subset of your queue
managers.
ROWLIM(limit)
This optional parameter specifies the maximum number of messages that will be
processed and returned by the agent when reading messages from a queue for report
requests. The default if not specified is 0 (zero) which means that the maximum
number of messages is not limited.
SVRCONN(YES|NO)
This optional parameter indicates whether or not to collect server connection channel
statistics which are displayed in the Channel Performance workspaces (and the short
and long-term Channel Performance History workspaces). The default if not specified
is YES.
QSGCHKINTERVAL(sss)
This optional parameter specifies how often, in seconds, IBM Tivoli OMEGAMON XE
for WebSphere MQ Monitoring “wakes up” to perform queue-sharing group
monitoring activities. The default is 300 which equals a 5-minute interval. The
minimum is 60 seconds; with the exception that it can be set to 0 (zero) to turn off
queue-sharing group monitoring activities. Note, if you turn this processing off, you
must recycle the agent to turn this processing back on.
GRPNAME(KMQQSG|gggggggg)
This optional parameter allows you to specify an alternative SysPlex XCF group
name, gggggggg, for the coexistence of multiple collection agents. The default is
KMQQSG. Under normal circumstances, this parameter should not be specified. This
parameter is intended for testing purposes, to allow multiple agents to coexist while
being tested.
Warning: Specifying an XCF group name that is in use by other system components
could have unexpected consequences and should not be done under any
circumstances.
Example
To start monitoring with a sampling interval of 120 seconds and turn on historical data
collection, as well as explicitly specify that historical data and server connection channel
statistics will be collected, specify:
PERFORM STARTMON SAMPINT(120) HISTORY(YES) SVRCONN(YES)
Description
The SET AGENT command allows you to specify the middle qualifier used in the
managed system name.
On distributed platforms, if this value is not specified, no value is used.
On z/OS, if this value is not specified, the host name is used. If you specify this value, it is
used only in the managed system names of subnodes. For example, to avoid confusion
and to allow multiple WebSphere MQ monitoring agents, instead of issuing the default
agent startup command "IRAMAN KMQAGENT START" (to start a node named
hostname:MQIRA) it allows you to issue the modified agent startup command "IRAMAN
KMQAGENT START agentid" (to start a node named agentid:MQIRA).
Here are some reasons to use the SET AGENT command:
I
On distributed platforms, if your site has multiple queue managers with the same
name, running on different nodes, you would to need to specify the node name for
each queue manager to uniquely identify them.
I To group and identify queue manager names by something other than the host name
and queue manager name.
I To allow multiple agents connected to the same CMS to monitor the same queue
manager.
Syntax
SET AGENT NAME(agentid)
Parameter
NAME(agentid)
Name to be used for the middle qualifier of the managed system name.
On distributed platforms, the complete managed system name will be
monitoredqueuemanagername:agentid:MQ.
On z/OS, the complete managed system name will be
monitoredqueuemanagername:agentid:MQESA.
The maximum length allowed for the complete managed system name is 32
characters, so the maximum length allowed for agentid will depend on the length of
the queue manager name. If there are not enough characters to fit the full agentid
specified, it will be truncated to no less than 8 characters.
Example
To monitor a queue manager named PERSONNEL on node AIX1 when there is also a
queue manager named PERSONNEL on a node named HPUX2, specify the following in
the monitoring file for AIX1:
SET MANAGER NAME(PERSONNEL)
SET AGENT NAME(AIX1)
To simultaneously monitor the PERSONNEL queue manager on node HPUX2, specify
the following in the monitoring file for HPUX2:
SET MANAGER NAME(PERSONNEL)
SET AGENT NAME(HPUX2)
Description
The SET APPL command identifies the WebSphere MQ-based z/OS applications, CICS®
transactions, and IMS™ programs that should be monitored for application debugging
information and application statistics.
Use the SET APPL command together with the SET MQIMONITOR command to activate
the application debugging and application statistics features. See “Monitor applications:
SET MQIMONITOR (z/OS only)” on page 52 for a description of SET MQIMONITOR.
Syntax
SET APPL NAME(application-name)
[TRANPGM(program-name)]
[MGRNAME(manager-name)]
[TRACE(NO|YES)]
[TRACELIMIT(1000|number-of-trace-records)]
[STATISTICS(NONE|NOQDATA|NODYNAMQ|ALL)]
[STATUS(ADD|DELETE)]
Parameters
NAME(application-name)
1–8 character name of the z/OS application to monitor. To specify a generic name,
enter a character string followed by an asterisk (*).
– The application name format differs depending on the applications being
monitored:
– For batch applications it is the 1–8 character job name.
– For TSO applications it is the 1–7 character user ID of the TSO session.
– For CICS applications it is the 1–8 character VTAM applid.
– For IMS applications it is the 1–4 character IMS subsystem ID prefixed with the
characters “IMS” and padded with a blank.
This parameter is required.
TRANPGM(program-name)
Further identifies the program(s) to monitor, as follows:
– The 1–4 character name of the CICS transaction to monitor within the VTAM
applid identified by the NAME parameter.
– The 1–8 character name of the IMS program within the IMS subsystem identified
by the NAME parameter.
– The 1–8 character name of the batch or TSO program within the address space
identified by the NAME parameter.
To specify a generic name, enter a character string followed by an asterisk (*). This
parameter is optional; if omitted, it defaults to "*".
MGRNAME(manager-name)
Name of the z/OS queue manager(s) whose applications are to be monitored. To
specify a generic name, enter a character string followed by an asterisk (*). The name
must exactly match the name specified on the corresponding SET MANAGER
statement. This parameter is optional; if omitted, it defaults to "*".
TRACE(NO|YES)
Specifies whether or not to record WebSphere MQ tracing information for this
application. This parameter is optional; the default is NO.
TRACELIMIT(1000|number-of-trace-records)
Specifies the number of trace records to save for later viewing. After this value is
reached, trace recording for this application is stopped. The maximum value allowed
is 12000; the default is 1000. You can issue the SET APPL statement again with this
parameter to resume trace recording after the maximum has been reached. This
parameter is optional.
STATISTICS(NONE|NOQDATA|NODYNAMQ|ALL)
The level of statistical information to collect for the applications identified by the
NAME parameter, as follows:
NONE - No statistical information is collected for this application.
NOQDATA - Application statistical information is not collected at the queue level;
however, statistical information is still collected at the application and transaction
levels.
NODYNAMQ - Application statistical information is not collected for dynamic queues
(temporary and permanent); however, statistical information is still collected for
predefined queues. Specifying NODYNAMQ does not affect the collection of
application statistics at the application and transaction level. Note specifying
NODYNAMQ activates Application Queue Statistics monitoring.
ALL - Statistical information is collected at the application, transaction, and queue
levels. Note specifying ALL activates Application Queue Statistics monitoring.
This parameter is optional; the default is NODYNAMQ.
STATUS(ADD|DELETE)
Specifies what to do if this SET APPL command was previously specified with the
same name.
If omitted, the application definition is added if it is a new name, or modified if the
same name was specified previously.
ADD - Creates a new application definition. If this SET APPL command was
previously specified with the same name then it will not be modified and an error
message will be issued.
DELETE - Deletes the application definition and all associated historical data.
Example
To collect only application- and transaction-level statistics, as well as WebSphere MQ
tracing information, for all the transactions running in CICS region PAYR, specify:
SET APPL NAME(PAYR) TRACE(YES) STATISTICS(NOQDATA)
Description
SET MQIMONITOR is supported on z/OS only.
The SET MQIMONITOR command activates monitoring for the applications you
specified using SET APPL. You must specify SET MQIMONITOR to turn on monitoring.
Use the SET MQIMONITOR command together with the SET APPL command to activate
the application debugging and application statistics features.
Syntax
SET MQIMONITOR STATUS(INSTALL|REMOVE|FREMOVE)
MGRNAME(manager-name) | GROUP(group-name)
[BUFFERSIZE(buffer-space)]
Parameters
STATUS(INSTALL|REMOVE|FREMOVE)
Required. Turns z/OS application monitoring on or off.
INSTALL - Application monitoring begins for the z/OS applications, CICS
transactions, and IMS programs identified on the SET APPL command. (If no SET
APPL command is specified, no data is collected.)
REMOVE - Application monitoring ends for the applications identified on the SET
APPL command. If monitoring has not already been activated by a previous SET
MQIMONITOR STATUS(INSTALL) command, the request is ignored.
FREMOVE - Use the FREMOVE option only if instructed to do so by IBM Software
Support. This parameter forces the removal and termination of application
monitoring.
MGRNAME(manager-name)
Application monitoring is installed or removed for the queue manager identified by a
previous SET MANAGER command. The name must exactly match the name
specified on the SET MANAGER command. This parameter is required if GROUP is
not specified.
GROUP(group-name)
Application monitoring is installed or removed for the group of queue managers
identified by a previous SET GROUP command. The name must exactly match the
name specified on the corresponding SET GROUP command. This parameter is
required if MGRNAME is not specified.
BUFFERSIZE(buffer-space)
Applies only when STATUS(INSTALL) is also specified. This parameter specifies the
size (in megabytes) of buffer data space for monitoring WebSphere MQ applications.
This parameter is optional, though IBM recommends using it for queue managers that
show more than 200 WebSphere MQ API calls per second. Use the following formula
to calculate the buffer space you need:
BUFFERSIZE=High MQSeries API rate/22
Example
To begin collecting application debugging information and application statistics for the
applications running for queue manager PRD1, with a buffersize of 32 megabytes,
specify:
SET MQIMONITOR STATUS(INSTALL) MGRNAME(PRD1) BUFFERSIZE(32)
Description
The SET QSG command specifies which queue-sharing groups the WebSphere MQ
monitoring agent on z/OS monitors and which queue managers the agent uses to collect
queue-sharing group data. At any given time, for a particular queue-sharing group, this
monitoring product uses only one queue manager to gather data. If that queue manager
becomes unavailable, data gathering will “fail over” to another queue manager.
The SET QSG command is optional. If not specified, the default behavior of the agent is
to monitor all queue-sharing groups that are associated with monitored queue managers.
You might use a SET QSG command to specify such things as:
I that no queue-sharing groups will be monitored.
I that a particular queue-sharing group will not be monitored.
I
that a particular queue manager should not be used to collect queue-sharing group
data.
Syntax
SET QSG [NAME(nnnn)]
[MGRNAME(mmmm)]
[MONITOR(NO|YES|TAKEOVER)]
Parameters
NAME(nnnn)
The NAME parameter specifies the name of a queue-sharing group. The NAME
parameter is optional. The default if not specified is NAME(*).
MGRNAME(mmmm)
The MGRNAME parameter specifies a queue manager name in a particular
queue-sharing group. The MGRNAME parameter is optional. The default if not
specified is MGRNAME(*).
MONITOR(NO|YES|TAKEOVER)
The MONITOR parameter specifies whether the agent monitors the specified
combination of queue-sharing group and queue manager. It also specifies whether
takover processing will be performed.
The MONITOR parameter is optional. The default if not specified is MONITOR(YES).
NO - The WebSphere MQ monitoring agent will not monitor the indicated
combination of queue-sharing group and queue manager.
YES - The WebSphere MQ monitoring agent will monitor the indicated combination
of queue-sharing group and queue manager. This is the default behavior.
TAKEOVER - The WebSphere MQ monitoring agent will takeover monitoring the
indicated queue-sharing group even if another WebSphere MQ monitoring agent is
already monitoring it. (Takeover processing does not occur if the other agent also
specified TAKEOVER.)
Examples
I To monitor no queue-sharing groups, specify:
SET QSG MONITOR(NO)
I To eliminate queue manager PMQ5 from queue-sharing group monitoring, specify:
SET QSG MONITOR(NO) MGRNAME(PMQ5)
I To direct queue-sharing group monitoring to queue manager PMQ6, specify:
SET QSG MONITOR(TAKEOVER) MGRNAME(PMQ6)
I To specify that a particular queue-sharing group will, or will not, be monitored may
require multiple SET QSG comands.
For example, suppose you have three queue-sharing groups in your environment
named QSGA, QSGB, and QSGC. To monitor only queue-sharing group QSGC, you
could specify the following commands:
SET QSG NAME(*) MONITOR(NO)
SET QSG NAME(QSGC) MONITOR(YES)
or the following commands could be used to produce the same effect.
SET QSG NAME(QSGA) MONITOR(NO)
SET QSG NAME(QSGB) MONITOR(NO)
SET QSG NAME(QSGC) MONITOR(YES)
However note that if you were to mistakenly specify only:
SET QSG NAME(QSGC) MONITOR(YES)
then all three queue-sharing groups, including QSGA and QSGB, would be
monitored. This is because the default behavior of the agent is to monitor all
queue-sharing groups.
Introduction
This section explains how to change monitoring options to suit your site’s requirements.
Instructions for each supported platform follow.
z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
NonStop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
OS/400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
z/OS
On z/OS, you can change monitoring options using any of the following methods:
I
Entering basic options through a panel using the Configuration tool (monitoring
group DEFAULT only).
I Dynamically specifying options from the MVS™ console.
I Editing the KMQUSER monitoring file.
These methods are discussed below.
1. If you are unfamiliar with the various monitoring options and the commands to enable
them, review the descriptions of the options in this chapter.
2. Display the monitoring options that are currently in effect:
F CANSMQ,KMQCMD DISPLAY SETTINGS MGRNAME(qmgrname)
where CANSMQ is the name of your started task for the monitoring agent and qmgrname
is the name of the queue manager. The MGRNAME parameter is optional; if you omit it,
the option settings for all monitored queue managers are displayed.
3. Change any options that you want:
F CANSMQ,KMQCMD command
where CANSMQ is the name of your started task for the monitoring agent and command
is the command syntax for the monitoring option you want to enable.
Continue to issue commands as needed.
Remember that the commands you enter remain in effect only while the monitoring agent
is running.
UNIX
On UNIX, you can change monitoring options by editing the mq.cfg monitoring file. If
your site has multiple queue managers, you may have created multiple instances of the
monitoring agent, each with its own uniquely named monitoring file pointing to a single
queue manager. You can customize monitoring options in any or all of these monitoring
files.
Steps
To edit the mq.cfg monitoring file, follow these steps:
1. If you are unfamiliar with the various monitoring options and the commands to enable
them, review the descriptions of the options in this chapter.
If you want to collect historical data, you must set the HISTORY option to YES on the
PERFORM STARTMON statement in the monitoring file. (For information about using
the historical data collection function see the CandleNet Portal online help and the
Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products.)
2. When you are ready to customize the monitoring file(s), do the following:
I
Edit the mq.cfg monitoring file as described in Installing and Setting up IBM Tivoli
OMEGAMON XE for WebSphere Business Integration on Windows and UNIX.
I Add, delete, or modify monitoring option commands, as your site requires. Adhere to
these editing rules:
– To continue a command onto the next line, end the current line with a hyphen (-).
– Parameters you set when grouping objects are effective for all the objects in the
group.
– You can override parameters for an object in a group by explicitly defining
parameters for that object.
3. Verify that the queue manager and its command server are running.
4. Restart each monitoring agent for your changes to take effect.
Windows
On Windows, you can change monitoring options by editing the mq.cfg monitoring file.
If your site has multiple queue managers, you may have created multiple instances of the
monitoring agent, each with its own uniquely named monitoring file pointing to a single
queue manager. You can customize monitoring options in any or all of these monitoring
files.
Steps
To edit the mq.cfg monitoring file, follow these steps:
1. If you are unfamiliar with the various monitoring options and the commands to enable
them, review the descriptions of the options in this chapter.
If you want to collect historical data, you must set the HISTORY option to YES on the
PERFORM STARTMON statement in the monitoring file. (For information about using
the historical data collection function see the CandleNet Portal online help and the
Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products.)
2. From the Manage Candle Services panel, under Service, select:
I WebSphere MQ Monitoring Agent -- instance
where instance is the name of the agent instance for which you want to change
monitoring options.
3. On the toolbar, click Actions > Reconfigure.
4. Verify settings or change as needed and click OK.
5. Click Yes when you are prompted to update the mq_instance.file.
6. Click OK.
A Notepad session opens.
7. Add, delete, or modify monitoring option commands as required for your site. Adhere to
the following editing rules:
I To continue a command onto the next line, end the current line with a hyphen (-).
I Parameters you set when grouping objects are effective for all the objects in the group.
I You can override parameters for an object in a group by explicitly defining parameters
for that object.
8. Close the Notepad.
9. Click Yes at the next prompt to continue.
10. Verify that your queue manager and its command server are running.
11. Restart the agent for the changes to take effect.
NonStop
On HP NonStop Kernel (formerly known as Tandem), you can change monitoring
options by editing the MQCFG monitoring file. If your site has multiple queue managers,
you may have created multiple instances of the monitoring agent, each with its own
uniquely named monitoring file (MQCFGx) pointing to a single queue manager. You can
customize monitoring options in any or all of these monitoring files.
Steps
To edit the MQCFG (or MQCFGx) monitoring file, follow these steps:
1. If you are unfamiliar with the various monitoring options and the commands to enable
them, review the descriptions of the options in this chapter.
If you want to collect historical data, you must set the HISTORY option to YES on the
PERFORM STARTMON statement in the monitoring file. (For information about using
the historical data collection function see the CandleNet Portal online help and the
Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products.)
2. When you are ready to customize the monitoring file(s), do the following:
I If you are not already at the volume.subvolume containing the data files, move there
now:
TACL> VOLUME $VOL.CCMQDAT
where $VOL is your installation volume. If you changed the name of the default
subvolume, enter the new name.
I Edit MQCFG (or MQCFGx) and add, delete, or change the command statements to
reflect the monitoring options you want to enable.
Refer to these general editing rules:
– To continue a command onto the next line, end the current line with a hyphen (-).
– Parameters you set when grouping objects are effective for all the objects in the
group.
– You can override parameters for an object in a group by explicitly defining
parameters for that object.
3. When you have finished customizing the monitoring file(s), save your changes and exit.
4. Verify that your queue manager and its command server are running.
5. Restart the agent for the changes to take effect.
OS/400
On OS/400, you can change monitoring options using the agent management program.
(You can also use the agent management program to start, stop, delete, replicate, view
status, display the log for, or change CMS configuration for one or more OMEGAMON
Monitoring Agents for WebSphere MQ on the same OS/400 system.)
Steps
To edit the monitoring file, follow these steps:
1. If you are unfamiliar with the various monitoring options and the commands to enable
them, review the descriptions of the options in this chapter.
If you want to collect historical data, you must set the HISTORY option to YES on the
PERFORM STARTMON statement in the monitoring file. (For information about using
the historical data collection function see the CandleNet Portal online help and the
Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products.)
2. When you are ready to customize the monitoring file, from an OS/400 command line
enter the following command:
WRKOMAMQ
The main panel for working with the OMEGAMON Monitoring Agent for WebSphere MQ
displays.
On this panel, multiple monitoring agents can be listed. These agents on an OS/400
system (and the unique monitoring file associated with each agent) are differentiated by a
unique 5-character numeric suffix. The first agent Added is automatically assigned suffix
00001, the second agent Added is automatically assigned suffix 00002, and so on.
3. Enter 2 in the Option column next to the agent whose monitoring file you want to
change.
The panel for changing the OMEGAMON Monitoring Agent for WebSphere MQ displays.
4. Press F8 to change the monitoring file associated with the agent.
An editing panel opens.
5. Insert, Delete, or modify monitoring option commands, as your site requires. Adhere to
these editing rules:
I
To continue a command onto the next line, end the current line with a hyphen (-).
I
Parameters you set when grouping objects are effective for all the objects in the group.
I You can override parameters for an object in a group by explicitly defining parameters
for that object.
6. When you have finished customizing the monitoring file, press F3 to save your changes
and exit. Press F3 twice more to exit the interface.
7. Verify that the queue manager and its command server are running.
8. Restart the agent for your changes to take effect.
3
Introduction
This chapter briefly describes selected features of this monitoring product.
Chapter Contents
Error Log Monitoring Feature (non-z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Message Manipulation Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Message Statistics Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Queue Statistics Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Enhanced Integration Using IBM Tivoli OMEGAMON DE . . . . . . . . . . . . . . . . . . . . . 73
Queue-Sharing Group Monitoring Feature (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . 75
Selected Features 63
Error Log Monitoring Feature (non-z/OS only)
Description
The Error Log monitoring feature allows you to view and monitor WebSphere MQ error
log data retrieved from a monitored queue manager (non-z/OS only). It does not provide
error log data associated with unknown queue managers or with client applications.
This feature provides data for the Error Log workspace, provides you with Error Log
attributes that you can use in situations, and provides the predefined situation:
MQSeries_Channel_Out_Of_Sync.
For details about attributes, predefined situations, and workspace provided with this
product, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of
the CandleNet Portal online help.
Details of operation
Note Error Log data is only available if it is being collected for the queue manager. This
product’s monitoring of the queue manager error log (non-z/OS only) is active by default.
However, you can deactivate the error log monitoring feature using the ERRLOGCYCLE
parameter of the SET MANAGER or SET GROUP monitoring option. You can also adjust
the maximum number of messages displayed in the Error Log workspace using the
ERRLOGMAX parameter of the SET MANAGER or SET GROUP monitoring option. See
“Customizing Monitoring Options” on page 27 for details.
This product monitors error logs found in the following default locations.
On HP NonStop Kernel (formerly known as Tandem):
qmvolume.qmsubvolumeL
where qmvolume is the WMQ installation volume (defined also in the "PARAM
MQDEFAULTPREFIX" variable in the startup script)
and where qmsubvolume is the queue manager "logs" (L) subvolume.
For example, in this error log:
$CLX9.QMGR004L.MQERRLG1
the qmvolume is $CLX9 and the qmsubvolume is QMGR004.
On OS/400:
/QIBM/UserData/mqm/qmgrs/qmname/errors
where qmname is the queue manager name.
On UNIX:
/var/mqm/qmgrs/qmname/errors
where qmname is the queue manager name.
On Windows:
<MQ WorkPath>\qmgrs\qmname\errors
Selected Features 65
Message Manipulation Features
Description
The Message Manipulation features of IBM Tivoli OMEGAMON XE for WebSphere MQ
Monitoring allow you to manipulate queued WebSphere MQ messages in these ways:
I
Browse a message's header or its contents, or delete the message.
I
Delete a message from the Dead-Letter Queue.
I
Forward a message (from the DLQ) to its original destination queue or (from the
DLQ) to a different destination queue.
The forward message function applies only to messages in the DLQ and is accessed from
the Dead-Letter Queue Messages workspace (see “Dead-Letter Queue Messages” on
page 87). You can also browse and delete messages displayed in this workspace. The
browse and delete messages functions that apply to messages on other queues are
accessed from the Queue Messages workspace (see “Queue Messages” on page 99).
Details of operation
Because of their potential for serious damage, the message-manipulation features have
the special security considerations described below.
simply accept the default setting of DESC, which enables users to browse message
descriptors in summary or detail reports. Or you can change the default to DATA to allow
users to browse message contents. Be aware, however, that these settings will
apply to all user IDs at your site. If someone at your site needs to be able to delete
messages, you must set MSGACCESS to DELETE, thereby giving all user IDs permission
to delete messages.
IBM recommends that you use the MSGACCESS option only in conjunction
with WebSphere MQ security. The WebSphere MQ security settings on the CandleNet
Portal user ID are passed to the Candle Management Server and then to the monitoring
agent. Using the two options together ensures that user IDs have only the message access
that they need.
If a user attempts to view a message report without the proper access, the following
message is displayed:
(KMQW000W)2035-Not_Authorized
The table below illustrates the combination of MSGACCESS settings and WebSphere MQ
settings that a user ID would require for the various levels of access to queue manager
messages.
The WebSphere MQ
The MSGACCESS setting Security Access to the
For this level of message for the queue manager queue for the user ID must
access . . . must be . . . be . . .
List the messages on a queue DESC or RETRY or DATA or MQGET (with the browse
(display the Queue Messages DELETE option)
workspace)
Browse a message’s descriptor DESC or RETRY or DATA or MQGET (with the browse
DELETE option)
Retry a message on the RETRY or DATA or DELETE MQGET (without the browse
dead-letter queue or forward a option)
message on the dead-letter
queue to another queue
Browse a message’s contents DATA or DELETE MQGET (with the browse
option)
Delete a message DELETE MQGET (without the browse
option)
Procedure
The following procedure is an example of a best practice to implement security for your
queue manager messages:
1. Create new user IDs
On each WebSphere MQ node to be monitored, create new user IDs that correspond to
the CandleNet Portal user IDs that you set up for users to access IBM Tivoli OMEGAMON
XE for WebSphere MQ Monitoring. Note that when sending a command to WebSphere
Selected Features 67
Message Manipulation Features
MQ, CandleNet Portal sends the user ID as typed on the Logon dialog with the casing
preserved exactly as typed.
2. Customize the WebSphere MQ security environment
Customize each node’s WebSphere MQ security environment to either allow or
disallow the new user IDs access to that node’s WebSphere MQ queues. These user IDs
are then passed to WebSphere MQ as alternate user IDs. Keep this in mind when
assigning access to WebSphere MQ queues.
If you allow a user ID access to a particular queue or set of queues, that user will have
access to queue manager messages as specified by the MSGACCESS setting (refer to the
table above). If you disallow the user ID access to a queue or group of queues, that user
will not have access to queue manager messages as specified by the MSGACCESS
setting.
Description
The Message Statistics feature provides summarized statistics about all messages on a
particular queue.
This feature provides data for the Message Statistics workspaces (for an overview, see
“Message Statistics” on page 101), provides you with Message Statistics attributes that
you can use in situations, and provides predefined situation examples:
MQSeries_Delayed_Message_Group and MQSeries_High_Delayed_Messages.
Message statistics can also be stored historically. The data that is kept historically for
message statistics is directly determined by the active situations for the Message Statistics
attribute group.
For details about attributes, predefined situations, and workspace provided with this
product, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of
the CandleNet Portal online help.
Details of operation
Unlike many other types of data collection performed by this monitoring product,
message statistics are collected “on request only” and sampling interval is not used. When
these statistics are requested, each message in the specified queue is read and processed
to provide the summarized message statistics.
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring requests message statistics
data collection whenever you open or refresh one of the Current Message Statistics
workspaces (that is, whenever you query the Message Statistics attribute group).
To view the Current Message Statistics workspaces, WebSphere MQ Security Access to
the selected queue for your CandleNet Portal Logon user ID must be MQGET (with the
browse option). Additionally, user access to messages on the queue must be allowed. This
can be adjusted during customization using the MSGACCESS parameter of the SET
GROUP and SET MANAGER monitoring option. Any value other than
MSGACCESS(NONE) allows collection of message statistics. The default setting of
MSGACCESS(DESC) enables all users to browse message statistics workspaces. If you
attempt to view one of the Current Message Statistics workspaces without the proper
access, no data is returned.
The behavior of the Recent Message Statistics workspace differs from that of other
“Recent” workspaces of this monitoring product. The Recent Message Statistics
workspace displays all rows associated with the requested queue currently held by the
agent waiting to be written to history. If there are no active situations associated with the
Message Statistics attribute group for the requested queue, then no rows are returned.
Once written to history, the data no longer displays in the Recent Message Statistics
workspace. This is normal operation for the Recent Message Statistics workspace.
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring also requests message
statistics data collection whenever a situation uses the Message Statistics attributes. A
Selected Features 69
Message Statistics Feature
situation drives the collection of message statistics data for a particular queue name. The
queue name is a required input attribute for message statistics situations and if it is not
specified, then no data will be collected. Note the Queue Name attribute must specify an
individual queue name, no wild cards are allowed. A separate situation must be created
for every queue that is to be monitored. Because of the overhead of collecting message
statistics data, it should only be collected for those queues that need to be closely
monitored. Note that for situations, the user ID of the monitoring agent is used to access
the queue.
Many of the message statistics are calculated using the put-date-and-time of the message
in the queue. If the queue will have messages with put-date-and-times that do not reflect
accurately when the message was put into the input queue, then the statistics will be
correspondingly inaccurate. Put-date-and-times are not accurate indicators when origin
context is preserved or set for a message during the put by an application to the queue.
This commonly occurs when an application is a message mover that moves messages
from one queue to another, or when any application passes or sets origin context for a
message.
If there is no data returned for Message Statistics situations or workspaces, refer to the
agent log to determine the reason. Messages KMQMI209E and KMQMI210E are
associated with this feature.
Description
The Queue Statistics feature provides additional current and historical information about
message arrival and departure rates, high queue depth, and time when latest activity
occurred.
This information allows you to better monitor queue activity, such as determining whether
activity is at expected levels, whether messages are being read from the queues within a
reasonable timeframe, or whether messages are being put on a queue and not retrieved.
This optional feature provides additional data in the Queue Statistics and Queue Manager
Status workspaces, provides additional Queue Statistics attributes for use in situations,
and provides data for the predefined situation:
MQSeries_No_Queue_Messages_Read.
For details about attributes, predefined situations, and workspace provided with this
product, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of
the CandleNet Portal online help.
Details of operation
Note that queue statistics data is only available if it is being collected for the queue or
queues. This product’s monitoring for queue statistics data is turned off by default to
ensure downward compatibility. It can be activated if you specify STATISTICS(YES) on
the SET QUEUE monitoring option for the queue or queues you want to monitor. See
“Customizing Monitoring Options” on page 27 for descriptions of monitoring options.
Use of this feature effects processing of other information and has the requirements and
restrictions described below.
Requirement
On all platforms, monitored queue managers must have the PERFMEV attribute that
determines whether or not performance-related events are generated set to ENABLED.
Selected Features 71
Queue Statistics Feature
have certain queue statistics available unless Application Queue Statistics monitoring is
active on z/OS (SET APPL STATISTICS(ALL|NODYNAMQ)).
Description
The optional Tivoli OMEGAMON DE version of IBM Tivoli OMEGAMON XE for
WebSphere MQ Monitoring (“the monitoring product” in the discussion below) gives you
the ability to easily change the parameters of specific WebSphere MQ objects (queue
managers, queues, channels, and so on) by providing cross-product access to the Tivoli
OMEGAMON DE version of IBM Tivoli OMEGAMON XE for WebSphere MQ
Configuration (“the configuration product” in the discussion below).
Details of operation
Upgrading to the optional DE feature gives you a more integrated view of your
WebSphere MQ environment. This integration allows you to select certain attributes of a
WebSphere MQ resource as displayed in the monitoring product’s workspaces and, if the
values are not to your liking, you can easily change them. The change will be deployed
immediately.
For example, you are using the monitoring product’s Channel Performance workspace
and you notice a problem with a SYSTEM.DEF.SENDER channel. You can select the
channel, right-click and, from the pop-up menu, select Configure Channel.
Selected Features 73
Enhanced Integration Using IBM Tivoli OMEGAMON DE
The following table lists the workspaces from which these additional actions using Tivoli
OMEGAMON DE are available.
Your user ID must have modify WebSphere MQ Configuration permission in order to use
this feature.
Description
The Queue-Sharing Group monitoring feature provides the ability to monitor and display
data unique to WebSphere MQ queue managers in a Sysplex environment that have
been configured to form queue-sharing groups.
This feature provides a number of workspaces on z/OS only, provides additional Queue
Statistics attributes for use in situations, and provides data for a number of predefined
situations (named in the form MQSeries_QSG_*).
For details about attributes, predefined situations, and workspace provided with this
product, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of
the CandleNet Portal online help. For a navigational introduction to the Queue-Sharing
Group workspaces, see page 98.
Details of operation
If there are no queue-sharing groups associated with your queue managers then you do
not need to take any further action.
To successfully monitor queue-sharing groups, install a WebSphere MQ monitoring agent
on the host system of each queue manager that participates in the queue-sharing group
(and ensure that the agent is configured to monitor those queue managers).
The default behavior of the agent is to monitor all queue-sharing groups that are
associated with monitored queue managers. This default behavior can be adjusted, if
necessary (see the SET QSG monitoring option and the QSGCHKINTERVAL and
GRPNAME parameters of the PERFORM STARTMON monitoring option). Also, all
WebSphere MQ monitoring agents that monitor queue managers in queue-sharing
groups should use the same sample interval length (refer to the SAMPINT parameter of
the PERFORM STARTMON monitoring option).
For information about queue-sharing groups see the IBM WebSphere MQ for z/OS
Concepts and Planning Guide.
Selected Features 75
Queue-Sharing Group Monitoring Feature (z/OS only)
4
Introduction
This chapter provides an introduction to the types of predefined workspaces provided in
the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring user interface.
Chapter contents
About Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Application Debugging (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Application Statistics (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Buffer Pool Statistics (z/OS only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Channel Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Channel Initiator Status (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Channel Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Cluster Queue Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Dead-Letter Queue Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Error Log (non-z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Log Manager Performance (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Message Manager Performance (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
MQSeries Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Page Set Statistics (z/OS only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Queue Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Queue Manager Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Queue Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Queue-Sharing Group (z/OS only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Queue Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Message Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Workspaces 77
About Workspaces
About Workspaces
Overview
IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring is installed with default views
that are displayed in workspaces. Where applicable, links have been provided within the
workspace to link from a parent view to a more detailed view about a selected row, or to a
related workspace (for example, a workspace containing historical information).
The format and appearance of the views within a workspace may be customized to suit
your preferences. For information on customizing workspaces and views, refer to the
CandleNet Portal online help.
For a complete list of all workspaces included with this product and for detailed
descriptions of workspaces and individual attributes within a workspace, see the IBM
Tivoli OMEGAMON XE for WebSphere MQ Monitoring section of the CandleNet Portal
online help.
Workspaces 79
Application Statistics (z/OS only)
Workspaces 81
Buffer Pool Statistics (z/OS only)
You can also consult the Page Set Statistics workspace to review the performance of the
page sets associated with a specific buffer pool ID (see “Page Set Statistics (z/OS only)” on
page 94).
Channel Definitions
Workspaces 83
Channel Initiator Status (z/OS only)
Channel Performance
Workspaces 85
Cluster Queue Manager
Workspaces 87
Dead-Letter Queue Messages
1. Within the Dead-Letter Queue Messages workspace, right-click on the message you want
to forward.
2. From the pop-up menu, select MQ Commands > Forward.
A dialog, showing the original destination queue of the message and the current queue
manager, appears.
3. Fill in the dialog:
I In the Queue name field, enter the name of the queue to send the message to.
I In the Queue Manager field, enter the name of the queue manager for the queue
that you specify in the Queue name field.
then click Yes.
4. The message is forwarded and then deleted from the dead-letter queue. The status of
your forward request appears; click OK to clear the status message.
Note: If you forward a segmented or grouped message, IBM Tivoli OMEGAMON XE for
WebSphere MQ Monitoring forwards the entire logical message.
Workspaces 89
Error Log (non-z/OS only)
Workspaces 91
Message Manager Performance (z/OS only)
MQSeries Events
Workspaces 93
Page Set Statistics (z/OS only)
Queue Definitions
Workspaces 95
Queue Manager Status
Queue Statistics
Workspaces 97
Queue-Sharing Group (z/OS only)
ENTERPRISE
OS/390 Systems
SP01
MQSERIES
QM01
QM02
QM03
QM04
QM05
Queue-Sharing Group
Queue Messages
Workspaces 99
Queue Messages
Message Statistics
Workspaces 101
Message Statistics
A on Non-Supported Platforms
Introduction
IBM assumes that you will install the OMEGAMON Monitoring Agent for WebSphere MQ
on each supported operating system platform. However, you can use the procedure
below to monitor events only on non-supported platforms. This procedure causes event
data to be stored in a monitored queue manager.
Procedure
1. In the queue manager on the non-supported platform, define the system event queues as
QREMOTE and residing in your monitored queue manager.
2. In the queue manager on the non-supported platform, enable events. Events must be
recorded in Coordinated Universal Time (CUT).
3. Enable monitoring of the queue manager on the supported platform to which the events
on the non-supported platform are sent.
B
Introduction
This appendix documents the KMQ-prefixed messages that are produced by the IBM
Tivoli OMEGAMON XE for WebSphere MQ monitoring feature, and certain messages
which may appear in the Windows Event Log.
Appendix contents
KMQ messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Windows Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Messages 105
KMQ messages
KMQ messages
The following messages have numbers in the form KMQccnnns, where cc is the
component identifier, nnn is a three-digit numeric identifier, and s is the message severity
(error, warning, informational, severe). The messages are listed alphabetically by cc, then
numerically within that group.
Note: Messages KMQ**001E through KMQ**005E apply to multiple components,
where the ** will be any of the various component identifiers.
User Response: If tracing is required and cannot be activated, note the message
text, and contact IBM Software Support.
Messages 107
KMQ messages
User Response: Correct the command, and resubmit it. For complete command
descriptions, see the chapter “Customizing Monitoring Options” in this guide.
User Response: Note the message text, and contact IBM Software Support.
Messages 109
KMQ messages
User Response: Correct the PERFORM STARTMON command, and resubmit it.
For complete command descriptions, see the chapter “Customizing Monitoring
Options” in this guide.
User Response: Correct the command, and resubmit it. For complete command
descriptions, see the chapter “Customizing Monitoring Options” in this guide.
Messages 111
KMQ messages
KMQCI145I command
Explanation: The command command was returned and processed.
System Action: The command is executed.
User Response: None.
Messages 113
KMQ messages
User Response: Specify either the MGRNAME (manager name) or GROUP (group
name) operands for the given queue or channel mask being set, and reenter the
command. The RMGRNAME parameter is no longer supported.
User Response: Correct and resubmit the command. For more information about
the GROUP and MGRNAME parameters, see the chapter “Customizing Monitoring
Options” in this guide.
KMQCI156E The group specified in the SET EVENTQIN |EVENTQOUT command does not
exist.
KMQCI156E The group must be defined before this command is issued
Explanation: The syntax for the SET EVENTQIN or SET EVENTQOUT
command was correct, but the group name specified in the GROUP option has not
been defined to IBM Tivoli OMEGAMON XE for WebSphere MQ.
System Action: The command is ignored. Processing continues.
User Response: Use the SET GROUP command to define the remote queue
manager, and resubmit the command. For instructions on using SET GROUP, see the
chapter “Customizing Monitoring Options” in this guide.
Messages 115
KMQ messages
User Response: Correct the SET MQIMONITOR command, and resubmit it. For
instructions on using SET MQIMONITOR, see the chapter “Customizing Monitoring
Options” in this guide.
KMQCI309I Remote QMgr rmgrname is monitored via local queue manager mgrname
Explanation: The DISPLAY SETTINGS command shows that the specified
remote manager rmgrname is monitored using a connection with the specified local
manager mgrname.
User Response: None.
KMQCI311I ROUTE(route_list)
Explanation: The DISPLAY SETTINGS command is continuing to display
information about a GROUP or RMANAGER by showing the ROUTE list that has
been set.
User Response: None.
KMQCI312I RUSERID(remote_userid)
Explanation: The DISPLAY SETTINGS command is continuing to display
information about a GROUP or RMANAGER by showing the remote userid that has
been set.
Messages 117
KMQ messages
KMQCI313I REPLYTOQMGR(mgrname)
Explanation: This message is one of several possible messages given in
response to a DISPLAY SETTINGS command. It gives the REPLYTOQMGR name
specified for the group or remote queue manager being addressed by the response.
User Response: None.
KMQCI322I eventqueuein|eventqueueout:
KMQCI322I QMGRQ(queue_manager_event_queue)
KMQCI322I PERFMQ(performance_event_queue)
KMQCI322I CHANNELQ(channel_event_queue)
KMQCI322I CONFIGQ(config_queue)
Explanation: This message is issued in response to a DISPLAY SETTINGS
command. It provides information about the names defined using the SET
EVENTQIN and SET EVENTQOUT commands.
User Response: None.
Messages 119
KMQ messages
Messages 121
KMQ messages
Messages 123
KMQ messages
Messages 125
KMQ messages
KMQMI106I Initialization completed, System sysid QMgr mgrname Waiting for Server
initiation message
Explanation: Initialization of the IBM Tivoli OMEGAMON XE for WebSphere
MQ monitoring agent has completed for the queue manager named mgrname on the
local system named sysid. The OMEGAMON XE agent now waits for Candle
Management Server initiation.
User Response: None.
KMQMI115E Start time for QMgr mgrname not available, because reason_text.
RC=return_code
Explanation: The IBM Tivoli OMEGAMON XE for WebSphere MQ monitoring
agent could not determine the start date and time of the queue manager named
mgrname, for one of the following reasons:
I
Unable to create temporary file name: A temporary file for receiving the
output from the ps -ef command could not be allocated.
I Unable to open file for output: The temporary file used to receive output from
ps -ef could not be opened.
I
WebSphere MQ manager not started: Queue manager mgrname has not been
started.
Messages 127
KMQ messages
System Action: Processing continues without start date and time information.
User Response: Note the message text, and contact IBM Software Support.
Messages 129
KMQ messages
User Response: Verify that you have defined a dead-letter queue for this queue
manager. If you have and this problem persists, note the message text, and contact
IBM Software Support.
Messages 131
KMQ messages
KMQMI148E Queue qname does not exist, STATUS(DELETE) is invalid. SET QUEUE
ignored
Explanation: A SET QUEUE command with STATUS(DELETE) refers to a
queue qname that does not exist.
System Action: The command is ignored. Processing continues.
User Response: If you misspelled the queue name, correct the command, and
resubmit it. Otherwise, the queue you specified for deletion does not exist, so no
action is necessary. For complete command descriptions, see the chapter
“Customizing Monitoring Options” in this guide.
KMQMI152E SET QUEUE refers to a MGRNAME mgrname that does not exist. SET
QUEUE ignored
Explanation: A SET QUEUE command refers to a queue manager that has not
previously been specified.
System Action: The command is ignored. Processing continues.
User Response: Either change the mgrname to one that has previously been
specified, or replace the MGRNAME option with a valid GROUP option. For
complete command descriptions, see the chapter “Customizing Monitoring Options”
in this guide.
KMQMI153E SET QUEUE refers to a GROUP group that does not exist. SET QUEUE
ignored
Explanation: A SET QUEUE command refers to a group that has not been
previously specified.
System Action: The command is ignored. Processing continues.
User Response: Either change the group to one that has previously been specified,
or replace the GROUP option with a valid MGRNAME option. For complete
command descriptions, see the chapter “Customizing Monitoring Options” in this
guide.
KMQMI154E SET CHANNEL refers to a MGRNAME mgrname that does not exist. SET
Messages 133
KMQ messages
CHANNEL ignored
Explanation: A SET CHANNEL command refers to a queue manager that has
not been previously specified.
System Action: The command is ignored. Processing continues.
User Response: Either change the mgrname to one that has previously been
specified, or replace the MGRNAME option with a valid GROUP option. For
complete command descriptions, see the chapter “Customizing Monitoring Options”
in this guide.
KMQMI155E SET CHANNEL refers to a GROUP group that does not exist. SET CHANNEL
ignored
Explanation: A SET CHANNEL command refers to a group that has not been
previously specified.
System Action: The command is ignored. Processing continues.
User Response: Either change the group to one that has previously been specified,
or replace the GROUP option with a valid MGRNAME option. For complete
command descriptions, see the chapter “Customizing Monitoring Options” in this
guide.
KMQMI156E SET QUEUE refers to a queue mask queue_mask that does not exist in
group |mgrname. SET QUEUE ignored
Explanation: The SET QUEUE command cannot delete the indicated
queue_mask because it has not been previously specified for the associated group or
mgrname.
System Action: The command is ignored. Processing continues.
User Response: If necessary, change the group or mgrname to one that has
previously been specified. For complete command descriptions, see the chapter
“Customizing Monitoring Options” in this guide.
KMQMI157E SET CHANNEL refers to a channel mask chlmask that does not exist in
group |mgrname. SET CHANNEL ignored
Explanation: The SET CHANNEL command cannot delete the indicated
chlmask because it has not been previously specified for the associated group or
mgrname.
System Action: The command is ignored. Processing continues.
User Response: If necessary, change the group or mgrname to one that has
previously been specified. For complete command descriptions, see the chapter
“Customizing Monitoring Options” in this guide.
Messages 135
KMQ messages
User Response: If this is expected as the result of the queue manager going
inactive or the agent shutting down, no action is needed. If this occurs unexpectedly,
note the message text, and contact IBM Software Support.
Messages 137
KMQ messages
KMQMI179E Value specified for SET AGENT is too long. Value truncated.
Explanation: The specified NAME parameter of the SET AGENT command is
longer than 8 characters; 8 characters is the maximum length for this parameter.
System Action: The name is truncated to 8 characters.
User Response: Specify a name with 8 characters or fewer, and resubmit the
command.
KMQMI182I Maximum delayed events queued awaiting online status; older events will
roll off
Explanation: WebSphere MQ events notification for situations using the
MQSeries_Events attribute group has been delayed until the IBM Tivoli OMEGAMON
XE for WebSphere MQ monitoring agent is fully online.
System Action: Because the maximum number of events that can be retained has
been reached, the agent will no longer retain the oldest event for each new event it
intercepts.
User Response: This message can occur at startup when the monitored queue
manager's event queues have many back-logged event messages. Determine the
reason for either the OMEGAMON XE agent's inability to come online or its loss of
online status, and correct the problem.
This may occur due to a communication failure with the Candle Management Server
(CMS). If this is a new monitoring environment, communication parameters such as
CTIRA_CELL_NAME may need adjustment. If the problem persists, contact IBM
Software Support.
KMQMI185E Error in writing to filename file. Write is not successful or data lost
Explanation: An error occurred when trying to write data to the specified file.
System Action: The write is unsuccessful. The data written is lost.
User Response: Ensure enough disk space is available for a write operation and
that there are no other file system problems, and retry the operation.
Messages 139
KMQ messages
KMQMI203W event_count events lost in Event Log for queue manager mgrname
Explanation: During the time that event logging was disabled, the specified
number of events event_count from queue manager mgrname were not recorded into
the persistent datastore. The time at which event logging was disabled is indicated by
the preceeding message KMQMI170E.
System Action: Event-log recording resumes.
User Response: If event-log integrity is critical, resolve the original problem
reported in message KMQMI170E.
KMQMI204W Directory name dirname is too long and ignored. The maximum allowed
Messages 141
KMQ messages
length is maxlen.
Explanation: The directory name dirname you specified using the SET
EVENTLOG command or the CTIRA_HIST_DIR environment variable is too long.
The maximum length of a directory name is maxlen.
System Action: The specified directory name is ignored.
User Response: Specify a valid directory name under the maximum allowable
length.
KMQMI209E Situation sitname for message statistics attribute group must specify single
queue name.
Explanation: The specified situation sitname must specify a queue name plus
an equal operator. A separate situation must be written for each individual queue.
The reason for this requirement is the overhead of collecting these data—this
information should only be collected for specific queues that need to be closely
monitored.
System Action: No rows are returned for the requested situation.
User Response: Modify the situation to specify a specific queue name for the
qname attribute.
Messages 143
KMQ messages
2080 Truncated_Msg_Failed
2082 Unknown_Alias_Base_Q
2085 Unknown_Object_Name
2086 Unknown_Object_Q_Mgr
2087 Unknown_Remote_Q_Mgr
2091 Xmit_Q_Type_Error
2092 Xmit_Q_Usage_Error
2099 Signal1_Error
2100 Object_Already_Exists
2101 Object_Damaged
2102 Resource_Problem
2109 Suppressed_By_Exit
2110 Format_Error
2111 Source_CCSID_Error
2112 Source_Integer_Enc_Error
2113 Source_Decimal_Enc_Error
2114 Source_Float_Enc_Error
2115 Target_CCSID_Error
2116 Target_Integer_Enc_Error
2117 Target_Decimal_Enc_Error
2118 Target_Float_Enc_Error
2119 Not_Converted
2120 Converted_Msg_Too_Big
2130 Adapter_Serv_Load_Error
2133 Adapter_Conv_Load_Error
2136 Multiple_Reasons
2140 CICS_Wait_Failed
2152 Object_Name_Error
2153 Object_Q_Mgr_Name_Error
2154 Recs_Present_Error
2155 Object_Records_Error
2156 Response_Records_Error
2157 ASID_Mismatch
2161 Q_Mgr_Quiescing
2162 Q_Mgr_Stopping
2183 API_Exit_Load_Error
2184 Remote_Q_Name_Error
2186 GMO_Error
2192 Pageset_Full
2193 Pageset_Error
2194 Name_Not_Valid_For_Type
2195 Unexpected_Error
2196 Unknown_Xmit_Q
2197 Unknown_Def_Xmit_Q
2198 Def_Xmit_Q_Type_Error
2199 Def_Xmit_Q_Usage_Error
2201 Name_In_Use
2202 Connection_Quiescing
2203 Connection_Stopping
2204 Adapter_Not_Available
2209 No_Msg_Locked
2217 Connection_Not_Authorized
2219 Call_In_Progress
2241 Incomplete_Group
2242 Incomplete_Msg
2243 Inconsistent_CCSIDs
2244 Inconsistent_Encodings
2245 Inconsistent_UOW
2246 Invalid_Msg_Under_Cursor
2247 Match_Options_Error
2255 UOW_Not_Available
2256 Wrong_GMO_Version
9002 Unsupported CCSID found.
9005 Insufficient Storage
9008 Not allowed by MSGACCESS value
9009 Agent timeout occurred
System Action: No rows are returned.
User Response: Resolve the problem indicated by the reason code.
Messages 145
KMQ messages
Messages 147
KMQ messages
handles that can be held by a single task) for the queue manager named mgrname.
Data collection for queues in the indicated queue manager cannot be completed.
System Action: Data for some queues will not be available for display. IBM Tivoli
OMEGAMON XE for WebSphere MQ requires that you monitor the MAXHANDLES
value for the number of queues you have defined to each queue manager plus a fixed
overhead of three queues.
User Response: Issue an ALTER QMGR MAXHANDS(nnnn) command to the
queue manager, where nnnn is greater than or equal to the number of queues defined
to that queue manager plus three.
KMQMQ117E command_text
Explanation: This message contains the text of the DISPLAY command that
timed out. The KMQMQ116E message precedes this message.
System Action: Data collection for the resource cannot be performed.
User Response: Investigate the queue manager, and determine why it did not
respond to the WebSphere MQ operator command. Possible causes include the
command server not running and performance problems in the queue manager
address space. If problems persist, note the message text, and contact IBM Software
Support.
KMQMQ125W Current Events Table lock failure. Obsolete events not removed for
QMgr=mgrname
Explanation: An error prevented the acquisition of the lock for the current
events table.
System Action: Any expired or obsolete events remain in the table.
User Response: If problems persist, note the message text, and contact IBM
Software Support.
Messages 149
KMQ messages
KMQMQ200E MQI monitoring for QMgr mgrname not started, invalid environment
KMQMQ200E RC=return_code Reason=reason_code
Explanation: Monitoring of the WebSphere MQ API could not start because the
specified queue manager mgrname does not meet all environmental requirements.
return_code and reason_code are diagnostic information.
System Action: WebSphere MQ interface monitoring is not started, but the rest of
the product continues normally.
User Response: Verify that the specified queue manager operates without
problems. Also, confirm that the WebSphere MQ version you are running is supported
by IBM Tivoli OMEGAMON XE for WebSphere MQ. If problems persist, note the
message text, and contact IBM Software Support.
Messages 151
KMQ messages
Messages 153
KMQ messages
KMQMQ219E text
Explanation: When attempting to issue a command to WebSphere MQ, the
command response contained a CSQN205I message with an unexpected return code
return_code. The text of this message comprises the command attempted and the
responses to it returned by the command server.
A common cause of this message is that the channel initiator is not running, but that is
by no means the only possible cause.
System Action: In general, the command has failed. Refer to CSQN205I message
and the return code contained within for further explanation.
User Response: If the command is failing because the channel initiator has failed
or has not yet been started, restart it. Correct any conditions associated with the
CSQN205I message. If the command appears to be syntactically or semantically
incorrect or the problem cannot otherwise be resolved, note the text of the
KMQMQ219E messages and those immediately preceeding it, and call IBM Software
Support.
Messages 155
KMQ messages
KMQMQ233W Channel initiator for QMgr mgrname not active. Cluster information cannot
be collected.
Explanation: The channel initiator address space for the queue manager named
mgrname is not active.
System Action: IBM Tivoli OMEGAMON XE for WebSphere MQ cannot collect
some cluster-related and cluster queue manager channnel information. Processing
continues.
User Response: Determine the reason for the channel initiator address space not
being active. In some cases this may be a normal situation. If appropriate start the
channel initiator address space.
KMQMQ234W Channel initiator for QMgr mgrname not active. Cluster information is not
available.
Explanation: The channel initiator address space for the queue manager named
mgrname is now active.
System Action: IBM Tivoli OMEGAMON XE for WebSphere MQ can now collect
cluster-related information, such as cluster queue and cluster queue manager channel
information. Processing continues.
User Response: None.
KMQMQ236W Performance events for QMgr mgrname now enabled. Queue statistics
information now available.
Explanation: The PERFMEV attribute of the queue manager being monitored
has been set to ENABLED. Queue statistics information can now be collected.
System Action: The IBM Tivoli OMEGAMON XE for WebSphere MQ agent
continues monitoring. All available queue statistics data will be collected.
User Response: None.
Messages 157
KMQ messages
System Action: Processing continues, but QSG data collection will probably not
be done.
User Response: Note the message text, and contact IBM Software Support.
Messages 159
KMQ messages
KMQPD101E module Routine for PDS function failed. POST code return_code
Explanation: The persistent datastore routine named module failed for the
specified function. return_code is the post code from the PDS routine.
System Action: If this message occurs several times, WebSphere MQ interface
tracing is disabled.
User Response: Check the RKPDLOG for persistent datastore error messages, and
ensure at least one of the datasets in the RKMQDSA group is available for write
access.
Messages 161
KMQ messages
Messages 163
KMQ messages
User Response: Check the return code return_code and reason code reason_code
from the CTRACEWR macro in the MVS Authorized Assembler Services Reference,
Volume 1.
Messages 165
KMQ messages
Messages 167
Windows Event Log Messages
Overview
When the IBM Tivoli OMEGAMON XE for WebSphere MQ monitoring agent is running
as a system service on Windows, if an error condition or critical event occurs, the agent
writes an application message into the Windows Event Log. (Refer to the installation
documentation for supported versions of Windows.)
Procedure
To access the Application Event Log
1. From the Start menu, select Control Panel.
2. Select Administrative Tools.
3. Select Event Viewer, then select Application.
Messages logged
The following messages (when the condition occurs) appear in the application event log.
Note: The Event ID number corresponds to the KMQ message number.
Message
Event ID Severity Symbolic Name Number
Introduction
The installation documentation for your product or product package provides the basic
disk space requirements for required components such as for the CMS and for CandleNet
Portal. These basic disk space requirements do not include additional space that is
required for maintaining historical data files. Because of the variations in client distributed
systems, system size, number of managed systems, and so on, it is difficult to provide
actual additional disk space requirements necessary for historical data collection. This
chapter provides the system administrator with basic record sizes for each of the tables
from which historical data is collected.
*These tables are not available on platforms other than z/OS. They are not included for determining default
space estimates.
** The Event Log is created for all platforms but cannot be configured via option 3, Customize Historical
Collection, on the HDC Main menu. It is included here since the data is available for use in the same
way as history data. By default, QMEVENTH is automatically archived into CTIRA_HIST_DIR when it
reaches 10MB. The name of the archive is QMEVENTH.arc.
D
If you have a problem with your IBM software, you want to resolve it quickly. This section
describes the following options for obtaining support for IBM software products:
I “Searching knowledge bases” on page 179
I “Obtaining fixes” on page 180
I “Receiving weekly support updates” on page 180
I
“Contacting IBM Software Support” on page 181
Severity 1 The problem has a critical business impact. You are unable to
use the program, resulting in a critical impact on operations.
This condition requires an immediate solution.
E
Overview
This information was developed for products and services offered in the U.S.A. IBM may
not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product, program, or service is
not intended to state or imply that only that IBM product, program, or service may be
used. Any functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's responsibility
to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described
in this document. The furnishing of this document does not give you any license to these
patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors. Changes
are periodically made to the information herein; these changes will be incorporated in
Notices 185
new editions of the publication. IBM may make improvements and/or changes in the
product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience
only and do not in any manner serve as an endorsement of those Web sites. The
materials at those Web sites are not part of the materials for this IBM product and use of
those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs and
other programs (including this one) and (ii) the mutual use of the information which has
been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed material available for it
are provided by IBM under terms of the IBM Customer Agreement, IBM International
Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment.
Therefore, the results obtained in other operating environments may vary significantly.
Some measurements may have been made on development-level systems and there is no
guarantee that these measurements will be the same on generally available systems.
Furthermore, some measurement may have been estimated through extrapolation. Actual
results may vary. Users of this document should verify the applicable data for their specific
environment.
Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM has not
tested those products and cannot confirm the accuracy of performance, compatibility or
any other claims related to non-IBM products. Questions on the capabilities of non-IBM
products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to
change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business operations.
To illustrate them as completely as possible, the examples include the names of
individuals, companies, brands, and products. All of these names are fictitious and any
Trademarks
IBM, the IBM logo, AIX, Candle, Candle Management Server, Candle Management
Workstation, CandleNet, CandleNet Portal, CICS, DB2, developerWorks, eServer,
IBMLink, Informix, iSeries, Lotus, MVS, OMEGAMON, OMEGAMON Monitoring Agent,
OS/400, Passport Advantage, pSeries, Rational, Redbooks, S/390, Tivoli, the Tivoli logo,
Tivoli Enterprise Console, TME, WebSphere, z/OS, and zSeries are trademarks or
registered trademarks of International Business Machines Corporation in the United
States, other countries, or both.
Intel, Intel Inside (logos), MMX, Celeron, Intel Centrino, Intel Xeon, Itanium, Pentium and
Pentium III Xeon are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Notices 187
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks of
others.
Index 189
knowledge bases, searching to find software problem queues to be monitored 36
resolution 179 Queue-Sharing Group monitoring feature 75
L R
Log Manager Performance workspaces, about 91 Resending a message to its original destination 88
M S
manuals sampling interval 45
see publications 9 SET AGENT command 47
Message Manager Performance workspaces, about SET APPL command 49
92
SET CHANNEL command 38
Message Manipulation features 66
SET EVENTLOG command 39
Message Statistics feature 69
SET EVENTQIN command 40
Message Statistics workspaces, about 101
SET EVENTQOUT command 42
monitoring options
as supplied on NonStop, UNIX, Windows, and SET GROUP command 29
OS/400 28 SET MANAGER command 31
as supplied on z/OS 28 SET MQIMONITOR command 52
changing 56 SET QSG command 54
summary of 27 SET QUEUE command 36
MQSeries Events workspaces, about 93 situations
definition 21
predefined 22
O
Software Support
OMEGAMON Platform 18–20
contacting 181
online publications specifying
accessing 9
channels to be monitored 38
ordering publications 9
event queues 40
external customization commands 44
P queue managers to be monitored 31
Page Set Statistics workspaces, about 94 queues to be monitored 36
PERFORM INCLUDE command 44 the event log 39
PERFORM STARTMON command 45 z/OS applications to monitor 49
performance 169 start monitoring 45
Policy Management 20 summary of monitoring options 27
predefined situations 22
Properties editor 21 T
publications
Take Action feature 22
accessing online 9
Tivoli OMEGAMON DE feature package 19
ordering 9
Tivoli OMEGAMON DE integration feature 73
Tivoli software information center 9
Q
queries 22
V
Queue Definitions workspaces, about 95
views
queue manager group 29
definition 21
Queue Manager Status workspaces, about 96
queue managers to be monitored 31
W
Queue Messages workspaces, about 99
Workflow editor 20
Queue Statistics feature 71 workspaces
Queue Statistics workspaces, about 97
Index 191
192 Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, V3.7.0
IBM@
Printed in USA
SC31-6888-00
SC31-6888-00