Download - Using IBM Tivoli OMEGAMON XE for WebSphere MQ ...publib.boulder.ibm.com/tividd/td/ITOMEGAXEfWSMQ/SC... · Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration ... Audit Logging

IBMTivoli®

Version 3.7.0

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

SC31-6889-00

IBM Tivoli OMEGAMON XE for WebSphere MQ

12

1

2

IBMTivoli®

Version 3.7.0

IBM Tivoli OMEGAMON XE for WebSphere MQ

Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

SC31-6889-00

12

1

Eighth Edition (April 2005)

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.

This edition replaces GC32-9327-00.

© Copyright Sun Microsystems, Inc. 1999

© 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

Before using this information and the product it supports, read the information in “Notices” on page 323.

Note

Contents 5

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

What’s New in Version 3.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 1. Introducing Tivoli OMEGAMON XE for WebSphere MQ Configuration . . . . . . 17Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18OMEGAMON Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration?. . . . . . . . . . . . . . .24Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Chapter 2. Viewing Your Current WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . 35Creating Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Entering Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Creating a Configured System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Discovering Your Existing WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . . . .40Reviewing Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Chapter 3. Prototyping Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Introducing Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Using the Global Variables Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Adding, Modifying, or Deleting Global User Variables . . . . . . . . . . . . . . . . . . . . . . . . . .54Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter 4. Creating and Defining Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63What Are Defined Objects? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Using the Configuration Search Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Creating New Queue Managers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69Setting Access Authority for WebSphere MQ Objects. . . . . . . . . . . . . . . . . . . . . . . . . . .73Connecting Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Creating Resource Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Contents

6 Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, V3.7.0

Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Using the Replicate Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Chapter 5. Validating Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Validating Objects in the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Controlling the Amount of Validation Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Chapter 6. Maintaining Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Maintaining Your Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94Viewing Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Updating the Configuration Database from Your Actual Configuration . . . . . . . . . . . . .97Backing Up the Configuration of the Actual Environment . . . . . . . . . . . . . . . . . . . . . . .99Updating Your Actual Configuration from Defined Objects . . . . . . . . . . . . . . . . . . . . .100Working with Queue-Sharing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Exporting or Importing XML Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104Exporting MQSC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Chapter 7. Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111About Action Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Scheduling an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Scheduled Action Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Scheduled Action Details Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Scheduled Action Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Running a Schedule on Demand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Chapter 8. Creating and Defining Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121About the Cluster Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122Clustering Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123Product-Managed Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125Creating a New Managed Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

Chapter 9. Audit Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Audit Logging Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Historical Disk Space Requirements for the Audit Log . . . . . . . . . . . . . . . . . . . . . . . . .141Audit Log Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142

Chapter 10. Backing up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Backing up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144Restoring the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Changing the Configuration Database Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Appendix A. Remote Queue Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153What Is Remote Configuration?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154Setting up Queue Managers for Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . .156Examples of Possible WebSphere MQ Configurations . . . . . . . . . . . . . . . . . . . . . . . . .158

Contents 7

Creating Remote Queue Manager Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

Appendix B. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165KMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166KCF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260KMCRCA Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289KCFCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295Windows Event Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310

Appendix C. Problem Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Problem Determination Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312The Environment File Used by this Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314

Appendix D. Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317

Appendix E. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327


Preface 9

Preface

IBM® Tivoli® OMEGAMON® XE for WebSphere® MQ Configuration 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 Configuration sofware helps you simplify the time-consuming and resource-intensive tasks of defining and managing your WebSphere MQ configuration.

This book describes the features and capabilities of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration and explains how to use it to quickly define and manage your WebSphere MQ configuration.

P

About This Book


About This Book

Who should read this bookThis guide is intended to provide system administrators of WebSphere MQ with the processes involved in preparing IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to help you design and prototype your WebSphere MQ resources.

Although step-by-step instructions are provided for each stage of the process, this book is designed to complement the online help that is provided with the product.

Note: Before you can follow any of the instructions in this book, you must have OMEGAMON Platform and IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration installed and configured in your enterprise. For instructions, see the installation and configuration books on the publications CDs that accompanied this product.

Related publicationsThis 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 Configuration:

� 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

� 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

� OS/400®:

– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere MQ on OS/400, SC31-6886

� 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:

� Using IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, SC31-6888

� Using IBM Tivoli OMEGAMON XE for WebSphere Integration Brokers, SC31-6890

Preface 11

About This Book

� Using IBM Tivoli OMEGAMON XE for WebSphere InterChange Server, SC31-6891

The following documents also provide useful information:

� Administering OMEGAMON Products: CandleNet® Portal, GC32-9180, describes the support tasks and functions required for the OMEGAMON Platform, including CandleNet Portal user administration.

� 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.

� 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.

� 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.

Accessing publications online

Two publications CDs are shipped with IBM Tivoli OMEGAMON XE for WebSphere MQ:

� IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD

� OMEGAMON Platform and CandleNet Portal Documentation CD

The format of all publications is PDF. Refer to the readme file on the CD for instructions on how to access the documentation.

IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address:

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the IBM Tivoli OMEGAMON XE for WebSphere Business Integration link to access the product library at the Tivoli software information center.

If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper.

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

� In the United States: 800-879-2755

� In Canada: 800-426-4968

http://www.ibm.com/software/tivoli/library/

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

About This Book


In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM Tivoli Education Web site:

http://www.ibm.com/software/tivoli/education

Support informationIf 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:

� Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information.

� Obtaining fixes: You can locate the latest fixes that are already available for your product.

� 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 317.

http://www.ibm.com/software/tivoli/order-lit/

http://www.ibm.com/software/tivoli/education

Preface 13

Documentation Conventions


OverviewThis guide uses several conventions for special terms and actions, and operating system-dependent commands and paths.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Required blanksThe slashed-b (!) character in examples represents a required blank. The following example illustrates the location of two required blanks.

!!!!eBA*ServiceMonitor!!!!0990221161551000

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of z/OS® command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols 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 | NOIn 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.



{ } 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.

Table 1. Symbols in Command Syntax

Symbol Usage

What’s New in Version 3.7.0 15

What’s New in Version 3.7.0

This product has a new nameIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (formerly OMEGAMON XE for WebSphere MQ Configuration) 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 Monitoring (formerly OMEGAMON XE for WebSphere MQ Monitoring) 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.

Configuration product enhancementsThis configuration product includes many user-requested enhancements. They are:

� Configuration database has a database type option

You can use either the product-provided Internal configuration database type (as in the previous release) or you can use a DB2 Universal Database (UDB) type database as your configuration database. Setting up the configuration database is part of setting up support for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration on your hub CMS. Refer to one of these books:

– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX

– Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS

You can find these books on the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product.

For information about the configuration database, see “Backing up the Configuration Database” on page 143.

� Enhanced Scheduled Action options

– You can manually save the data from a scheduled action report to a log file on the client machine, or optionally export the data to a specified file. The saved file may be used as input for third-party reporting utilities.

– A “Backup configuration database” scheduled action is available.

W


For information about scheduled actions, see “Action Scheduling” on page 111.

� Enhanced dialogs

– The enhanced Discrepancy Display dialog lets you select muliple items then perform the Update actual from defined, or Update defined from actual operation. For information about discrepancies, see “Viewing Discrepancies” on page 95.

– The enhanced Validation Display dialog lets you select an item that is in error and correct it without leaving the dialog. For information about validation, see “Validating Objects in the Defined View” on page 86.

� Pop-up menu options additions and some minor changes

– Use the Change Fonts option to adjust the appearance of some of the text in the defined view or prototype view. These changes are in effect until you log off of the session.

– Use the Compare items option to compare the resource definitions of two selected objects of the same type in the defined view tree; any combination of Defined or Actual resources is allowed. For example you can compare the defined resources of queue manager QM1 to either the defined resources or the actual resources of queue manager QM2.

– Use the Display configured systems option to quickly view the associations between configured systems and host names. The Display configured systems option is available when you right-click on the top-level icon in the defined view tree.

– Use the Display resources option to quickly view the resources contained in a resource group. The Display resources option is available when you right-click on a resource group icon in the defined view tree.

– Use the View authorities option to view the WebSphere MQ authorities in effect for objects in the selected configured system in the defined view tree.

– Use the Export all option to perform a full export of the entire configuration database. The data is exported in XML format for use with third-party report generators. An XML data file created using the Export all option cannot be imported back into the configuration database. The Export all option is available when you right-click on the top-level icon in the defined or prototype view tree.

– In a disaster recovery situation only, use the Reset Actual Exists option for the selected configured system in the defined view tree.

The appearance of some pop-up menu options has changed so that they fit more compactly on the menu. For example:

– The former “Update actual from defined” and “Update defined from actual” now appear as “Update > actual from defined” and “Update > defined from actual”.

– The former “Show resolved” menu option has been renamed to “View resolved”.

The functional operation of these menu options has not changed.

For information about menu options, see the IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration section of the CandleNet Portal help.

Introducing Tivoli OMEGAMON XE for WebSphere MQ Configuration 17

Introducing Tivoli OMEGAMON XEfor WebSphere MQ Configuration

IntroductionThis chapter provides an overview of this product’s configuration features and explains how they can help you manage your WebSphere MQ configuration.

This chapter also contains a scenario designed to explain how the elements of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration work together to help you ensure a cohesive network whose interrelationships are correctly defined.

Chapter contentsGetting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18OMEGAMON Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration? . . . . . . . . . . . . . 24Putting All the Pieces Together: A Typical Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

1

Getting Started


Getting Started

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration uses the CandleNet Portal® interface and adds the Configuration navigator view and the WebSphere MQ Configuration Authorities items to the interface. These items are described below.

Here’s how to get started using the Configuration view:

1. Log on to CandleNet Portal and, from the List of available Navigator Views, select Configuration.

The Configuration view is present in this list after initial installation of your IBM Tivoli OMEGAMON XE for WebSphere Business Integration product package.

If Configuration does not appear in your List of available Navigator Views, then your IBM Tivoli OMEGAMON XE product administrator needs to assign the view to your User ID.

2. To add the Configuration view to your list of available Navigator views: open the Administer Users dialog (or ask your IBM Tivoli OMEGAMON XE product administrator to open it for you), select your User ID, then select the Navigator Views tab and add Configuration to your list of Assigned Views.

If you move Configuration to the top of the list of Assigned Views, as shown below, it becomes your default view.

Note: If Configuration is not listed in the Administer Users dialog on the Navigator Views tab shown above, either in the list of Available Views or in the list of Assigned Views, then product support is not properly installed from the CD for IBM Tivoli OMEGAMON XE for WebSphere Business Integration. Refer to the installation


Getting Started

documents on the the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product package.

3. While in the Administer Users dialog, select the Permissions tab and scroll down the list of Authorities. In this list, you will see the WebSphere MQ Configuration Authorities item, as shown in the next illustration.

Note: If the WebSphere MQ Configuration Authorities item is not listed in the Administer Users dialog on the Permissions tab shown above, then product support is not properly installed from the CD for IBM Tivoli OMEGAMON XE for WebSphere Business Integration. Refer to the installation documents on the the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product package.

Your User ID requires the Modify permission (Modify includes View) in order to change your site’s WebSphere MQ configuration or to schedule configuration updates using this configuration product (which may include access from the IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring product by means of enhanced integration using OMEGAMON DE).

4. Click OK to save and exit the Administer Users dialog.

Getting Started


5. Close the interface then log on to CandleNet Portal again to update the List of Available Navigator Views and select (or default to) the Configuration view.

The Configuration view is the usual way to access IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. (It can also be accessed by means of enhanced integration with IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring using OMEGAMON DE.) This guide describes what you can do in the Configuration view.


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 agentsOMEGAMON 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.

Figure 1. OMEGAMON XE Agent–Server–Client Architecture

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).

Candle Management ServerThe Candle Management Server (CMS) gathers data from the OMEGAMON XE agents and acts as a collection and control point for alerts received from the agents. The CMS

Monitoring Agents

CandleNet Portal Server

CandleNet Portal Clients

Candle Management Server

OMEGAMON Platform


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.

CandleNet Portal clientsCandleNet Portal is the Java-based interface to the data monitoring and management resources of OMEGAMON Platform. Depending on how it is installed, CandleNet Portal can be used as either a desktop or browser-based client.

CandleNet Portal has its own server, the CandleNet Portal Server. The CandleNet Portal Server performs common CandleNet Portal functions and serves to lighten the CandleNet Portal client.

Candle Management WorkstationThe Candle Management Workstation (CMW) is used for certain administrative functions that CandleNet Portal does not support. If you want to define and manage work groups and work lists, you must use the CMW.

IBM Tivoli OMEGAMON DEThe IBM Tivoli OMEGAMON DE feature package for CandleNet Portal offers a process-driven view of your enterprise. It enables you to pull together information from disparate sources, including a range of operating systems, servers, databases, mainframes, and network and Web components, in a single workspace and provides a single point of control from which you can manage all the resources your business-critical applications rely on.

IBM Tivoli OMEGAMON DE extends the capabilities of OMEGAMON XE to include:

� Enterprise-specific Navigator views

The Navigator physical view shows the hierarchy of your managed enterprise by operating platform and type of IBM Tivoli OMEGAMON XE agent. The Navigator business view offered by IBM Tivoli OMEGAMON DE shows the hierarchy of any managed objects. You can also define Navigator views for any logical grouping, such as a business process or a departmental hierarchy.

� Views of data from different types of monitoring agents in one workspace

In a single workspace, you can build a table or chart with data from one type of monitoring agent, and another table or chart with data from a different agent. Within that workspace, you can show views from as many different agent types as are included on that branch of the Navigator.

� Linking application workspaces

You can define a link from a workspace associated with one type of monitoring agent to a workspace associated with another type of agent.


OMEGAMON Platform

Policy ManagementThe 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 to be performed by users, or automates manual tasks.

Where to find more informationFor more information about OMEGAMON Platform, see the CandleNet Portal online help and the books on the OMEGAMON Platform and CandleNet Portal Documentation CD.

What Is Tivoli OMEGAMON XE for WebSphere MQ Configuration?



What IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration doesBuilding a network for your WebSphere MQ messaging middleware can be a slow and difficult task. As your network grows and queue managers span dozens of systems running on a variety of operating systems, it becomes even more difficult to determine where and how to configure new queue managers and their resources.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration simplifies the time-consuming and resource-intensive tasks of defining your configuration. You can use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to:

� Manage your WebSphere MQ network, including local or remote nodes, from a single point of control

� See how your WebSphere MQ queue managers and resources are related by viewing a graphical representation of your entire network

� Manipulate WebSphere MQ objects across one or more networks of queue managers from a single workstation

� Base configurations on prototype models so you can implement global updates with the click of a mouse

� Save time and resources by performing many difficult development tasks automatically

� Group related WebSphere MQ resources together in ways that reflect the business-oriented relationships between them and the logical structure of your enterprise

This guide provides information on the features and tools that IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration offers to help you manage your WebSphere MQ configuration.

Centralized configuration informationIn a highly distributed network, WebSphere MQ may run on a wide variety of platforms, which compounds the complexity of configuring and maintaining hundreds or even thousands of nodes. No matter where your resources lie, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides simplification by offering a single repository for all your WebSphere MQ configuration data, called the configuration database.

The configuration database is stored at the hub CMS and includes a default set of objects to help you start using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

A graphical representation of your configurationIt is difficult to get a sense of your configuration structure when your view of it consists only of configuration definitions. To help you understand the structure of your configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides a



representation of your WebSphere MQ configuration called the Defined View. Defined objects in this view represent current or potential WebSphere MQ resources—queue managers, channels, queues, processes, namelists, and so on, all under the management of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

You can use the Discover feature to quickly and easily build defined objects that represent your actual WebSphere MQ configuration.

You can also use the Defined View to safely validate changes to your configuration before applying them to your actual WebSphere MQ configuration.

Common prototype models for creating WebSphere MQ objectsThe prototype feature enables you to create blueprints for queue managers, resource groups, and resources that you can use as templates for defining configurations. Once you create a prototype object, you can drag and drop it from the Prototype View into the Defined View as needed to build or update your configuration.

Any object created from a prototype inherits the characteristics of the prototype unless you specifically override them. If you update a prototype, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration updates all objects based on that prototype automatically. Using prototypes makes maintaining your WebSphere MQ configuration much easier, because instead of having to update many defined objects, you can update just the prototype on which they are based.

You can decrease your maintenance costs even further by using variables in your prototypes. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration includes a Global Variables workspace that enables you to quickly and easily change variable values that are inherited by subordinate objects.

Managing resources from a business perspectiveInstead of locking you into a systems perspective of your WebSphere MQ configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration frees you to organize WebSphere MQ resources into groups according to their business purpose. Configured system groups let you organize queue managers into groups of your own choosing. For example, you can group and manage all resources related to a particular application. This allows you to create a configuration that closely matches the logical structure of your



enterprise. At a lower level, Resource groups make it easy to organize queue manager resources (such as channels, queues, processes, namelists, and so on) by the business purpose they serve.

Keeping your actual and defined configurations in syncOnce you develop and test the Defined View, you will want to implement your changes in your actual WebSphere MQ configuration. Or you may want to change your actual configuration manually and update the Defined View accordingly. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides update features that enable you to keep your actual configuration and defined configuration in sync.

It is a good practice to reconcile differences between the Defined View and your actual WebSphere MQ configuration before attempting any type of update operation. The View discrepancies action lets you resolve specific differences either in favor of the configuration database or in favor of the actual configuration.

When you choose to Update actual from defined, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration first validates your Defined View to prevent errors from being implemented in your actual configuration, then updates your actual configuration to match the configuration database.

Another way to keep your actual configuration and defined configuration in sync is to choose to Update defined from actual, which changes the configuration database to match your actual WebSphere MQ configuration.

Note both the Update actual from defined and Update defined from actual operations may delete objects from the configuration that is being updated (thus it is important to View discrepancies before you perform either Update action to ensure you know what changes will be implemented).

Scheduling actionsYou can either perform the Update actual from defined, Update defined from actual, or View discrepancies actions as you update your configurations, or you can schedule these actions to run at specific intervals. For more information see “Action Scheduling” on page 111.

You have options available for how to perform long-running tasks. Based on how you have the product option set, you can select whether to always run in the foreground, always run in the background, or be prompted each time. Actions that you can perform in the background include:

� Update defined from actual

� Update actual from defined

� View discrepancies

� Delete (defined, actual, or both actual and defined)

� Validate

� Discover new resources



� Backup configuration database

For example, if you have the product option set to prompt each time, when you select Update actual from defined you are prompted as to whether the update should run in the background. If you reply yes, the product creates an internal scheduled action to perform the update.

Monitoring network performance with the monitoring productA sibling product of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring, enables you to easily collect WebSphere MQ data from all your remote and local queue managers and analyze it from a single vantage point.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration and IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can be used independently of one another. However, when used together, one product enhances the other. CandleNet Portal® integrates the monitoring functions provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring with the configuration functions provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, thereby enabling a single WebSphere MQ administrator to address both needs from a single workstation.

In addition, the monitoring and performance information provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can help you configure your WebSphere MQ network for maximum efficiency. For example, IBM Tivoli OMEGAMON XE for WebSphere MQ Monitoring can help you determine if there are any bottlenecks in your configuration and you can then use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to resolve bottlenecks by moving or adding queues or by reconfiguring queues and channels.

Viewing monitoring product statistics from the configuration productWhen you perform a View actual request against a queue manager, a local queue, or a channel, the configuration product queries the appropriate OMEGAMON Monitoring Agent for WebSphere MQ to pick up the most current monitoring statistics.

The statistics collected are presented in the Statistics section of the settings list for the object. The Statistics section is only included in the settings list if you perform the View Actual request (it is not present for a normal settings list open). If the monitoring agent is not available, the message "Statistics unavailable - WebSphere MQ monitoring agent not running" is displayed.

Entering WebSphere MQ commands from the defined viewWhen you select the Submit MQ Command option (for example: in the Defined View select a channel, right-click and, from the pop-up menu, select Action > Submit MQ command..) a dialog appears which allows you to enter a free-form WebSphere MQ operator command. The resulting return code is displayed at the client. For other action command options see “Using the Action menu option for queue managers or channels” on page 71.

Putting All the Pieces Together: A Typical Scenario



This section presents a scenario that may help you understand how the features of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration work together to help you build your WebSphere MQ network. At this point, you won’t need to know exactly how each task is performed—subsequent chapters describe these tasks in detail. Instead, note how the company in the scenario uses the power of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to minimize the effort involved in the rollout and maintenance of a new application to many sites.

The XYZ CompanyThe XYZ Company has only recently begun to use WebSphere MQ for application-to-application integration. The company expects their WebSphere MQ configuration to grow rapidly in size and complexity. As systems administrator, you suggest they purchase IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to help them manage an increasingly challenging environment.

One of their first uses of WebSphere MQ is to integrate two applications:

� An order processing application that currently runs on a central z/OS system at company headquarters.

� An order entry application that will run on AIX® systems located at each of the seven branch offices. The application will be rolled out to the seven offices over the next two weeks.

BackgroundBefore you installed IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you created a queue manager and supporting queues on the central z/OS system for the order processing application. You also created queue managers on each of the remote AIX systems in anticipation of the order entry application rollout.

Each AIX queue manager requires four queues. Because each group of four queues supports the same application, the WebSphere MQ administrator expects to configure each group the same way.

Now that you have installed IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you want to use its features to minimize the cost of:

� Designing and testing your planned configuration of the four queues supporting the order entry application on each AIX system.

� Deploying the planned configuration on the seven remote AIX systems.

� Maintaining the configuration of the queues over the life of the application.

StrategyAfter reviewing the goals and the tools provided by IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration, you work out the following strategy for designing, testing, and deploying the planned configuration.



Because the planned configuration will comprise sets of four queues on each of the seven systems, you decide to create prototypes of the four queues. You also decide to create a resource group prototype to hold the four queue prototypes.

This strategy simplifies the work required to build the initial configuration, because once you are satisfied with the configuration of the queue prototypes, you can use them as needed to quickly create queues for the new application. All you have to do is drag an instance of the resource group prototype to the queue manager on each system in the defined view.

Using prototypes also greatly minimizes the effort required to maintain the queues supporting the order entry application. If changes to the application require additional queues or changes to the existing queues, you can change the prototypes directly instead of manually changing each copy.

After copying the resource group prototype to a queue manager in the defined view, you use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to test the defined configuration. Once you are satisfied with the results, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to update the actual WebSphere MQ configuration with a few clicks of the mouse.



ExecutionTo implement this strategy, you take the following steps:

1. Discover and view your existing WebSphere MQ configuration.You use the Discover feature to upload your existing WebSphere MQ configuration so that you can view a representation of it in the Defined View (this is explained in detail in the next chapter). Now that you can see and manipulate the structure of your existing configuration, you can easily make configuration decisions.

2. Create queue prototypes.

Next you create a prototype of each of the four queues that support the order entry application. These prototypes serve as the models for queue objects you will add later to the defined view. Once the queues are added to the seven AIX systems in the defined view, you can change the queues by simply changing the original four prototypes on which they are based.

When creating the four queue prototypes, you specify a name for the prototype, ProtoOrderEntryQn, and another name for defined objects based on the prototype, OrderEntryQn on System Y, where n is a number from 1–4, and Y is the AIX nodename.



By using similar names for defined objects and for the prototypes on which they are based, you can easily keep track of related objects.

3. Create a resource group prototype.

You create a resource group prototype to contain the four resources supporting the order entry application. Creating a resource group prototype makes it easy to configure each AIX system for the order entry application as it is rolled out.

When creating the prototype resource group, you specify a name for the prototype, ProtoOrderEntryGroup, and another name for defined objects that will be based on the prototype, OrderEntryGroup on System Y. Again, using similar names for defined objects and for the prototypes on which they are based, makes it easier to keep track of related objects.

4. Drag an instance of the queue prototypes into the resource group prototype.

You can drag an instance of the four queue prototypes into the resource group prototype. This creates references to each of the four queue prototypes. These references act as pointers that link the queue prototypes to the resource group prototype. If you make



changes to a queue prototype, the change is automatically reflected in the resource group prototype and in each defined object based on these prototypes.

5. Drag an instance of the resource group prototype to the defined view tree.

Next, you open the Defined and Prototype view and copy the resource group prototype to the defined queue manager for the first system to support its order entry application. Dragging an instance of a prototype to the Defined View does not affect your actual WebSphere MQ configuration.

Copying the resource group prototype to the Defined View creates a defined resource group called OrderEntryGroup on System Y. The defined resource group contains the



four queues referenced in the resource group prototype on which it is based. As defined in their prototypes, the queues are all named OrderEntryQn on System Y.

6. Validate the queue manager definition.

To ensure that there are no errors in the queue manager definition or in any of its new underlying resource definitions, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to validate the queue manager with the new resource group.

If you find any errors in the four new queues, edit the associated prototypes, not the object in the Defined View, then validate the queue manager again.

7. Update the WebSphere MQ configuration.

Now that you are confident that the defined view you have created in support of the order entry application is valid, use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to update the actual WebSphere MQ configuration automatically. Instead of implementing the changes command by command, right-click the queue manager you want to update and, from the pop-up menu, select Update actual from defined.

By default, this configuration product validates the defined configuration automatically before adding the four new queues to the queue manager on the actual AIX system.

Next, repeat the process as needed for each of the remaining six AIX systems as the order entry application is rolled out.

MaintenanceOne year later, an upgrade to the order entry application requires the addition of a fifth queue to each of the seven AIX systems. Because you used prototypes to build the



resource group and original four queues for the application, it is easy and fast to add another queue.

1. You create a fifth prototype in the same manner as you created each of the original four queue prototypes. You use the same naming convention as well: ProtoOrderEntryQ5 for the prototype name and OrderEntryQ5 on System Y for the name of defined objects based on the prototype.

2. You add ProtoOrderEntry5 to the resource group prototype ProtoOrderEntryGroup. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration adds a reference to the fifth queue prototype to the prototype. Now that the resource group prototype has been changed, all the defined resource groups based on ProtoOrderEntryGroup get a fifth defined queue as well.

3. Because this configuration product validates updates to an actual configuration before implementing them, you can run the Update actual from defined operation on the entire configured system group without first validating the change you just made to seven AIX systems.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration looks for validation errors that may have been introduced with the fifth queue and, finding no errors, adds the fifth queue to the actual WebSphere MQ configurations on the seven AIX systems.

Viewing Your Current WebSphere MQ Configuration 35

Viewing Your CurrentWebSphere MQ Configuration

IntroductionThis chapter explains how to use the configuration product to view your existing WebSphere MQ configuration. This enables you to see a graphical representation, the structure, and the contents of your configuration.

Chapter contentsCreating Your Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Entering Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Creating a Configured System Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Discovering Your Existing WebSphere MQ Configuration . . . . . . . . . . . . . . . . . . . . . . 40Reviewing Your Defined View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2

Creating Your Defined View


Creating Your Defined View

About creating a defined view of your configurationThe Defined View enables you to create a graphical representation of your WebSphere MQ configuration and provides features that help you manage your site’s actual WebSphere MQ queue managers, and resources.

You can initially build this representation by one of two methods:

� Using your existing WebSphere MQ configuration as the basis for your representation in the Defined view.

� Creating your representation in the Defined View directly within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. See “What Are Defined Objects?” on page 64.

Process summaryCreating a representation in the Defined View based on your existing WebSphere MQ configuration comprises the following tasks:

1. Entering update mode so you can make changes to the configuration database as described on page 37.

2. Creating a new configured system group, as described on page 38.3. Using the Discover feature to populate the configuration database with defined

objects representing your actual WebSphere MQ configuration, as described on page 40.

4. Reviewing the graphical representation of your WebSphere MQ configuration, as described on page 42.


Entering Update Mode

Entering Update Mode

What you can do in update modeTo change the configuration database, you must first change to update mode. When you are in update mode, you can:

� Change your Defined View, including using the configuration database to update your actual configuration (as described in “Maintaining Your Configuration” on page 93) and using your actual configuration to populate the configuration database (as described in this chapter).

� Change your Prototype View. See “Prototyping Your Configuration” on page 43.

� Use the Global Variables workspace to create, delete, and change the values assigned to your site’s global user variables. See “Introducing Variables” on page 51.

� Backup and restore the configuration database. See “Backing up the Configuration Database” on page 143

Before you can enter update mode

To enter update mode, your user ID must have Modify WebSphere MQ Configuration permission, and the Navigator Configuration view as an Assigned View as described in “Getting Started” on page 18.

For detailed information about user administration, refer to the Administering OMEGAMON Products: CandleNet Portal guide.

Procedure To enter update mode:

1. Ensure you are viewing IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.In CandleNet Portal’s List of available Navigator Views, the Configuration view is selected.

2. In the configuration navigator tree, select Configuration (the root-level item).

3. The Update mode check box displays in the Configuration workspace.

4. Select the Update mode check box.

Creating a Configured System Group



What is a configured system group?A configured system group is a unit of organization within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration that enables you to organize queue managers into groups of your own choosing. A configured system group has no corresponding component in an actual WebSphere MQ configuration; it is simply a collection of queue managers, which in turn contain resource groups. Resource groups contain individual resources (queues, channels, and so on). Configured system groups are the highest unit of organization within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

You may create any number of configured system groups and organize them in any way that is meaningful for your site.

Procedure To create a new configured system group:

1. Ensure you are in update mode.

2. Open the Defined View.

3. The defined view tree displays on the left side of the Defined View workspace.

4. Right-click on Defined View (the root-level item) and, from the pop-up menu, select Create new Configured System Group.

You are prompted to supply a name for the new object.

5. Enter an alphanumeric name for the new configured system group. Click OK.

The new configured system group object is added to the defined view tree.

If the default settings for the object are acceptable, you are finished creating the new configured system group.

If you want to modify or view the default settings for the object, continue with the next step in this procedure.



6. In the defined view tree, select the new configured system group.

7. The settings list for the object displays on the right side of the Defined View.

8. Complete the settings list as necessary.

9. Click Help to display information about each parameter.

10. Click Save to save your changes.

Discovering Your Existing WebSphere MQ Configuration



What the discover process doesThe Discover process populates your Defined View with data from existing queue managers. When you run the Discover process, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration searches your entire WebSphere MQ network for queue managers not already defined in the configuration database and adds them to the selected configured system group. This feature is only available at the configured system group level.

Considerations A few key points about the Discover feature:

� The Discover feature processes only new queue managers on systems running IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (the configuration agent, hereafter) connected to the CMS. If the configuration manager discovers a queue manager that is already defined within the database, that queue manager is ignored.

� All z/OS queue managers must be defined as z/OS subsystems.

� On non-z/OS systems, the configuration agent scans for information relating to each queue manager that has been defined using the WebSphere MQ CRTMQM command.

� Queue managers can be discovered if they have been created using the WebSphere MQ CRTMQM command.

� For the configuration agent to pick up resource information, a queue manager must be active at the time the Discover process takes place. Inactive queue managers appear in the defined view tree as a single node with no resource groups. If this occurs, you can use one of the following options to add resource information:

– Start the queue manager and perform an Update defined from actual. See “Updating the Configuration Database from Your Actual Configuration” on page 97.

– Go to the queue manager settings list, expand the Auto Start section, and select the Auto start check box. Then perform an Update defined from actual, see “Updating the Configuration Database from Your Actual Configuration” on page 97.

� IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration can automatically perform a discovery if you activate the Auto Discover product option (in the Product Options area of the Configuration workspace). By default, automatic discovery is disabled. For more details, see the online help in the Configuration workspace.

� Depending on the size and complexity of your existing WebSphere MQ configuration, the Discover process may take a while, and it is not interruptible once begun. If it is not practical to wait for the entire Discover process to complete, you can activate the



Discover Lite product option (in the Product Options area of the Configuration workspace). By default, Discover Lite is disabled. For more details, see the online help in the Configuration workspace.

� The terms Discover and Discovery describe the default Discover process of this configuration product unless specifically noted in this guide.

Procedure

Warning:

Depending on your WebSphere MQ configuration, this can be a lengthy procedure and it is not interruptible once begun.

To search your site’s WebSphere MQ network for queue managers and add them to the current configured system group:



The defined view tree displays on the left side of the Defined View workspace.

3. Right-click on the configured system group to which you want to add the discovered queue managers and, from the pop-up menu, select Discover.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration searches your site’s entire WebSphere MQ environment for unknown queue managers and adds them and all their associated resources (queues, channels, and so on) to the configured system group you selected. For each queue manager discovered, this product creates a resource group named $Default_Group, and the queue manager’s resources are added to that resource group.

When the Discover process is complete, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration displays a report containing information about the Discovery.

Reviewing Your Defined View


Reviewing Your Defined View

OverviewAfter you use the Discover feature to populate a configured system group, you can see your existing WebSphere MQ configuration in the Defined View. Your configuration is shown graphically in a tree view. In this view, different icons represent each type of object in your configuration–queue managers, queues, channels, processes, namelists, and so on.

The left side of the display shows a hierarchical representation of configured system groups, configured systems (queue managers), resource groups, and resources. Click on the + or - signs to expand or contract the display.

The right side of the display shows the settings list of the currently-selected object.

Resource group $Default_GroupWhen you populate a configured system group in the Defined View using the Discover feature, resources associated with each active queue manager are put into a resource group called $Default_Group. Each active queue manager you discover has its own $Default_Group of resources. After the Discover process completes, you can move resources from this pool into resource groups that you create.

See page 76 for more information about resource groups.

Prototyping Your Configuration 43

Prototyping Your Configuration

IntroductionThis chapter discusses the Prototype View and its relationship to the Defined View. It explains prototyping and explains how to use the provided tools effectively.

Chapter contentsAbout Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Creating Prototypes in the Prototype View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Creating Prototypes from Defined Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Dragging Prototype Objects to the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Introducing Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Using the Global Variables Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Adding, Modifying, or Deleting Global User Variables. . . . . . . . . . . . . . . . . . . . . . . . . 54Adding Global Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Adding Symbolic Variables to Prototypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Determining Prototype Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Disinheriting Prototype Associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

3

About Prototypes


About Prototypes

Why use prototypes?Prototyping allows you to design and plan your WebSphere MQ configuration. Sample prototype objects are provided. You can use these samples to build objects that may eventually become part of your WebSphere MQ configuration. Any object created from a prototype inherits the characteristics of the prototype unless you specifically override them. If you update a prototype, all objects based on that prototype are automatically updated, regardless of their location.

This is ideal if you have a distributed network and you want to place identical objects in different locations while ensuring they always remain in sync. For example, you may need to create several identical queue manager configurations. Once you define the queue manager prototype, you can use it to create as many Defined View objects as you need and put them in several locations. If you decide to change the queue manager configuration in all locations, simply alter the original prototype queue manager.

Creating prototypes: two methodsYou can work entirely within the Prototype View to create a new prototype, or you can use a defined object from the Defined View to create a prototype.

� Before you actually add objects to your WebSphere MQ configuration, you may want to design and create objects from scratch in the Prototype View. The advantage here is that you can design the objects to your exact specifications before you add them to your WebSphere MQ configuration.

� You can also take an object that you uploaded from your WebSphere MQ configuration or created in the Defined View, and copy it to the Prototype View to use as a prototype for future objects. The advantage here is that your current WebSphere MQ objects are already configured to your specifications, so you can easily create other objects based on them.

Introducing the prototype viewThe Prototype View, where you work with prototypes, is divided into the following organizational levels:

� Configured System Prototypes, which represent queue managers and managed clusters.

� Resource Group Prototypes, which allow you to gather resources into logical groups.


About Prototypes

� Resource Prototypes, which represent channels, queues, processes, namelists, storage classes, and so on.

Creating an instance of a prototype object within the defined viewAfter you create and define prototype objects, you can drag an instance of the prototype to the Defined View to create objects that are based on the prototypes. See “Dragging Prototype Objects to the Defined View” on page 49.

Global variables versus symbolic variablesWhen used with prototypes, global variables provide a powerful way to define and maintain a value in a single place and the value can be referred to symbolically in many resources. Global variables can be used with any object.

Symbolic variables are variables that apply only to one prototype and can be inherited by subordinate objects within that prototype. For example, a symbolic variable that you define at the queue manager level is available to all subordinate resource groups and resources.

Creating Prototypes in the Prototype View



OverviewYou create prototypes as models on which to base future objects. If you decide to change the parameters of an object, simply alter the prototype, and all objects that are based on the prototype are updated automatically.

When you drag a prototype to the Defined View, you actually create an instance of the prototype.

Sample prototypesIn the Prototype View, the configuration product provides the following types of sample prototypes to help you design and create all or part of your WebSphere MQ configuration. Sample prototypes include standard, defined resources as specified in AMQSCOMA.TST:

� Configured System prototypes

– Use a configured system prototype sample to create queue manager or managed cluster prototypes. Queue manager prototypes consist of a set of queue manager properties and zero or more references to resource group prototypes. Managed cluster prototypes consist of a set of cluster properties and zero or more local queue objects or references to local queue objects. See the note on page 46.

� Resource Group prototypes

– Use a resource group prototype sample to create resource group prototypes that refer to one or more resource prototypes. When you reference a resource prototype within a resource group, a reference object appears. References are pointers to the original prototype. See the note on page 46.

� Resource prototypes

– Use a resource prototype sample to create individual resource prototypes. Resource prototypes correspond to the WebSphere MQ resource types. For example, a local queue prototype and a sender channel prototype are provided as well as other WebSphere MQ resource types.

Note: When you drag and drop a prototype directly to a higher-level prototype, the product’s Prototype copy semantics setting (in the Configuration view) determines whether the resource is copied directly to the higher-level prototype, or whether a reference object is created which points back to the prototype being dragged. The default setting is to create a copy. However, if the Prototype copy semantics setting is “Create reference” then a prototype reference object is created.



ProcedureTo create a new prototype in the Prototype View:


2. Open the Prototype View.

3. In the prototype view tree, use one of the following options:

� To prototype a new queue manager or managed cluster, right-click on Configured System Prototypes and, from the pop-up menu, select Create then select either Queue Manager or Managed Cluster.

� To prototype a new resource group, right-click on Resource Group Prototypes and, from the pop-up menu, select Create Resource Group.

� To prototype a new resource, right-click on Resource Prototypes and, from the pop-up menu, select Create then select the type of prototype object to create.


4. Enter a name for the new object and click OK.

The new prototype object is added to the prototype view tree.

Note: The following applies to prototype queue managers and resource groups: If the name you assign to this prototype object already exists in the configuration database, the configuration product appends the number 1 to the prototype object. If you create another prototype object with the same name again, the configuration product increments this number by one.

5. In the prototype view tree, select the new prototype.

The settings list for the object displays on the right side of the Prototype View.

6. Complete the settings list as necessary. Click Help to display information about each parameter.

7. If you are creating a new queue manager prototype, add the Default.MQSeries.Resources to the new queue manager as follows:

1. In the Prototype View, expand the Resource Group Prototypes.2. Locate the resource group named

3. Drag the Default.MQSeries.Resources icon to the appropriate queue manager icon in the prototype view tree, then release the mouse button.

An instance of the default resources are added to the new queue manager prototype definition.


Creating Prototypes from Defined Objects


Creating Prototypes from Defined Objects

OverviewYou can create a prototype by dragging a defined object from the Defined View and dropping it in the Prototype View.

ProcedureTo create prototypes from defined objects:


2. Open the Defined and Prototype workspace.

The Defined View and Prototype View are positioned and sized so you can easily drag objects between them.

3. In the defined view tree, select the object you want to use as a prototype.

Note: The defined object you select cannot itself have been based on a prototype.

4. Drag the defined object from the defined view tree to the prototype view tree; then release the mouse button on the appropriate icon.

A prototype is built based on the defined object. The original object remains unchanged in the Defined View and in the configuration database.


Dragging Prototype Objects to the Defined View


OverviewAfter you create a prototype object, you will eventually want to create an instance of an object based on that prototype in the Defined View. When you drag a prototype object to the Defined View, the configuration product adds a new icon to the Defined View, creates a defined object based on the prototype, and adds its definitions to the configuration database.

Any changes you make to the original prototype in the Prototype View automatically updates the instance that is now in the configuration database.

GuidelinesUse these guidelines when dragging objects:

� You must be in update mode to drag objects.

� You can drag instances of queue manager prototypes into defined configured system groups only.

� You can drag instances of resource group prototypes into defined queue managers or defined resource groups.

� You can drag instances of resources into defined resource groups or defined queue managers.



ProcedureTo create an instance of a prototype in the Defined View:


2. Open the Defined and Prototype workspace.

The Defined View and Prototype View are positioned and sized so you can easily drag objects between them.

3. In the prototype view tree, select the prototype whose instance you want to copy to the Defined View.

4. Drag the selected prototype from the prototype view tree to the defined view tree.

Hint: While dragging the selected prototype, if you hover near the top or bottom of the defined view tree, the items will scroll. This may take a moment.

5. Release the mouse button when the prototype is in the appropriate location.

An instance of an object based on the prototype is added to the configuration database. Notice that the prototype icon changes to the corresponding defined icon.

6. If necessary, right-click and, from the pop-up menu, select Refresh to update the Defined View display.

Even though the object is now part of the defined configuration, it is not added to your actual WebSphere MQ configuration until you use the Update actual from defined feature. See “Updating Your Actual Configuration from Defined Objects” on page 100.


Introducing Variables


OverviewWhen used with prototypes, variables ensure consistency throughout your configuration and can help you quickly identify objects that may be based on the same prototype.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides a Global Variables workspace that allows you to create your own global user variables. Global user variables are available for use by any individual object in the configuration.

Symbolic variables are local to a particular defined or prototype object, and all its subordinate objects can inherit the symbolic variables. Symbolic variables are defined in the Symbolic variables field of the object’s settings list (for example, in the Prototype section of a prototype object).

Variables resolve only after you create an instance of the prototype in the Defined View. If necessary, you can override variables after the objects are in the Defined View.

You can view resolved global variables or symbolic variables in the Defined View using the View Resolved menu option. For more information see “Viewinging resolved variables” on page 60.

Product-provided global variablesIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following global variables:

APPLNAME The application type (for example, "MQ") associated with the current object.

CFGSYSNM The name of the "current" configured system (for example: queue manager).

HOSTNAME The host name associated with the "current" configured system.

You cannot add, delete, or modify these global variables. You may see them in some of the sample prototypes and you may use them in your prototypes if you want.

Dynamic variablesIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following dynamic variables. These variables are dynamic in the sense that they are likely to have a different value each time they are referenced.

DATE Current local date at the CMS, in the format yymmdd. This variable can be used in dynamic resource creation where multiple resources are to be created, using the date to form part of a unique resource name.

JDATE Current Julian local date at the CMS, in the format yyddd. This variable can be used in dynamic resource creation where multiple resources are to be created, using the date to form part of a unique resource name.



TIME Current local time at the CMS, in the format hhmmss. This variable can be used in dynamic resource creation where multiple resources are to be created, using the time to form part of a unique resource name.

USERID Current logged on User ID. Note this value is displayed in the System Information Area of the Configuration workspace. This is the user ID you typed on the CandleNet Portal Logon dialog with the casing preserved exactly as typed.

Dynamic variables are designed to be used in Resources in the Prototype View. When you drag a prototype that uses a dynamic variable to the Defined View, the dynamic variable references the value that is current at the time that you drag the prototype. For example, you might create a prototype resource that contains in the Description field: “Created by &MYUSER on &MYDATE at &MYTIME” and that contains in the Symbolic Variables field: MYDATE=&DATE,MYTIME=&TIME,MYUSER=&USERID.

Dynamic variables are not appropriate to use if you are creating Resources in the Defined View without using a prototype. For example if you create a Resource in the Defined View without using a prototype and you use the variable &TIME, the dynamic variable references one value when you save the Resource, but when you perform a View discrepancies, the database version references a new value and will always cause a discrepancy.


Using the Global Variables Workspace

Using the Global Variables Workspace

OverviewUse the Global Variables workspace to view the global user variables currently defined for your IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration environment. Global user variables are variables that your site creates. The values of these variables can be referenced in the settings list of any IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration object.

If you are authorized to do so, you can use the Global Variables workspace to create, modify the values of, or delete your site's global user variables.

Viewing global user variablesThe Global Variables workspace displays your site’s global user variables in a report-like format. The workspace lists the following for each variable:

� Variable The name of the global user variable.

� Value The value that the variable resolves to.

� Description An optional text description of the variable.

Adding, Modifying, or Deleting Global User Variables



GuidelinesUse these guidelines when adding, modifying, or deleting global user variables:

� You must be in update mode to add, modify, or delete variables.

� You can modify a user-defined variable Value or Description, but not its Name. If you mis-name a variable, delete it and define a new one.

Adding a global user variableTo add a global user variable:


2. Open the Global Variables workspace.

The list of global user variables displays.

3. Click Add new variable.

The Add User Variable dialog displays.

4. In the Name field, enter the name of your new variable (from 1 to 48 case-sensitive characters); in the Value field, enter its value (from 1 to 64 case-sensitive characters), in the Description field, enter an optional text description (from 1 to 64 case-sensitive characters).

5. Click Add.

The variable is added to the list of global user variables.



Modifying a global user variableTo modify a global user variable:




3. Double-click in the Value field or the Description field of the variable you want to modify.

A blinking text cursor appears in the field; you can now edit the field.

4. Edit the variable as appropriate.


Deleting a global user variableTo delete a global user variable:




3. Select the variable you want to delete and click Delete variable.

The user variable is deleted from the Global variable editor.

Note: When you delete a variable, be sure to also delete any references to the deleted variable from any settings list.


Adding Global Variables to Prototypes



OverviewThis section provides an example that you can use to add global variables to prototypes.

GuidelinesUse these guidelines when adding global variables to an object’s settings list:

� You must be in update mode to add global variables.

� To use a global user variable, be sure that it is defined in the Global Variables workspace.

� You can use a global variable in any text field of a settings list.

� When you use a global variable in the text field of a settings list, it must be preceded by an ampersand (&). For example, to use the global variable that resolves to the application name, enter:

&APPLNAME

� To string variables together or add additional descriptive text, use a period to indicate the end of a variable name. For example:

&APPLNAME..&HOSTNAME.New_Queue

resolves to

MQ.lwallNew_Queue



Example In the following example, you create a global variable to identify your payroll system on the West Coast. You want to be able to identify that the system is WebSphere MQ in the Los Angeles office.


2. Open the Global Variables workspace and create a new global user variable named LAQ.

3. In the Value field, enter: Los_Angeles.

4. Create a new queue manager prototype.

5. When prompted for the name of the new queue manager (this will be the Prototype name field on the Prototype section), enter:

My_New_Queue_Manager

6. Open the settings list of the new queue manager prototype.

7. Expand the Manager section, and in the Name field enter:

&APPLNAME..&LAQ..Payroll_West

This is a combination of the application name product-provided global variable, the global variable you created, and additional text.

8. Complete the settings sections, click Save to save your changes.

A new queue manager prototype named My_New_Queue_Manager appears in the prototype view tree.

9. When you drag an instance of the prototype to the Defined View, the following queue manager name displays based on the global variables you entered:

MQ.Los_Angeles.Payroll_West

Adding Symbolic Variables to Prototypes



OverviewThis section provides an example that you can use to add symbolic variables to prototypes.

Guidelines Use these guidelines when adding symbolic variables to prototypes:

� You must be in update mode to add symbolic variables to prototypes.

� Before you add symbolic variables to prototypes, you must define them in the Symbolic variables field in the Prototype section of the settings list.

� You can use a symbolic variable in any text field of a settings list.

� When you use a symbolic variable in the text field of a settings list, it must be preceded by an ampersand (&).

� To string variables together or add additional descriptive text, use a period to indicate the end of a variable name.

� You can override symbolic variables for a particular object if necessary after it is in the Defined View. See “Overriding assigned symbolic variables” on page 59.

Example The following example shows how to specify and use symbolic variables in prototype objects.

1. Create a queue manager prototype and name it:Satellite.Queue.Manager.Proto

2. Open the settings list for the queue manager prototype. In this settings list, locate the Symbolic variables field and double-click in its Value field. The Symbolic variables dialog pops up.



3. Use the Symbolic variables dialog to define variable QMGR with a value of Queue.Manager.Name and variable HOST with a value of HostName.

For details about using this dialog, refer to the online help. Click Save to save and exit the dialog.

This step defines symbolic variables QMGR and HOST and assigns initial values to them.

4. Back in the settings list for the queue manager prototype, expand the Manager settings section and:

� in the Name field, enter:

&QMGR

� in the Host system name field, enter:

&HOST

5. Complete the settings list and click Save to save your changes.

The new queue manager prototype named Satelite.Queue.Manager.Proto appears in the prototype view tree.

6. When you drag an instance of the prototype to the Defined View, the following queue manager name is displayed based on the symbolic variables you defined:

HostName:Queue.Manager.Name

Overriding assigned symbolic variablesYou use the Based On settings section to override symbolic variables for specific objects.

To override the assigned symbolic variables:





3. In the defined view tree, select the object whose symbolic variables you want to override.

4. The settings list for the object displays on the right side of the Defined View.

5. Expand the Based On section of the selected object.

In the Symbolic variables field, double-click in the Value field. The Symbolic variables dialog pops up.

Note that the overriding variable name must exactly match the variable name listed in the Symbolic variables from prototype field. Variables are case-sensitive.

For details about using this dialog, refer to the online help. Click Save to save and exit the dialog.

Return to the settings list for the object.


The override affects the selected object only. None of the other defined objects based on the original prototype are affected.

Viewinging resolved variablesTo view resolved global variables or symbolic variables in the Defined View:


2. In the defined view tree, right-click on an object and, from the pop-up menu, select View > Resolved.

The settings list for the object appears with all the symbolic variables resolved.


Determining Prototype Usage

Determining Prototype Usage

OverviewThis section describes how to determine which objects are using a prototype.

ProcedureTo determine which objects are using a prototype:


2. In the prototype view tree, right-click on a prototype and select Show Using.

A Show Using dialog lists the following information about the prototype object:

� name of the configured system using this prototype

� name of the defined object (in the Defined View)

� name of the resource type associated with the defined object

Once you determine the prototype an object is using, you can use the Disinherit from Prototype feature or the Disinherit feature to break the prototype association. See “Disinheriting Prototype Associations” on page 62.

Disinheriting Prototype Associations


Disinheriting Prototype Associations

OverviewThis section describes how to break prototype associations.

Procedures

Option 1

To break the association between a prototype and all objects using it:



3. In the prototype view tree, right-click on the prototype that you want to disassociate from all objects using it and, from the pop-up menu, select Disinherit objects.

Option 2

To break the association between a prototype and a defined object that is using it:


2. Open the Defined View and select the defined object that is using the prototype.

3. Right-click and, from the pop-up menu, select Disinherit.

Creating and Defining Objects 63

Creating and Defining Objects

IntroductionThis chapter describes how to create and define objects in the Defined View.

Chapter contentsWhat Are Defined Objects?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Using the Configuration Search Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Creating New Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Setting Access Authority for WebSphere MQ Objects . . . . . . . . . . . . . . . . . . . . . . . . . 73Connecting Queue Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Creating Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Creating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Copying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Using the Replicate Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

4

What Are Defined Objects?


What Are Defined Objects?

About defined objectsObjects in the Defined View represent WebSphere MQ resources that IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration manages. This includes all types of objects in an actual WebSphere MQ configuration, such as queue managers, queues, channels, processes, namelists, and so on.

Each object in the Defined View has its own settings list that contains information specific to that object. Most of the information you specify in the settings list corresponds to values that you would specify on the command line if you created objects manually using WebSphere MQ commands.

The objects displayed in the Defined View are defined in the configuration database and may be objects that do not yet exist in your actual environment.

Determining data sources in settings listsYou use settings lists to define object values in IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. Because you can use different methods to add objects to your Defined View, there may be times when you need to know the origin of object data. In general, the color of the data displayed in a defined object’s settings list indicates the source of the data, as follows:

Black This data was explicitly defined for the object.

Green This data is a WebSphere MQ or configuration product default.

Blue This data was inherited from a prototype.

Gray This data was acquired from an actual WebSphere MQ resource during an Update Defined from Actual operation.

Note: The “Auto Create” and “Auto Create NonStop” sections of a Queue Manager settings list are exceptions. See the online help for details.

After you add objects to the configuration databaseAfter you add objects to your configuration database, test the definitions to ensure that the objects were defined properly. The validation process checks the configuration database only; it does not query actual queue manager data in your WebSphere MQ environment. See “Validating Your Configuration” on page 85 for instructions.


Using the Configuration Search Facility


OverviewThe configuration search facility allows you to search the configuration database for object name, object type, or property values. When you enter a name, type, or value, you get back a list of all objects in the configuration that match the search criteria.

Note: Performance may be an issue with the search facility. It is possible that the entire Defined View or Prototype View may have to be searched.

You will see partial results in the display area (at the bottom of the dialog), before the search ends. You can stop the search process at any time by clicking Stop.

ProcedureTo find an object in the configuration database:

1. Open either the Defined View or the Prototype View and select any object.

2. Right-click and, from the pop-up menu, select Find.

The Find Objects dialog displays.

3. Use the Name page to specify the name and the object type of the object that you are looking for.

� Enter any valid generic name in the Name field. You can include the wild cards characters '*' and '?', which indicate that a generic search for the name is to be performed.

� Select the type of object. If you want to search through all configuration objects, regardless of their type, select <none>.



� Select where you want the search to begin. The Look in drop-down indicates where in the hierarchy to begin the search. The decendants of the object referenced within this drop-down list are searched. The contents of this drop-down list depend on where you originally select the Find option.

When you select the Find option from the pop-up menu for a specific configuration object, then the Look in drop-down list is initialized with the name of the object, plus the names of each of the object's ancestors. By default, the current object is selected, but you can choose one of the ancestor objects in order to begin the search.

� Indicate whether to include subcomponents in the search. Select the Include subcomponents check box to indicate that the search should include lower levels of the tree (the direct and indirect descendents of the objects searched).

4. You can optionally specify a date and/or userid to use as the search filter. The Last Modified page allows you to specify this search filter by using the date and/or userid last modified:

5. You can optionally specify advanced search options.



The Advanced tab allows you to filter the search results based on a specific configuration property:

� Use the Attribute drop-down list to specify any property that is applicable to the type specified on the Type field on the Name page.

� Use the Relationship drop-down list to select the comparison relationship. The comparison relationships available are dependent on the types of values that can be associated with the property. For example, an attribute that can contain a numeric value may have six comparisons (equal, not equal, greater than, less than, greater than or equal, less than or equal), whereas an attribute that can contain an enumerated value may have only two comparisons available (equal and not equal).

� Value may be an entry field (if the property allows arbitrary numeric or character data) or it may be a drop-down list (if the property can only contain one of a set of enumerated values).

6. Click Find Now to initiate the search. While the search is in progress, the results obtained so far are displayed in a report which appears at the bottom of the dialog. Each row of this report represents a configuration object which matches the search criteria. This report contains:

� The name of the object found

� The resource type of the object

� The date and time that the object was last modified

� The userid who last modified the object

Note: You can stop the search request before it is complete by clicking Stop. The report showing the results so far remains on the dialog.

From the results report, you can highlight the report entry of a particular found object and:



� (In update mode) Click Edit to open the object’s settings list.

� Click Show in Tree to locate the object in the tree display. This option navigates through the defined view tree or prototype view tree, expanding branches if necessary, and causes the object to be selected.


Creating New Queue Managers


OverviewYou can create a new queue manager in your Defined View in any of the following ways:

� Creating an instance of a queue manager from a configured system prototype in the Prototype View. See “Creating Prototypes in the Prototype View” on page 46.

� Copying an existing queue manager from another configured system group within the Defined View. See “Copying Objects” on page 81.

� Use the menu options within the Defined View to define a new queue manager from scratch.

This section describes how to define a new queue manager from scratch.

Queue managers on z/OSIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration cannot create nor start queue managers on z/OS nodes, but it can perform all the other configuration functions it provides for non-z/OS platforms. For example, after you create a queue manager on z/OS manually, you can still use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to discover the existing queues and channels for the queue manager and to add new queues and channels.

ProcedureTo create a new queue manager definition for a queue manager that does not yet exist:


2. Open the Defined and Prototype View.

The defined view tree and prototype view tree are positioned and sized so you can easily drag objects between them.

3. In the defined view tree, right-click on the configured system group to which you want to add the new queue manager and, from the pop-up menu, select Create new Queue Manager.


4. Enter an alphanumeric name for the new queue manager then click OK.

The new queue manager object is added to the defined view tree.

5. In the defined view tree, select the new queue manager.

The settings list for the object displays on the right side of the Defined View.

6. In the Manager section of the settings list, enter a Host system name or select one from the drop-down list.

7. Complete the rest of the settings as necessary for your new queue manager. Click Help to display information about each parameter.



8. One important step when creating a new queue manager definition is to add the IBM-provided default resources. If you do not add default WebSphere MQ resources to new queue managers, when you perform a Validate operation, you will receive a validation error. Add the Default.MQSeries.Resources to the new queue manager as follows:

1. In the Prototype View, expand the Resource Group Prototypes.2. Locate the resource group named

3. Drag the Default.MQSeries.Resources icon to the appropriate queue manager icon in the defined view tree, then release the mouse button.

An instance of the default resources are added to the new queue manager definition.

9. (non-z/OS queue managers only) Another important step when creating a new queue manager definition is to select the Auto create check box (in the Auto Start section of the queue manager settings list) and complete the Auto Create settings. If you do not enable Auto create, when you perform a Validate operation, you will receive error KMC0185E. Also, the configuration product will be unable to successfully create the actual queue manager.

When the Auto create check box is selected and the configuration agent determines that this queue manager does not yet exist in your actual WebSphere MQ environment, the configuration agent automatically creates it when you select the queue manager definition in the defined view and perform the first Update actual from defined operation.


Queue managers on nodes without a configuration agentIBM Tivoli OMEGAMON XE for WebSphere MQ Configuration cannot discover or create queue managers on systems that do not run a configuration agent. However, it is still possible to configure WebSphere MQ environments on which you cannot or choose not to install a configuration agent. See “Setting up Queue Managers for Remote Configuration” on page 156 for details.

Starting non-z/OS queue managers automaticallyCertain actions you can take with IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration require information from the queue manager:




� View actual

You can choose to allow IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to start a non-z/OS queue manager automatically when any of these actions occurs. This feature is not available for z/OS queue managers.



ProcedureTo automatically start a (non-z/OS) queue manager:


2. In the defined view tree, select the queue manager you want IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to start automatically.


3. Expand the Auto Start section and select the Auto start check box.

4. Complete the rest of the settings in this section. You can also use this section to start the WebSphere MQ listener and channel initiator. Click Help to display information about each parameter.


If the Auto start is check box is selected, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration starts this queue manager when you take an action that requires information from the queue manager.

Using the Action menu option for queue managers or channels

Action options for queue managers

You can start, stop, or send commands to a queue manager from the Defined View of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. The Action pop-up menu option is available for all queue managers when you right-click on a queue manager name in the defined view tree. The action options for queue managers are Start, Stop ..., and Submit MQ command .., as show below.

When you select Stop for a queue manager, further Stop suboptions are available: Controlled, Immediate, Wait, and Preemptive. Controlled is the default. These are equivalent to the options available on the WebSphere MQ endmqm command. For details, refer to the WebSphere MQ System Administration Guide.

Action options for channels

You can start, stop, retrieve the status of, or send commands to a WebSphere MQ channel from the Defined View of the configuration product. The Action pop-up menu option is available for all WebSphere MQ channels when you right-click on a channel name in the



defined view tree. The action options for channels are Start, Stop (quiesced), Stop (force), Display status, and Submit MQ command .., as shown below.

When you select an option, the configuration product attempts to start, stop, retrieve the status of, or forward a WebSphere MQ command to the selected channel or group of channels.


Setting Access Authority for WebSphere MQ Objects


OverviewYou can configure security authorizations that control access authority for the following WebSphere MQ objects:

� namelist

� queue

� queue manager

Each object listed above has at least one settings section from which you can specify the security attributes for that object.

ProcedureTo specify security authorizations:


2. Open the Defined View and, in the defined view tree, select the namelist, queue, or queue manager whose security authorizations you want to set.


3. Expand the Authorization section.

The Authorized users field lists users (U) or user groups (G) that are authorized to use this resource. (This example shows that users who belong to user group mqm are authorized to use this resource.) Each 3-item comma-delimited string sequence, displayed in this Value field, ends with a number created by IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (which can be ignored). For settings list details, refer to the online help.



To edit values, double-click in the Value field. The Authorization dialog pops up.

Use this dialog to add, delete, or alter principals or groups; you can also specify various authorities for a specific user or group.

When you select an entry from the list area (on the left), the Authorities check boxes are set according to the defined authority settings associated with the selected user or group. For details about using this dialog, refer to the online help. Click Save changes to save and exit the dialog.

Return to the settings list for the object; click Save to save your changes.

4. Ensure that the Configure WebSphere MQ Authorization check box (in the Auto Start section of the Queue Manager settings list) is selected. This check box must be selected before the configuration product can configure WebSphere MQ security.



Connecting Queue Managers

Connecting Queue Managers

OverviewYou can use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to quickly and easily create bidirectional links between two queue managers. When you drag and drop queue manager objects within the graphical interface, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration automatically creates the necessary channels and transmission queues.

ProcedureTo automatically create bidirectional links between two queue managers:


2. Open the Defined View and expand the defined view tree as necessary.

3. Locate the first queue manager you want to connect.

4. Locate the second queue manager.

5. Click the first queue manager you want to connect.

6. Drag its icon to the queue manager you want to connect to; then release the mouse button.

A resource group is automatically added to each queue manager. The resource group added is based on the value specified in the Autoconnect prototype resource group field (in the Auto Start section of the Queue Manager settings list). Default “autoconnect” prototype resource groups are shipped with IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. For details, see the online help for the Auto Start section of the Queue Manager settings.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration creates the necessary transmission queues and channels to link the two queue managers. They are added to the first resource group for each queue manager. If a queue manager has no resource groups, one is created named $Default_Group.

Creating Resource Groups



What is a resource group?A resource group is a unit of organization within IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. Resource groups make it easy to organize queue manager resources (such as channels, queues, processes, namelists, and so on) by the business purpose they serve. For example, you can put all the resources associated with a particular application into a single resource group. Or you can use resource groups to logically group resources in any way that is meaningful in your environment. For example, you might want to organize the queues discovered on a particular queue manager into resource groups named ProdQueues and TestQueues. Once you organize resources into groups, you can take actions on all of the resources in the group in one step instead of issuing commands on individual resources.

Note: If your site's configuration contains a large number of resources within a resource group, you may experience a degradation in performance. To avoid this situation, decrease the number of resources in a resource group and create more resource groups.

Resource group $Default_GroupWhen you populate a configured system group in the Defined View using the Discover feature, resources associated with each active queue manager are put into a resource group called $Default_Group. Each active queue manager you discover has its own $Default_Group of resources. After the Discover process completes, you can use this pool of definitions to populate resource groups that you create.

Details of how discovered resources are automatically groupedThe Discover process (or alternatively, the Auto Discover product option or the Discover New Resources option for Configured Systems) separates the $Default_Group resources into sub-resource group types. This process reduces potential performance issues because you have smaller resource groups, thereby requiring less client processing time.

In each $Default_Group, the resources are separated into the following subgroups:

� $AuthInfo contains all WebSphere MQ authentication information objects� $Channels contains all channels� $Listeners contains all channel listeners� $Namelists contains all namelists� $Processes contains all processes� $Queues contains all queues� $StorageClasses contains all storage classes

In the case of dynamic resources (permanent dynamic queues), the $DynamicResources resource group will also contain sub-groups for each resource type. However, only the $Queues resource group will exist, as queues are the only type of dynamic resource



supported. Note that permanent dynamic queue definitions are not created in the configuration database unless you have enabled the Configure permanent dynamic queues option (in the Auto Start section of the queue manager settings list).

Controlling how discovered resources are automatically groupedYou can control the number of resources that are automatically put into a resource group and you can indicate that discovered resources be placed in separate groups, based on the high-level prefix of the resource name.

The Dynamically-created resource groups area (in the Product Options area of the Configuration workspace) provides these options for controlling how discovered resources are grouped.

Select the Limit number of resources to check box to indicate that the number of resources to be placed into a resource group during discovery should be limited to a number that you specify. Use the entry field to indicate the maximum resource group size (it has been set to 100 in the example above.) If more resources are discovered than will fit in a resource group, a new resource group is created, with a numeric suffix (starting with 0001) added to the resource group name to make it unique. By default, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration limits the number of resources placed into a resource group to 200 resources.

Select the Separate resources by high-level qualifier check box to indicate that separate resource groups should be created for each high-level qualifier found in the set of discovered resources. The high-level qualifier is defined as the set of characters in the resource name up to but not including the first period. If you select this option, the high-level qualifier of the resource name is added as a suffix to the resource group name that would normally be used. All resources with different resource types and different high-level qualifier are placed into distinct resource groups.

You can combine the two options for limiting resource group size.

For example, let's say that a queue manager has 300 queues defined. 250 of the queue names begin with ‘PROD.’ and the remainder begin with ‘TEST.’. You do not select the Limit number of resources to check box, therefore the resource groups created as a result of discover will contain no more than 200 resources. You select the option that indicates that resources are to be separated by high-level qualifier.

When a discover is done against this queue manager, 3 new resources groups are created within $Default_Group:

$Queues.PROD contains the first 200 queues whose names begin with the characters PROD.

$Queues.PROD.0001 contains the rest of the 50 queues whose names begin with the characters PROD.



$Queues.TEST contains all queues whose names begin with the characters TEST.

Precedure to create a new resource groupTo create a new resource group:




3. Right-click the icon of the queue manager for which you want to create a new resource group and, from the pop-up menu, select Create Resource Group.

Note: You can also create a resource group within a resource group, if you want.


4. Enter an alphanumeric name for the new resource group and click OK.

The new resource group object is added to the defined view tree.

If the default settings for the object are acceptable, you are finished creating the new resource group.

If you want to change or view the default settings for the object, continue with the next step in this procedure.

5. In the defined view tree, select the new resource group.



Click Help to display information about each parameter.



Creating Resources

Creating Resources

OverviewYou can use the Defined View’s menu options to create and define new resources within an existing resource group. Types of resources you can define are:

� Alias queue

� Authentication Information object

� Client connection channel

� Cluster receiver channel

� Cluster sender channel

� Coupling facility (z/OS only

� Listener

� Local queue

� Model queue

� Namelist

� Process

� Receiver channel

� Remote queue

� Requester channel

� Sender channel

� Server channel

� Server connection channel

� Storage class (z/OS only)

New resources created with the method described in this section are not based on a prototype, so you will need to either specify all required parameters or accept the default settings. To base an object on a prototype, see the chapter “Creating Prototypes in the Prototype View” on page 46.

Creating Resources


ProcedureTo create a new resource for a resource group:




3. Right-click the icon of the resource group to which you want to add the new resource and, from the pop-up menu, select Create then select the type of resource you want to create.


4. Enter an alphanumeric name for the new resource and click OK.

The new resource object is added to the defined view tree.

If the default settings for the object are acceptable, you are finished creating the new resource.

If you want to change or view the default settings for the object, continue with the next step in this procedure.

5. In the defined view tree, select the new resource.



Click Help to display information about each parameter.


Changing object parametersOnce you create an object, you may need to change the parameters specified in the settings list. The IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration online help provides information on specific parameters. To access the online help for a particular settings list, click Help at the bottom of the list.


Copying Objects

Copying Objects

OverviewYou can copy objects from one location to another within the same view. You can choose one or more objects at a time to copy to a new location.

The rules described in this section also apply to the Prototype View.

For information about dragging an instance of an object from one view to another, see “Dragging Prototype Objects to the Defined View” on page 49.

GuidelinesUse these guidelines when copying objects within the same view:

� You can copy existing queue managers from one configured system group only to another configured system group, or within the same group.

� You can copy an existing resource group from one queue manager only to another queue manager, or within the same queue manager, or to another resource group within the same queue manager or a different queue manager.

� You can copy existing resources (queues, channels, and so on) from one resource group to another resource group, or to another queue manager.

� If you copy an object that is based on a prototype, the new copy is based on the same prototype.

ProcedureTo copy an object from one location to another within the same view:

1. Ensure that you are in update mode.

2. Open the Defined View or the Prototype View.

3. Select the object you want to copy.

4. Drag the object to the new location.

5. Release the mouse button to drop the object.

The object is copied to the new location.

Copying prototypesWhen you are dragging one prototype object to another (for example, copying a prototype local queue to a prototype resource group), you have a choice of making a copy of the object you are dragging or creating a prototype reference object within the target object, which then refers back to the object you are dragging. The default is to copy the object.

To create a prototype reference object:

Copying Objects



2. In the Configuration view, ensure that Prototype copy semantics is set to: Create reference.

3. Open the Prototype View and expand the prototype view tree as necessary so that you can see both the object you want to drag and the target object.

4. Select the object you want to drag.

5. Drag the object to the object you want to drop it on.

6. Release the mouse button to drop the object.

A prototype reference object will be created within the object that was dropped on. This prototype reference object points back to the original prototype that was dragged.


Using the Replicate Option


OverviewYou can use the Replicate option to create multiple copies of a configuration item (within the same parent object) without having to drag and drop once for each item you want to copy. You can use this option with all configuration objects.

ProcedureTo create multiple copies of a configuration item, within the same view:


2. Open the Defined View or the Prototype View.

3. Right-click the item you want to copy and, from the pop-up menu, select Replicate.

4. When you select the Replicate option, a dialog appears, requesting that you provide:

� The number of copies to make of the object.

� The name of a symbolic variable already associated with the object into which a unique number will be assigned for each new object created.

5. Click OK to replicate. The copies are added to the view.

ExampleFor example: You create a resource called LOCAL.QUEUE.&NUM, and in the Based On section for the resource, associate a value of 0 with the symbolic variable NUM. The resolved name of the resource is therefore LOCAL.QUEUE.0. Then you select the Replicate option and indicate that 50 copies of the object are to be made, and that NUM is the symbolic variable into which unique numbers are to be assigned.

The configuration product creates 50 copies of the resource within the same parent object. For the first copy, NUM is assigned a value of 1, thus creating a resource called LOCAL.QUEUE.1. In the second copy, NUM is assigned a value of 2. In the last copy, NUM is assigned a value of 50. The configuration product assigns numbers starting with 1, unless a numerical value is already associated with the symbolic variable in the original object; in which case, the configuration product starts numbering with the next consecutive number.



Note: The symbolic variable is optional; if omitted, the configuration manager attaches a numerical suffix to each object created in order to create unique names. The number will be padded on the left with enough zeros to make each suffix the same length, thereby ensuring that they will sort in the proper sequence.

Validating Your Configuration 85

Validating Your Configuration

IntroductionThis chapter explains how to ensure that the defined objects you create using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration are valid before you add them to your WebSphere MQ configuration.

Chapter contentsValidating Objects in the Defined View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Controlling the Amount of Validation Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

5

Validating Objects in the Defined View



What validation doesBefore you add defined configuration objects to your actual WebSphere MQ configuration, you can validate the definitions to ensure they are defined properly. For example, WebSphere MQ allows you to create a sender channel that references a transmit queue that does not yet exist in your WebSphere MQ configuration. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration notifies you if the validation test detects this error.

When you choose the validation feature, a group of default validation functions are performed on all objects. You can, however, control the amount of validation testing you want to perform on specific objects.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides two ways to control validation testing:

� Use the object’s Validation settings to enable or disable validation options. The validation options apply to individual objects only and cannot be inherited by subordinate objects.

� Use the queue manager’s Resource Validation settings to enable or disable validation options for a queue manager’s subordinate resources. All subordinate resources inherit the queue manager validation options by default.

Note: Validation processes objects in the configuration database only; it does not process actual queue manager data in your WebSphere MQ environment.



Default validation optionsBy default, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration performs the following validation tests on all objects, unless you change the validation options:

� Queue manager validation

– ensures that no resources with the same name exist within a queue manager

– ensures that IBM-default resources are defined within the queue manager

– ensures that referenced dead-letter queues and default transmit queues are defined correctly

� Queue validation

– ensures that a sender or server channel exists on the same queue manager that references the queue if a local queue is defined as a transmit queue

– ensures that the remote queue manager referenced by the remote queue is defined within the same queue manager as a transmission queue, if the XMITQ field is blank

– ensures that if triggering is enabled for a queue, the process and initiation queue exist within the queue manager

� Channel validation

– ensures that a sender or server channel references a transmit queue

– ensures that the transmit queue is properly defined within the queue manager

– ensures that there is a receiver or requester channel properly defined on the connected queue manger for each sender or server channel on the local queue manager

� Process validation

– ensures that defined processes are referenced by local queues within the queue manager

� Namelist validation (z/OS only)

– ensures that each name referenced within a namelist is defined as a queue within the queue manager



ProcedureTo validate an object in the Defined View:



3. Right-click the object you want to validate and, from the pop-up menu, select Validate.

� If there are no validation errors, a message indicates that the validation request completed successfully.

� If there are validation errors, the Validate dialog lists the object name and type, its location in the defined view tree, and a description of the error found.

Correct the errors, and repeat steps 3 and 4 until no error conditions are detected.

4. When the objects are error free, you can use them to update your WebSphere MQ configuration. See “Updating Your Actual Configuration from Defined Objects” on page 100.


Controlling the Amount of Validation Testing


About validation settingsYou can change the default validation rules for either single objects or for a queue manager’s subordinate objects.

A resource object’s Validation settings section allows you to enable or disable validation options for individual objects. The selected options apply to the individual object only and cannot be inherited by other objects.

A queue manager’s Resource Validation settings section allows you to enable or disable validation options for queue manager subordinate objects. All subordinate objects inherit the queue manager’s validation options unless you specifically change a resource setting.

You can also set validation options for prototype objects. Any object created from the prototype inherits its validation rules.

Setting validation rules for individual objectsYou use the Validation settings section to enable or disable validation options for individual objects.

ProcedureTo set validation rules for individual objects:


2. In the Defined View select a resource object or in the Prototype View select a resource object prototype.

The settings list for the object displays.

3. Expand the Validation section of the settings list.

4. To disable a particular validation setting, either select Disabled from the list of available options or deselect the checkmark.


When you use the validate function for this object, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration performs only the validation options that are activated.



Setting default validation rules for resources within a queue managerThe queue manager Resource Validation settings section allows you to enable or disable validation options for queue manager subordinate objects.

Note: You must also select the Use Queue Manager Default option or the Inherit option in the resource object’s Validation settings section to enable it to inherit the queue manager’s validation options.

ProcedureTo set default validation rules for resources within a queue manager:


2. In the Defined View select a queue manager or in the Prototype View select a prototype queue manager.


3. Expand the Resource Validation section.

All options are checked by default.

4. To disable an option, click the option to remove the checkmark.


If you want to be sure that a resource inherits the default queue manager validation rules, be sure that the Use Queue Manager Default option or the Inherit option is selected in the Validation section of the resource’s settings list.



Disabling validation by prefixYou can also use the Validation settings section of a queue manager (or a prototype queue manager) to specify that validation not be performed on objects whose names begin with a certain prefix. By default, validation ignores all objects that use the prefix SYSTEM., which represents the IBM-provided objects. You can delete the default option and enter a prefix you prefer, or enter several prefixes separated by commas.

ProcedureTo enable validation by prefix:


2. In the Defined View select a queue managerorIn the Prototype View select a prototype queue manager.


3. Expand the Validation section.

4. In the Don’t check resources prefixed with field, type the prefix names you want to exclude from validation.

You can enter more than one prefix, separated by commas.

For details, see the online help for the Validation section of the Queue Manager settings.


Now, when you use the validation feature, objects with the selected prefixes are ignored.



Maintaining Your Configuration 93

Maintaining Your Configuration

IntroductionThis chapter discusses using the configuration product’s features to keep your WebSphere MQ configuration in sync with the configuration database and display.

Chapter contentsMaintaining Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Viewing Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Updating the Configuration Database from Your Actual Configuration . . . . . . . . . . . . 97Backing Up the Configuration of the Actual Environment . . . . . . . . . . . . . . . . . . . . . . 99Updating Your Actual Configuration from Defined Objects . . . . . . . . . . . . . . . . . . . . 100Working with Queue-Sharing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Exporting or Importing XML Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Exporting MQSC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6




OverviewWhen you use the Discover feature, you add a matching set of WebSphere MQ objects to the configuration database and the defined view tree. You now have corresponding objects in two separate places: one set in the defined configuration and one set in your actual WebSphere MQ configuration. When you create new objects or modify existing objects in either location, the changes are not automatically added to the corresponding objects.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following functions to help you keep corresponding objects in sync:

� The View discrepancies operation checks for differences between defined configuration objects and the corresponding objects in your WebSphere MQ configuration since the last update.

� The Update defined from actual operation changes the defined resource to match the actual definition.

� The Update actual from defined operation changes the actual resource to match the defined version.

� The Discover new resources option for Configured Systems searches the queue manager and adds newly-discovered resources to the configuration database and the defined view tree. Any newly-discovered permanent dynamic queues are saved in a resource group called $DynamicResources; all other newly-discovered resources are saved in resource group $Default_Group. Note that permanent dynamic queue definitions are not created in the configuration database unless you have enabled the Configure permanent dynamic queues option (in the Auto Start section of the Queue Manager settings list).


Viewing Discrepancies


About viewing discrepanciesUse the View discrepancies pop-up menu option to evaluate the difference between the defined and actual resource definitions for an object and display any conflicts. If selected for an object containing other objects, the action is applied to the contained objects as well. If there are differences, you can make the appropriate changes before you use one of the Update operations.

The Discrepancy Display dialog appears whenever you use the View discrepancies operation and discrepancies are found. Use this dialog to locate resouce definitions that do not meet system requirements or conventions before updating your actual configuration from your defined configuration. You can resolve discrepancies for individual objects or for an object and its subordinates.

GuidelinesUse these guidelines when viewing discrepancies:

� Be aware that the View discrepancies operation when used at the resource group level cannot be used to add or delete resource definitions for objects at that level. (Because the update defined from actual operation when used at the resource group level will only update resources that already exist in that group.)

� To add or delete resource definitions for objects in your defined configuration or your actual configuration, use the View discrepancies operation at the configured system level.

To view discrepanciesTo view discrepancies between the defined and actual resource definitions for an object:

1. In the defined view tree, right-click the object that you want to compare to its corresponding object in your WebSphere MQ configuration and, from the pop-up menu, select View discrepancies.

2. The configuration product checks the defined object against the corresponding object in your WebSphere MQ configuration.

� If no discrepancies are detected, a pop-up message indicates that no discrepancies have been found.

� If discrepancies are found, the Discrepancy Display dialog lists them.

About resolving discrepanciesThe Discrepancy Display dialog lists the discrepancies found between resource definitions as defined in your configuration database and the corresponding resource definitions in your actual configuration. Discrepancies found is an error condition.



If you are authorized to do so, you can use the Discrepancy Display dialog to resolve these discrepancies. You must be in update mode in order to perform an Update action from this dialog. See also the guidelines for viewing discrepancies, listed above.

When you are in update mode, the dialog displays buttons (and a check box) that list the actions you can take to resolve the discrepancy either in favor of the configuration database or in favor of the actual configuration.

When you are using the dialog, click Help for more details.


Updating the Configuration Database from Your Actual Configuration


OverviewUse the Update defined from actual pop-up menu option to update your defined configuration to match your actual configuration.

This option changes the defined resource to match the actual definition. If any differences exist, the defined resource is changed to match the actual version. When used at the configured system level, if an actual resource exists that has no defined counterpart, a new defined resource is created; if a defined resource exists that has no actual counterpart, the defined resource is deleted.

You can use this operation on a configured system group, queue manager, resource group, or resource.

This operation affects only the objects you select. For example, if you make changes in WebSphere MQ to a queue manager whose corresponding object is already part of the configuration database, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration updates the selected object in the configuration database and in the display. Now the object in the Defined View and its corresponding object in the WebSphere MQ configuration are identical.

GuidelinesUse these guidelines when updating the configuration database:

� It is a good practice to use the View discrepancies operation before you use the Update defined from actual operation to ensure that you know what changes OMEGAMON XE for WebSphere MQ Configuration will implement.

� If you changed any object that is currently in the defined configuration database, the Update defined from actual operation overwrites its current parameters.

� Be aware that the Update defined from actual operation when used at the resource group level will only update resources that already exist in that group. If you want to add new resources found in the actual configuration, use the Discover new resources operation which is available at the configured system level.



ProcedureTo add actual WebSphere MQ objects and changes to the configuration database and display:



3. Right-click the object or objects you want to update and, from the pop-up menu, select Update defined from actual.

You are prompted to confirm the update.

4. Click Yes to confirm the update.

Any new WebSphere MQ objects or changes to corresponding objects are added to the configuration database.

Note: If you add a WebSphere MQ queue manager that has resources attached, you must first create a resource group in the defined configuration to hold the resources. If not, one is created named $Default_Group.

� If the update is successful, the WebSphere MQ objects and changes are added to the configuration database and the Defined View, and an update successful message appears.

� If there are problems, an error message appears.

5. If there are problems, correct them then run the Update defined from actual operation again.


Backing Up the Configuration of the Actual Environment

Backing Up the Configuration of the Actual Environment

OverviewIt is a good practice to make a backup copy of the original configuration of your actual environment before you make any changes to it with the Update actual from defined operation that is described in “Updating Your Actual Configuration from Defined Objects” on page 100.

ProcedureTo back up the actual environment:




3. Right-click on Defined View (the root-level item) and, from the pop-up menu, select Create new Configured System Group.


4. Type in a name (for example, Backup) for the new configured system group. Click OK.

The new backup configured system group is added to the defined view tree.

5. Copy one or more queue managers that you want to backup to the new backup configured system group. (See “Copying Objects” on page 81.)

6. Right-click on the backup configured system group and, from the pop-up menu, select Update defined from actual. (See “Updating the Configuration Database from Your Actual Configuration” on page 97.)

You have successfully backed up the configuration for one or more queue manager objects in your existing configuration by storing the definition(s) to the duplicate(s) you created in the backup configured system group.

If you ever need to restore the original configuration for a queue manager from the backup you created using the procedure above, right-click on the name of the duplicate queue manager in the backup configured system group and, from the pop-up menu, select Update actual from defined.

Updating Your Actual Configuration from Defined Objects



OverviewThe Update actual from defined operation changes the actual WebSphere MQ resource to match the defined version (in the configuration database and the Defined View). If any differences exist, the actual resource is changed to match the defined version. If an actual resource exists that has no defined counterpart, the actual resource is deleted; if a defined resource exists that has no actual counterpart, the actual resource is created.

You can use the Update actual from defined operation to add new objects to your WebSphere MQ configuration or to update corresponding objects in your WebSphere MQ configuration.

The Update actual from defined operation automatically runs validation tests on defined configuration objects; and will not add objects, or changes, that are not defined properly to your WebSphere MQ configuration. Objects that you copy from the configuration database to your actual WebSphere MQ configuration perform as if they were originally created in the WebSphere MQ environment.

Note: If you delete a resource in your Defined View, and you run an Update actual from defined operation against the queue manager, the resource will be deleted from the actual configuration.



ProcedureNote: 1. It is a good practice to make a backup copy of the actual environment before

you make any changes to it with the Update actual from defined procedure described below.

Note: 2. Use the View Discrepancies operation before you use the Update actual from defined operation to ensure you know what changes IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration will implement.

To add configuration database objects and updates to your actual WebSphere MQ configuration.



3. Right-click the object or objects you want to add to your WebSphere MQ environment, or right-click the object whose updates you want to add to its corresponding image in your WebSphere MQ environment and, from the pop-up menu, select Update actual from defined.

You are prompted to confirm the update.

4. Click Yes to confirm the update.

� If the update is successful, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration adds the new information to your WebSphere MQ environment and an update successful message appears.

� If there are problems, an error message appears.

5. If there are problems, corrrect them then run the Update actual from defined operation again.

Working with Queue-Sharing Groups



Before you startBefore you can use this configuration product to work with queue-sharing groups:

� Your queue-sharing group environment must already exist.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration cannot create nor start queue managers on z/OS nodes, but it can perform all the other configuration functions it provides for non-z/OS platforms.

� Your queue-sharing group environment must be defined to this product.

This means you have used this configuration product to Discover the queue managers in your queue-sharing group. The queue managers are visible in the Defined View and your defined configuration matches your actual configuration environment.

For information about queue-sharing groups see the IBM WebSphere MQ for z/OS Concepts and Planning Guide.

What you can doIn an existing queue-sharing group environment on z/OS, you can use this product to define the following resource objects.

� Authentication Information

� Channels (all types)

� Namelist

� Process

� Queues (all types)

� Storage Class

You can also update a queue manager that already belongs to a queue-sharing group, or convert an existing WebSphere MQ for z/OS queue manager to be part of an existing queue-sharing group.

Defining a new resource in a queue sharing group environmentTo add a new resource, the general sequence of steps is:

1. On any one queue manager in your queue-sharing group, define a new resource and specify a Disposition of GROUP. Save the definition.

2. On the resource that you just defined, perform the Validate operation.3. On the resource that you just defined, perform the Update actual from defined

operation.



IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration issues the necessay WebSphere MQ commands to define the resource on every queue manager in your queue-sharing group.

Example procedureYou have three queue managers (QMG1, QMG2, and QMG3) defined in your queue-sharing group and these queue managers are displayed in the Defined View.

To add a new local queue to be used by all queue managers in this queue-sharing group, proceed as follows.


2. In the defined view tree, right-click on QMG1 (any queue-manager in the group would do, we chose QMG1 for this example) and, from the pop-up menu, select: Create local queue.

3. Define your new local queue, name mynewqueue, with a Disposition of GROUP. Fill in all parameters as required. Save the definition.

4. Select the local queue and Validate

5. Select the local queue and and, from the from the pop-up menu, select: Update actual from defined.

The configuration product generates, in the Defined View, the following objects on QMG1 and on QMG2, and on QMG3:

� a local queue object named mynewqueue with a Disposition of COPY

This is the local copy that belongs to each queue manager

� a local queue object named mynewqueue with a Disposition of GROUP

This is the actual definition of the local queue object with a Disposition of Group is maintained in the shared DB2 repository.

If present in the Defined View, the background color of a resource object icon indicates its queue-sharing group information as follows:

Blue The object is a group resource.

Turquoise The object is a copy.

Green (local and model queues only) The local queue or model queue is shared.

Updating a queue manager in a queue sharing group environmentTo update a queue manager in a queue-sharing group environment, the general sequence of steps is:

1. In the defined view tree, select the queue manager, fill in the queue sharing group section of the settings list as required. Save the definition.

2. On the queue manager that you just defined, perform the Validate operation.3. On the queue manager that you just defined, perform the Update actual from defined

operation.

Exporting or Importing XML Data



OverviewYou can export data from and import data to the configuration database using the XML (eXtensible Markup Language) format.

Using this feature allows you to do the following:

� Batch reporting (using a third-party report generator)

� Offline data manipulation

Both options can show where resources are used, which resources are used, and which resources are based on a specific prototype.

Typically, you export XML data by right-clicking on a resource within the defined view tree or prototype view tree and selecting Export > Partial (or Export > Extended) from the pop-up menu. That resource, and all lower level resources beneath it will be exported to a file name that you specify.

Similarly, you can import XML data that was previously exported (using the Partial export or Extended export options only) by right-clicking a resource and selecting Import from the pop-up menu. The XML data is imported below that resource from a file name that you specify.

Any invalid, unknown, or out of sequence data found within an import file causes the import process to be terminated. The point at which the error was found is identified through an error message.

An Export all option is also available. An XML data file created using the Export all option cannot be imported back into the configuration database.

For more detailed information about XML export and XML import, continue reading this section.

For information about XML, see the web site of the World Wide Web Consortium at www.w3.org.

XML data formatThe XML export data is tag-based. XML tags surround each Resource and Attribute.

An example of the data might look like:



XML exportThere are three XML export options: Partial, Extended, and all.

After any one of these XML export options, the original object remains unchanged in the configuration database.

Partial export

Partial export allows you to export a single resource or group of resources, which may be either defined or prototype resources.

Only Application Attributes are included in the export file. Resources that are based on Prototypes will be effectively disinherited within the export file, similarly, Global variables will be resolved in the export file.

The XML partial export option is available from the defined view tree or the prototype view tree. Right-click a resource and, from the pop-up menu, select Export > Partial.

When you select Export > Partial, you are presented with a standard open file dialog, where you enter the name of the file to receive the exported XML data. If the file does not exist it will be created.

The selected resource and all subordinate resources will be included in the export file.

Extended export

Extended export allows you to export a single resource or group of resources, which may be either defined or prototype resources.

<CNFG Ver="370" Appl="MQ" Type="FULL" Level="1" Date="06/30/2004" Time="12:15:04"> <MGSYSGROUP>

<Name>MQ on SYSG</Name><Descr>All Queue Managers on SYSG</Descr><MGSYS>

<QMNAME>MQM1</QMNAME> <Desc>My Queue Manager</Desc>

<RSCGROUP> <Name>$Default_Group</Name> <RESOURCE> <QUEUE>SYSTEM.MQSC.REPLY.QUEUE</QUEUE> <TYPE>LOCAL</TYPE> etc…

</RESOURCE> <RESOURCE> <QUEUE>SYSTEM.DEFAULT.REMOTE.QUEUE</QUEUE> <TYPE>REMOTEQ</TYPE> etc…

</RESOURCE></RSCGROUP>

</MGSYS> </MGSYSGROUP></CONFIG>



Extended export differs from the normal Partial export in that the export file contains all Resource Attributes.

The extended export option is available from the defined view tree or the prototype view tree. Right-click a resource and, from the pop-up menu, select Export > Extended.

When you select Export > Extended, you are presented with a standard open file dialog, where you enter the name of the file to receive the exported XML data. If the file does not exist it will be created.

The selected resource and all subordinate resources will be included in the export file.

Export all

The Export all option exports the entire configuration database, including Global variables, Defined resources, and Prototype resources, in a single XML format file. This file may be used in XML utilities to view the resources and their attributes. However, as the file contains mixed resource types, it cannot be imported back into the configuration database. (In order to back up the entire database, use the Backup Configuration Database button in the Configuration View.)

The Export all option is available from the top level icon in the defined or prototype view tree. Note this option performs the same full export of the entire configuration database no matter which icon is selected.

You are presented with a standard open file dialog, where you enter the name of the file to receive the exported XML data. If the file does not exist it will be created.

General information about exported XML files

XML tag names within the file will generally be the same as the WebSphere MQ command parameter names. Internal attributes are given tag names by which they are known internally.

Various freeware, shareware and commercial XML editors and browsers are available that allow you to view the exported file. You can also use most common internet browsers, such as Microsoft’s Internet Explorer or Netscape Navigator, to view the XML file.

XML importThe Import option you select depends upon the Export option originally selected for the XML file to be imported.

When you select an Import option, you are presented with a standard open file dialog in which to name the file that contains the XML data to be Imported.

A partial export dataset may be imported into the database by right-clicking on a resource which exists at a similar level to that from which it was exported. The resources within the import file will be imported below the selected resource in the defined view tree or prototype view tree.

All resources imported will be treated as new resources, and as such, standard renaming will be applied to any duplicate names, just as it would if you were creating new resources manually.



An XML data file created using the Export all option cannot be imported back into the configuration database.

Security (z/OS only using external security)Security is an issue, and as a minimum the following is required:

� For partial export or partial import operations, you must have Update access to the resource that is selected to Export the data from or Import the data below.

� For export operations, you must have Read authority to the objects being exported.

� For import operations, you must have Update authority to the target object.

Exporting MQSC Commands



OverviewYou can export data from the configuration database in MQSC commands script format.

The MQSC commands script thus produced, and saved in a file, is in a form which can be directly used to create WebSphere MQ objects on your actual queue manager using WebSphere MQ command processors.

For example, you can use the IBM runmqsc control command to execute a command like:

runmqsc QMGR < mqsc.tst

where mqsc.tst is an MQSC commands script exported from IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

For details of the runmqsc control command provided by WebSphere MQ, see the IBM WebSphere MQ System Administration Guide.

On z/OS, use the CSQUTIL batch utility program to create objects on your actual queue manager using the exported MQSC commands script.

On OS/400, use the STRMQMMQSC command to create objects on your actual queue manager using the exported MQSC commands script.

MQSC commands exportMQSC commands export allows you to export a single resource or group of resources, which are defined resources.

The MQSC commands export option is available from the defined view tree. Right-click on a resource, resource group, configured system, or configured system group and, from the pop-up menu, select Export > MQSC Commands. (You can select multiple objects while holding down the Ctrl key, then right-click and from the pop-up menu, select Export > MQSC Commands.)

The selected resource (or resources) and all subordinate resources to the resource, resource group, configured system, or configured system group are included in the export file.

Only application attributes are included. Resources that are based on Prototypes will be effectively disinherited within the export file; similarly, Global variables will be resolved in the output file.

When you select the Export > MQSC Commands option, you are presented with a standard open file dialog, where you enter the name of the file to receive the exported MQSC commands. The suggested file extention for an MQSC commands script is .tst. If the file does not exist, it will be created.

After the export operation, the original object remains unchanged in the configuration database.



Details of operation and caveatsThe Export > MQSC commands option generates a commands script of DEFINE commands for creating WebSphere MQ objects which are under the scope of export.

To make scripts readily portable, the significant length of generated MQSC commands is restricted to 72 characters. If a command exceeds 72 columns, it is continued on the next line.

� If the defined queue manager's platform type is unknown, then all attributes which belong to the resource will be exported. For example, for a resource of type local queue, the attribute QSGDISP will be exported. If this script is used as an input to a queue manager running on UNIX, it will cause a syntax error. In this case, you would need to edit the generated script to make sure the syntax errors do not occur on the target platform.

� Syntax errors may also result while running runmqsc with the generated script, if the MQSC commands script was generated for a queue manager running on a platform type (for example, z/OS) different from the platform type of the target queue manager (for example, UNIX). Again, this is due to some attributes or resources being valid only on certain platforms. Syntax errors may also result if the source and target of the commands script are running different versions of WebSphere MQ.

� When you run the runmqsc utility with the generated commands script, duplicate default resources will cause duplicate resource errors which is expected.

� Queue Manager definitions are not exported. The command to create a queue manager is outside the scope of the runmqsc control command. Only the resources contained within the Configured System are exported.



Action Scheduling 111

Action Scheduling

IntroductionThis chapter discusses the action scheduling feature. This feature enables you to

� compare your defined configuration to your actual WebSphere MQ configuration at specified intervals.

� backup the configuration database at specified intervals.

� schedule an action against one or more objects in the configuration database.

� view scheduled actions and status information in scheduled action reports

� save the contents of the scheduled action report to a log file after the action has run, or optionally export the data to a specified file after the action has run. (The saved file may be used as input for third-party reporting utilities.)

� view scheduled action failures as CandleNet Portal alerts.

� optionally, run a scheduled action on demand using an activity program within a policy.

Chapter contentsAbout Action Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Scheduling an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Scheduled Action Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Scheduled Action Details Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Scheduled Action Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Running a Schedule on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

7

About Action Scheduling


About Action Scheduling

OverviewWhen you make changes to your defined or actual WebSphere MQ environments, you want to update or compare these configurations to keep them in sync. However, performing these actions as configuration changes are made, or during regular business hours may mean slower response time and a delay in your configuration activities. Additionally, you may be working with configurations in different time zones and want to schedule actions based on the time of day in a particular time zone. Using the action scheduling feature, you can schedule an action to run weekly, daily, hourly, or every n hours in specified time zones. You can also schedule an action to run on demand using an activity program in a policy.

You can schedule one of the following actions for one or more objects:




� Delete (defined, actual, or both actual and defined)

� Validate

� Discover new resources

� Backup configuration database

You can also schedule an action to run based on the time where the CandleNet Portal client is located or where the configured system is located.

Scheduled actions reportsThe action scheduling feature provides reports which allow you to view the nature and status of scheduled actions. IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration provides the following reports:

� Scheduled Action Summary

� Scheduled Action Details

� Scheduled Action Status


Scheduling an Action


OverviewTo schedule actions for a target object, use the Scheduled Action settings list. You can create a scheduled action for one object, or for a group of objects.

GuidelinesUse these guidelines when scheduling an action:

� You must be in update mode to schedule an action.

� You must have authority to update the target object.

� The object cannot be locked by someone else who is performing an action on the object in update mode.

� The object cannot be part of another scheduled action.

Scheduling an actionTo schedule an action:


2. In the Defined View, right-click on the object for which you want to schedule an action and, from the pop-up menu, select Schedules > Create.

3. Enter the name of your new scheduled action, click OK.

The Scheduled Action settings list appears. Here you can specify and schedule the action.

Note: The following applies to scheduled actions that you create under the same parent object:If the name you assign to this scheduled action already exists in the configuration database, the number 1 is appended to the scheduled action name. If you create another scheduled action with the same name again, this number is incremented by one.

4. Use the Name section to specify:

� the name and description of the schedule

� whether the scheduled action should continue running after a failure on one of the target objects when more than one target object was originally selected

� whether the schedule is enabled or disabled (To run the scheduled action, the Enabled check box must be selected.)

� whether to preserve the integrity of target objects and their descendants or ancestors (This prevents another user from making any updates to target objects or their descendants or ancestors when the scheduled action is Enabled.)

� the type of action to perform



5. Use the Time section to specify:

� when the scheduled action should run

� whether the times specified are relative to the CandleNet Portal client or the configured system containing the target object or objects

� how often the scheduled action should repeat

� when the schedule should be purged from the configuration database

� whether the defined action should be performed on a specified schedule or executed by a policy

6. Use the Detail section to view the target object or objects as part of its configured system(s) and configured system group.

7. Use the Save section to specify:

� whether to make the scheduled action report data eligible for saving (To Save the scheduled action report output, the Save output check box must be selected. This is not an automatic process, manual steps are required later, from the Scheduled Action Summary Report, if you decide to save the output to a file after the scheduled action runs.)

� whether this is a one-time-only scheduled action that should be deleted after the report data is saved

� the format of the saved report data

� the level of detail of the saved report data

� whether this is a one-time-only save request

� the file name and location of the saved report data


See the online help for details about each field.

Execution of scheduled actions in multiple time zonesWhen the execution time of a scheduled action targeting multiple configured systems is specified as relative to Conf. System, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration attempts to perform the action according to the local time of each target configured system. Generally this means that the action is started for the eastern-most target first, then proceeds westward.

For example, suppose you have queue managers in London (GMT), New York (EST), and San Francisco (PST), and a CMS located in Salt Lake City (MST). You define a single scheduled action for all three queue managers. You specify that the action must run at 12:00 midnight and cannot run after 2:00 A.M. and select Conf. System as the time zone.

At approximately 5:00 P.M. in Salt Lake City (midnight in London), the scheduled action starts running. It starts performing the requested action on the London queue manager. When the action is complete, the scheduled action waits until 10:00 P.M. Mountain time (midnight in New York), then starts performing the action on the New York queue



manager. While the scheduled action is waiting between targets, its status is RUNNING. At 1:00 A.M. Salt Lake City time, the requested action is performed on the queue manager in San Francisco. Only when the requested action is performed against all the selected targets is the scheduled action considered COMPLETE.

If two or more target configured systems are located in the same time zone, the scheduled action is performed on these systems at the same time.

Scheduled Action Summary Report



OverviewThe Scheduled Action Summary report shows one row for each scheduled action you have created. It provides general information about each schedule, such as its status, its time zone, and the type of action scheduled.

From the Scheduled Action Summary report, you can

� view a Scheduled Action Details report showing all the targeted objects of a particular schedule

� (in update mode) modify an existing scheduled action

� (in update mode) delete a scheduled action

� (in update mode) save the output of a scheduled action report to a file after the action runs

Accessing the Scheduled Action Summary report To access the Scheduled Action Summary report:

In the Defined View, right-click on the Configured System Group associated with the scheduled action and, from the pop-up menu, select Schedules > View.

Modifying a scheduled actionIf you have the proper authorization, you can modify a scheduled action from the Scheduled Action Summary report.

To modify an existing scheduled action:


2. Access the Scheduled Action Summary report.

3. Select the action you want to modify, click Edit.

The Scheduled Action settings list appears.

Click Help at the bottom of the Scheduled Action settings list for detailed descriptions of each field.

4. Modify the scheduled action. Click Save to save your changes.

5. Back on the Scheduled Action Summary report, click Refresh to update the report.



Deleting a scheduled actionNote: Use caution when deleting scheduled actions, as you cannot undo a deletion.

To delete a scheduled action:



3. Select the action you want to delete, click Delete.

About saving scheduled action report outputYou can save the output data associated with a scheduled action to a file, but this is not an automatic process; manual steps are required, from the Scheduled Action Summary Report, if you decide to save the report data to a file after the scheduled action runs. The saved file may be used as input for third-party reporting utilities.

When you create or modify a scheduled action, if you intend to save the scheduled action report output data to a file, fill in the Save section. In that section, ensure that you select the Save output check box to make the data eligible for saving.

When viewing the Scheduled Action Summary Report, data that is eligible for saving indicates “Yes” in the Save column.

Saving scheduled action report outputTo save the output of a scheduled action report to a file:



3. Select an action that has already run and whose data you want to save to a file. Ensure that the selected action indicates “Yes” or “Yes/Once” or Yes/Delete” in the Save column of the Scheduled Action Summary report.

4. Click Save Output to save the output.

The output is saved to the file specified in the Save section of the Scheduled Action settings list. The default save file location is the logs directory. This directory is relative to the current working “CNP” directory (for example c:\Candle\CNP). The default filename is the name of the scheduled action with a suffix of .TXT. If the save file for a particular scheduled action already exists, subsequent output is appended to the end of the file. Thus several scheduled actions can use the same file name.

Viewing the Scheduled Action Details reportTo view the Scheduled Action Details report:



3. Select a scheduled action that has already run and that you want to know more about, click Details. The Scheduled Action Details report appears.

Scheduled Action Details Report


Scheduled Action Details Report

OverviewThe Scheduled Action Details report contains a row for each object targeted for action by a selected schedule. The detailed information includes:

� the name of the object targeted for a scheduled action

� the actual start and end time of the scheduled action

� the status of the action

� the configured system the target object belongs to

� the ancestors of the object in the tree hierarchy

Viewing the Scheduled Action Details reportTo view the Scheduled Action Details report:

1. Ensure you are in update mode


3. Select a scheduled action that has already run and that you want to know more about, click Details.

The Scheduled Action Details report appears.


Scheduled Action Status Report

Scheduled Action Status Report

OverviewThe Scheduled Action Status report shows the status of failed actions after the actions have completed. It contains detailed information about the failed actions, such as:

� the name of the configured system in which the error was detected.

� the name and type of the object for which the error was detected.

� the type of error encountered.

� for a discrepancy, the type of discrepancy.

� if the error was a discrepancy, the defined configuration value and the actual configuration value of the property.

Viewing the Scheduled Action Status reportTo view the Scheduled Action Status report:

1. Ensure you are in update mode


3. Select a scheduled action that has already run, click Details.

The Scheduled Action Details report appears.

4. Select the scheduled action that you want to know more about, click Status.

The Scheduled Action Status report appears.

Viewing alerts for scheduled actionsIBM provides a situation, Configuration_Background_Error, that automatically alerts you if an error has occurred during a scheduled action. To view the alert, switch back to the Navigator physical view.

Running a Schedule on Demand


Running a Schedule on Demand

About running a schedule on demandIBM Tivoli OMEGAMON DE users with the Policy Management solution offering enabled can build OMEGAMON policies to implement more complex workflow strategies than are possible with situations alone.

Polices and the Workflow editor are described in Administering OMEGAMON Products: CandleNet Portal and the CandleNet Portal online help.

With the IBM Tivoli OMEGAMON DE Policy Management solution offering enabled, you can execute a scheduled action to run on demand by creating a policy that uses the product-provided Run_OnDemand_Config_Action activity program. When the situations within a policy become true, CandleNet Portal executes the scheduled action.

Accessing the Workflow EditorTo access the Workflow Editor, select Workflow Editor from the CandleNet Portal tool bar.

Note: This feature displays only if the IBM Tivoli OMEGAMON® DE Policy Management solution offering is enabled.

For more information about creating Policies and for instructions on assigning authority to users, see Administering OMEGAMON Products: CandleNet Portal and the CandleNet Portal online help.

Creating and Defining Clusters 121

Creating and Defining Clusters

IntroductionThis chapter describes the Cluster Exploitation Feature of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. This feature provides you with a simpler, more powerful means of creating and managing WebSphere MQ clusters than is available with native WebSphere MQ commands.

Chapter contentsAbout the Cluster Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Clustering Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Product-Managed Configuration Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Creating a New Managed Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

8

About the Cluster Feature


About the Cluster Feature

OverviewWebSphere MQ Clustering is a powerful facility that provides ease of administration for WebSphere MQ customers, as well as a means of dynamic workload balancing.

The Cluster feature of IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration allows clusters to be defined as explicit objects within the Defined View. Clusters can be managed as follows:

� as other types of existing configuration objects

� defined

� deleted

� dragged-and-dropped

� modified

You can define cluster prototype objects that can be used to build new defined clusters. Objects which are logically associated with the cluster, such as queue managers and cluster queues, are shown in the defined view tree as subordinate objects.


Clustering Terminology


The following terms are associated with the Cluster feature:

Term Definition

Cluster A cluster is a network of queue managers that are logically associated in some way. The queue managers in a cluster may well be physically remote.

Repository A repository is a collection of information about the queue managers that are members of a cluster. A full repository is a complete set of information about the cluster.

Cluster queue manager A cluster queue manager is a queue manager that is a member of a cluster. A queue manager may be a member of more than one cluster. Each cluster queue manager must have a name that is unique throughout all the clusters of which it is a member.

A cluster queue manager may host queues, which it advertises to the other queue managers in the cluster.

Full repository queue manager A full repository queue manager contains all the information about the cluster. Normally, not every queue manager in a cluster contains a full repository.

You must specifically designate full repository queue managers. Other queue managers contain only a subset of the information about a cluster.

IBM recommends that you designate two queue managers to act as full repository queue managers for each cluster.

Cluster queue A cluster queue is a queue that is hosted by a cluster queue manager. The cluster queue manager makes a local queue definition for the queue and this has the effect of advertising the queue to the other queue managers in the cluster. The other queue managers in the cluster can put messages to a cluster queue without needing a corresponding remote-queue definition.

Cluster-receiver channel A cluster-receiver channel definition defines a channel on which a cluster queue manager can receive messages from other queue managers in the cluster.

Cluster-sender channel A cluster-sender channel definition defines a channel on which a cluster queue manager can send messages to one of the full repository queue managers.

Configuration placeholder object

An object within the defined view tree which acts as a placeholder for another object in the configuration.

Placeholder objects are required to preserve the hierarchical structure of the configuration data, while at the same time representing the fact that clusters can contain multiple queue managers, but a queue manager can be a member of multiple clusters.



Virtual configuration object A defined object represented in the configuration product that does not have a one-to-one correspondence to an actual object, but can provide information on how other defined objects are to be created and configured.

Product-managed configuration object

A defined object which is dynamically created and managed by the configuration product. Product-managed configuration objects appear in the defined view tree, and you can view the properties of the object; however, certain properties of the object cannot be modified directly. A product-managed configuration object is usually related to a virtual configuration object; you can indirectly control a product-managed configuration object by manipulating the related virtual configuration object.

Product-managed cluster

A product managed cluster is a virtual configuration object that represents a WebSphere MQ cluster which you want the configuration product to completely manage. It is represented by an object in the configuration hierarchy at the Configured System level.

The descendant objects of a product-managed cluster are either cluster queue manager configuration objects, cluster queue configuration objects, or resource groups containing cluster queue configuration objects. You can define prototypes for product-managed clusters.

Cluster queue manager configuration object

A cluster queue manager configuration object is a configuration placeholder object that represents a queue manager’s participation in a cluster. It serves as a placeholder for a defined queue manager located elsewhere in the configuration tree.

A cluster queue manager configuration object is always subordinate to a product-managed cluster; it is created by dragging and dropping a defined queue manager onto the product-managed cluster.

Cluster queue configuration object

A cluster queue configuration object is a virtual configuration object that represents one or more cluster queues within a cluster, all of which have the same queue name. A cluster queue configuration object provides the specifications for the definitions of each of the cluster queues. The settings list for a cluster queue configuration object indicates on which queue managers the cluster queue is to be defined.

A cluster queue configuration object is always subordinate to a product-managed cluster. It may be subordinate to a resource group within a product-managed cluster. A cluster queue configuration object can be based on a local queue prototype object; if so, any product-managed local queues created from the cluster queue object will also be based upon the local queue prototype object.

Term Definition


Product-Managed Configuration Objects

Product-Managed Configuration Objects

Configuration placeholder objectA configuration placeholder object serves as a placeholder for another object in the configuration. The placeholder object contains a reference to the other object, referred to as the base object. The placeholder object has properties that are accessible through the placeholder object’s settings list.

There are three pop-up menu options for placeholder objects:

� Open settings for base object: This option opens up the settings list for the placeholder’s base object.

� Select base object: This option navigates to, and selects, the placeholder object’s base object.

� Regenerate cluster managed objects: This option causes cluster objects defined on one cluster queue manager to be generated (defined) on all other queue managers within the cluster. This option is only used when things are altered within the managed cluster.

Virtual configuration objects Virtual configuration objects direct how other application-specific objects are to be defined. They do not directly correspond to an actual application-specific object.

Creating a New Managed Cluster



How the cluster feature works - a typical scenarioAll actions of the Cluster Feature are accessible from the Defined and Prototype Views. To best show how the feature works, it may help to look at an example scenario:

XYZ Company, an existing user of the configuration product has recently migrated to a version of WebSphere MQ that supports clustering. XYZ wants to define a cluster consisting of three queue managers, QM1, QM2, and QM3. We’ll assume that these three queue managers are already defined within the configuration product.

ProcedureTo create a new managed cluster:



3. In the defined view tree, right-click on the configured system group (CSG) that is to contain the cluster and, from the pop-up menu, select Create Managed Cluster.


4. Enter the name new_cluster and click OK.

The managed cluster new_cluster appears in the defined view tree within the original configured system group. At this point, the cluster has no subordinate objects.

5. Drag the icon for queue manager QM1 and drop it on the managed cluster. A pop-up confirmation appears asking whether to include the new item in the cluster, click YES if the names are correct.

This creates a cluster queue manager configuration object QM1 under new_cluster.

Note that cluster queue manager configuration object QM1 has the same name as queue manager object QM1 (but a different icon) and contains an internal reference back to queue manager QM1. (The original object, queue manager QM1, is the base object.)

6. Select the cluster queue manager configuration object (under new_cluster).




7. Within the settings list for the cluster queue manager configuration object, select the Acts as cluster repository check box (in the Queue manager name section of the Custer Queue Manager settings list) to indicate that queue manager QM1 (the base object) will act as a full repository for the cluster. Click Save to save your changes.

8. Next, drag the icons for queue manager QM2 and QM3 to cluster new_cluster. This creates cluster queue manager configuration objects QM2 and QM3 under new_cluster. Again, each time you drag a queue manager object and drop it on the managed cluster a pop-up confirmation appears asking whether to include the new item in the cluster, click YES if the names are correct.

9. Select cluster queue manager configuration object QM2 and:

� in the Queue Manager name section, ensure that the Acts as cluster repository check box is not selected. This ensures that the queue manager QM2 (the base object) will not act as a full repositiory for new_cluster.

� in the Channels section, for the Queue managers to predefine cluster sender channels on parameter, select QM1. This instructs the configuration product to define a cluster sender channel from queue manager QM2 (the base object) back to the full repository on QM1.



Click Save to save your changes.

10. Configure cluster queue manager configuration object QM3 in the same way. Click Save to save your changes.

11. Right-click the managed cluster object (new_cluster) and, from the pop-up menu, select Create cluster queue.


12. Enter the name new_cluster_queue and click OK.

This creates a cluster queue configuration object under new_cluster.

13. Select the cluster queue configuration object new_cluster_queue.




14. Within the settings list for new_cluster_queue, in the Cluster queue location section, select QM1 and QM2 to indicate that the new cluster queues are to be defined on queue managers QM1 and QM2. Click Save to save your changes.

15. Run the Validate option at the cluster level to verify that the cluster definitions are OK. Running the Validate option ensures that:

� there is at least one full repository cluster queue manager.

� the definition of each cluster queue manager specifies that a cluster sender channel should be defined back to each full respository for the cluster.

� the definition of each cluster queue configuration object indicates the queue is to be defined on at least one queue manager in the cluster.

� the definition of each cluster queue configuration object does not conflict with any other identically-named cluster queue objects which may reside on one or more of the same queue managers.

16. In the defined view tree, right-click queue manager QM1 (the base object) and, from the pop-up menu, select Refresh. The configuration product recognizes that a cluster which the queue manager is a member of has been modified, and applies the cluster definition to the defined queue manager:

� The definition for queue manager QM1 is modified: the Clusters section is modified to indicate that the queue manager will be acting as a full respository for new_cluster.



� A new resource group is created under the queue manager. The resource group will contain each new resource created by the product. The name of the resource group is taken from the settings list for new_cluster.

� A new cluster receiver channel is defined within the new resource group. The specifications for the cluster receiver channel are again taken from new_cluster’s settings list. The new cluster receiver channel is associated with new_cluster.

17. In the defined view tree, right-click queue managers QM2 and QM3 (the base objects) and, from the pop-up menu, select Refresh for each of them. Similar changes are made to their queue manager definitions:

� Within the new resource groups on queue managers QM2 and QM3, a new cluster sender channel is created, with the same name and specifications as the cluster receiver on QM1.

� Also created within the new resource groups on QM2 and QM3 are the local queue definitions for new_cluster_queue. The details for the local queue definitions are taken from the settings list for the new_cluster_queue cluster queue configuration object. The Clusters section for each local queue definition indicates that the queue is associated with new_cluster.

18. As a final step, perform an Update Actual from Defined against each of the queue managers.

This action causes the appropriate cluster definitions to be made at the actual queue managers.

Note: If a queue manager becomes part of more than one cluster, it may be necessary for the configuration manager to create namelist resources on the queue manager. This is because WebSphere MQ does not allow you to directly associate an object with multiple clusters; instead, the object must be associated with a namelist using the CLUSNL property, and the cluster names must be defined within the namelist.

Audit logWhen product-managed configuration objects are created, modified, or deleted as a result of a change to a cluster definition request, entries are added to the configuration audit log to show the change. The entries in the audit log are flagged to indicate that the changes were made as a result of a change to a virtual configuration object.

Prototype objectsPrototype objects can be created for managed clusters. You create managed cluster prototypes within the Configured System Prototypes root. Cluster prototypes can contain the following as subordinate objects:

� local queue prototypes directly

� references to local queue prototypes

� resource group prototypes

� references to resource group prototypes



Cluster prototypesYou can use a cluster prototype to build a defined cluster by dragging it to the targeted Configured System Group in the defined view tree; when you take this action, the resulting defined cluster is based-on the cluster prototype. Clusters based on cluster prototypes will have subordinate cluster queues for each local queue prototype or prototype references defined within the cluster prototype.

Cluster queues based on local queue prototypesYou can build a cluster queue configuration object from a local queue prototype object by dragging the prototype and dropping it either directly on the target managed cluster, or on a resource group within the managed cluster. Any local queues which are subsequently created from this cluster queue object will also be based on the local queue prototype.

Special Considerations



Control over product-managed configuration objectsThis section describes how you can control the properties and characteristics of the various product-managed configuration objects created and managed by the Cluster feature.

Queue manager objects

For queue managers defined as full repositories for one or more managed clusters, the configuration product controls the settings of the repository Cluster Name and Namelist properties (in the Clusters section of the Queue Manager settings list).

If the queue manager is a full repository for a single cluster, the Cluster name property contains the name of the cluster.

If the queue manager is a full repository for more than one cluster, then the Cluster name property is blank, and the Namelist property contains the name of the namelist containing the cluster names.

Resource group objects

When a queue manager participates in a managed cluster, then the configuration product creates one or more resource groups within the queue manager, to contain any product-managed configuration resources that are generated.

For each cluster that the queue manager is a member of, a resource group is created to contain those resources specifically related to the cluster. The name of the resource group is specified in the Resource Group Name property (in the Cluster Resources section of the Managed Cluster settings list). The default value for this property is ‘RG.4.&CLUSTER<1:35>..OBJECTS’; The specification of &CLUSTER<1:35> within this property indicates that the first 35 characters of the symbolic variable ‘CLUSTER’ are to be substituted into the property text. Because the configuration product assigns the name of the cluster to the CLUSTER symbolic variable within the resource group definition, by default, the name of the resource group contains the first 35 characters of the cluster name.

For example: if queue manager QM1 is a member of managed cluster CLUSTERA, then the resource group within QM1 which contains all resources specifically related to this cluster is called RG.4.CLUSTERA.OBJECTS.

In addition, the configuration product may also create a resource group that contains product-managed configuration resources not related to a specific managed cluster. Typically, this resource group contains the namelist definitions that result from a queue manager being made a part of multiple managed clusters. The name of this non-cluster specific resource group is provided in the Resource group name property (in the Clusters section of the Queue Manager settings list); the default for this property is RG.FOR.CLUSTER.OBJECTS.



Cluster receiver channel objects

If a queue manager is participating in one or more managed clusters, the configuration product creates a definition for at least one cluster receiver channel for the queue manager. The name for the cluster receiver channel comes from either of the following:

� the Cluster Receiver Name in the Cluster Resources section of the Managed Cluster settings list

� the Cluster Receiver Name in the Clusters section of the Queue Manager settings list.

Note: If both properties are specified, the name found in the Managed Cluster settings list is used.

The default value for the Cluster Receiver Name property for a Managed Cluster is CH.2.&QMGR<1:4>.4.&CLUSTER<1:8>. Because the configuration product assigns the value of the queue manager name to the QMGR symbolic variable, and the name of the managed cluster to the CLUSTER symbolic parameter, the resulting channel name will contain the first 4 characters of the queue manager name and the first 8 characters of the cluster name.

For example: if queue manager QM1 is a member of managed cluster CLUSTERA, then by default a cluster receiver channel is created with the name CH.2.QM1.4.CLUSTERA. The cluster receiver is located in resource group RG.4.CLUSTERA.OBJECTS.

If the Cluster Receiver Name in the Managed Cluster settings list is blank, then the value found in the Clusters section of the Queue Manager settings list is used instead. The default value for this property is CH.2.&QMGR<1:15>, implying that the first 15 characters of the queue manager name will be used in the channel name.

If the queue manager is a member of more than one cluster, by default a separate cluster receiver channel is created for each cluster. However, it is possible to define the configuration so that a single cluster receiver channel can be shared across multiple clusters. If the name to be specified for the cluster receiver is the same for more than one cluster (this can only happen if the cluster name is not part of the channel name), then a single cluster receiver channel is generated. The definition of the cluster receiver channel will refer to a cluster namelist containing the names of each cluster that the channel is associated with.

Cluster receiver channel prototype

You can specify that the cluster receiver channel be based on a prototype. You can specify the name of the prototype either in the Cluster Resources section of the Managed Cluster settings list, or in the Clusters section of the Queue Manager settings list. If the name of the cluster receiver channel was obtained from the Managed Cluster settings, then the name of the cluster receiver prototype is also obtained from the Managed Cluster setting; otherwise, the prototype name is obtained from the Queue Manager settings.



The following properties are automatically associated with the cluster receiver channel; hence, you cannot modify them:

You can modify all other properties of the cluster receiver channel.

Cluster sender channels

Cluster sender channels are generated by the configuration product to provide predefined connections to queue managers that are acting as full repositories. Cluster sender channels are generated for a queue manager for each of the following:

� each full-repository queue manager in the cluster, for which the Automatically connect all other queue managers in the cluster check box is selected (in the Queue Manager Name section of the Cluster Queue Manager settings list).

� each queue manager specified in the Queue Managers to predefined Cluster Sender Channels field (in the Channels section of the Cluster Queue Manager settings list).

The name of the cluster sender channel must match the name of the cluster receiver channel that the sender is to communicate with. Therefore, you have no direct control over the name assigned to the cluster sender. The configuration product determines the name by locating the cluster receiver channel on the queue manager to be connected to.

The channel name, connection name, and transport type properties of the cluster sender channel are taken from the definition of the corresponding cluster receiver channel, and you cannot directly modify them. The Cluster Name and Cluster Namelist properties are set automatically depending on the names of the managed clusters that the channel is associated with. You can set all other properties of the channel.

Local queues

The configuration product generates a local queue for each uniquely-named cluster queue that indicates residence on the queue manager. When a cluster queue is defined, you indicate which queue managers the queue is to reside on (in the Cluster Queue Location section of the Cluster Queue settings list). If you select a queue manager name in this section, a local queue is generated within that queue manager.

All properties of the local queue, including its name and based-on prototype, are copied directly from the cluster queue definition.

If you create the cluster queue by dragging and dropping a local queue prototype into the managed cluster definition, then the generated local queue is also based on the local queue prototype.

Channel name described above

Connection name The connection name is taken from the values in the Auto Start section of the Queue Manager settings list.

Transport type Taken from the Default Network Protocol property in the Cluster section of the Managed Cluster settings list.

Cluster Name and Cluster Namelist

Set automatically depending on the names of the managed clusters that the channel is associated with.



If a queue manager is associated with multiple clusters, and two or more duplicately-name cluster queue definitions specify that the queue is to reside on the queue manager, then the cluster queue definitions are merged to create the local queue. See “Generation of local queues” on page 135.

Namelists

The configuration product generates namelists resources on an as-needed basis. Because WebSphere MQ does not allow a resource to refer directly to more than one cluster name, namelists may be required when a queue manager is participating in more than one managed cluster.

� If a resource is associated with more than one cluster, the resource must contain a reference to a cluster namelist that specifies the names of all the clusters.

� If the configuration product determines that a product-managed configuration object should be associated with more than one cluster, then it builds a namelist object that specifies the clusters. The namelist is placed in the non cluster-specific resource group. See “Resource group objects” on page 132.

The configuration product always builds the minimum required number of namelist objects, and allows namelists to be shared among resources associated with the same set of clusters.

For example: If there are two local queues generated which are both associated with CLUSTERA and CLUSTERB, then the configuration product builds a single namelist specifying both cluster names, and sets the Cluster namelist property (in the Clusters section of the Queue settings list) in both queue definitions to refer to the same namelist.

The name of the namelist is determined by the Namelist name property (in the Clusters section of the Queue Manager settings list). The Namelist name property provides a prefix for each generated namelist name. A numeric suffix is added to each namelist name to provide uniqueness.

As changes are made to the definitions of the clusters that a queue manager is participating in, namelist definitions may be automatically created, deleted, or altered by the configuration product.

Generation of local queues

When an identically-named cluster queue exists in more than one cluster in the configuration, the potential exists for conflicting definitions, especially if one or more queue managers exist in both clusters.

For example: Let’s say the configuration defines managed clusters CLUSTERA and CLUSTERB. Queue Manager QM1 exists within both clusters. A cluster queue called QUEUEA exists in both CLUSTERA and CLUSTERB, and in both definitions, you indicated that QUEUEA should reside on Queue Manager QM1.

As a result of these definitions, the configuration product generates the definition for a single local queue on QM1 called QUEUEA, and associates the local queue with both clusters. Normally, the properties of the generated local queue are copied directly from the cluster queue, but in this case there are multiple cluster queue definitions, one residing in CLUSTERA, and the other in CLUSTERB. Which cluster queue is used?



The answer is that they both are. The properties associated with the QUEUEA cluster queue within CLUSTERA are merged with the properties associated with the cluster queue definition within CLUSTERB. If there are conflicting properties, the configuration product detects this as an error, and does not generate the local queue. For example, if the QUEUEA definition within CLUSTERA specifies a Maximum Queue Depth of 500, and the QUEUEA definition within CLUSTERB specifies a Maximum Queue Depth of 1000, the configuration product detects the conflict, and stops the local queue from being generated. The conflict is noted by the configuration manager as a background error. In addition, when a Validate function is performed against a cluster queue, the configuration manager will detect potential conflicts with other cluster queue objects, and inform the user of the conflict.

Modifying objects within a clusterNote: Modifying objects within a cluster may involve modifying, creating, and deleting

objects which are not necessarily the targets of the action, but are associated with a defined queue manager object. For example, the modification of a cluster may cause the configuration product to attempt to create cluster sender and receiver channels on the cluster queue managers. You must have the appropriate access to the defined queue manager at the time the queue manager is dragged and dropped on the managed cluster. You must have ALTER access to the appropriate security profiles (as if attempting to create the channels manually) in order for this processing to complete successfully.

When you modify the managed cluster itself, the Span and Scope of control feature ensures that the current user not only has authorization to the Managed Cluster, but also has authorization to each queue manager participating in the cluster. Likewise, when a cluster queue within the cluster is checked for access, the Span and Scope of control feature also verifies that you have the appropriate authorization to the managed cluster itself, and to all queue managers participating in the cluster.

Procedure to remove a queue manager from a managed cluster

To remove a queue manager from a managed cluster:



3. In the defined view tree, expand the managed cluster that is to be modified.

The Cluster Queue Manager configuration object for the queue manager you want to delete displays here. Right-click on it and, from the pop-up menu, select Select base object.

4. The configuration object for the queue manager is now selected. Right-click and, from the pop-up menu, select Action > Submit MQ command.

In the dialog that displays next, enter the WebSphere MQ command to suspend the queue manager. The command to suspend the queue manager is of the form:

suspend qmgr cluster(clustername)



where clustername is the name of the managed cluster. Click OK to submit the command.

5. In the defined view tree, expand the resource group containing cluster resources defined for this queue manager.

The cluster resources for this queue manager display here. Right-click each channel and, from the pop-up menu, select Action > Stop.

6. In the defined view tree, if it is not already expanded, once again expand the managed cluster that is to be modified.

Right-click the Cluster Queue Manager configuration object for the queue manager you want to delete and, from the pop-up menu, select Delete > Defined. This will delete the queue manager from the defined cluster as well as its defined resources for the cluster.

7. Right-click the configuration object for the queue manager and, from the pop-up menu, select Update actual from defined.

This should remove the real cluster resources for the queue manager.



Audit Logging 139

Audit Logging

IntroductionThis chapter discusses the audit logging feature, which logs all of the changes to your defined and actual configurations that were made using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

Chapter contentsAudit Logging Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Historical Disk Space Requirements for the Audit Log . . . . . . . . . . . . . . . . . . . . . . . 141Audit Log Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

9

Audit Logging Feature


Audit Logging Feature

DescriptionThe Audit Logging feature enables you to view historical records of the changes you make to your defined and actual configurations using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. Auditors, WebSphere MQ system administrators, or anyone else interested in determining configuration changes can view this information in easy-to-read report format.

The changes reported include:

� creation of new objects or action schedules

� deletion of objects or action schedules

� changes to settings

� updates to defined or actual objects

� actual object discoveries

� prototype disinheritance

� security violations

� changes to product-managed configuration objects made as a result of a change to a managed cluster

Details of operationThe IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration audit logging feature is enabled by default. However, if you want, you can deactivate this feature.

To disable the audit log on distributed plaforms, use the environmental variable KCF_AUDIT. A value of NO disables audit logging. The default is YES.

To disable the audit log on z/OS, use the Configuration tool to reconfigure the IBM Tivoli OMEGAMON XE for WebSphere Business Integration product package. When you “Configure OMEGAMON XE for WebSphere MQ Configuration” the “Configuration Auditing” option controls this feature. If you do not want to use this feature, change the value to N.

If your Candle Management Server is on z/OS, and you have the CMS enhanced security feature enabled, you can control access to the audit log by defining a RACF profile called ADMIN.AUDIT. Users must have READ access to this profile to view audit log reports.

For more information about accessing the Configuration tool, see Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS.

Archiving the audit logFor performance and storage considerations, you should archive the audit log on a regular basis.

Audit Logging 141

Historical Disk Space Requirements for the Audit Log

Historical Disk Space Requirements for the Audit Log

OverviewBecause 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 audit log data collection.

This section provides the system administrator with basic record size information for the table from which audit log data (historical data) is collected.

Audit log data tableThis data table is used for logging changes made to your configuration. You can use this table if you are using archiving and conversion facilities described in the Historical Data Collection Guide for IBM Tivoli OMEGAMON XE Products which you can find on the OMEGAMON Platform and CandleNet Portal Documentation CD that accompanied this product. This log data is written only on the CMS node and cannot be configured by the historical configuration program.

Note: *Based on making 100 configuration updates per 24-hour period.

Audit log table record size

Disk space requirement worksheetUse the following worksheet to estimate expected file sizes and the additional disk space requirements for your site. A sample calculation is provided for the audit log history table.

History Table Filename for Historical Data

Default HDC Table

Estimated Space Required per managed

system per 24 hours

Audit Log KCFAUDIT No 59 kilobytes*

History Table Record Size Frequency

Audit Log 600 bytes 1 record per change to the configuration

Interval Record Size

Formula Expected File Size per 24 Hours

N/A 600 bytes (600 x 100) / 1024 for 100 configuration changes

59 kilobytes

Audit Log Reports


Audit Log Reports

About audit log reportsThis report contains information about each change to your defined and actual configurations, including the name of the user who made the changes. Depending on the type of configuration change, you can access additional details reports.

Accessing audit log reportsUse the Audit Log workspace to access the Audit Log report.

To view an Audit Log report:

� Specify a custom time period for which you want to view records (using the Start time and End time controls), then click Show Audit Log.

or

� Click one of the predefined time periods for which you want to view records. The choices are: Last week log, Yesterday log, Last hour log, Last 15 minutes log.

The Audit Log report opens.

Accessing additional details reportsAn additional details report is available for entries in the Audit Log report that represent update and drag/drop actions. The contents of the report vary according to the type of action.

For update actions, a detailed report contains one row for every property that was altered. Every row contains the name of the property and its before and after values.

For drag/drop actions, a detailed report contains the name of the original configured system, the name of the original parent, and the name of the new parent.

To get additional information for a particular entry in the Audit Log report:

1. Highlight an entry that contains one of the following actions: DragDrop Copy, Settings Change, Update Defined.

2. Click Open as Details. The Details report opens.

Backing up the Configuration Database 143

Backing upthe Configuration Database

IntroductionThis chapter explains how to back up and restore the configuration database or change from one to the other of the supported configuration database types. Background information and step-by-step procedures are provided.

Chapter contentsBacking up the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Restoring the Configuration Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Changing the Configuration Database Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

10

Backing up the Configuration Database



About the backup processIt is a good practice to regularly back up the configuration database.

Note: In order to restore the configuration database, a previous back up of the configuration database must have been performed.

The backup process is performed using a CandleNet Portal client. The backup process does not interfere with the functioning of the configuration manager, nor does the Candle Management Server need to be disabled in order to execute the backup process.

The backup begins only if there are no outstanding deferred database updates pending; the backup also waits until all database commits have completed. While the backup is running, it is possible to fetch records from the database as required by other transactions; however, any deferred database updates that are created while the backup is running will remain queued until the backup completes. This will not prevent other update transactions from running.

The format of the backup file is platform-independent; therefore, the backup process can be used to migrate the configuration data from one platform to another. If you choose to use FTP to accomplish this, you must specify ASCII format. Also, if you transfer a backup file to z/OS, the LRECL of the receiving data should be defined as follows:

RECFM=FB,LRECL=440,BLKSIZE=<some multiple of 440>

There is only one procedure to back up the configuration database file regardless of the type of database (the product-provided Internal type or the DB2 Universal Database type) that your site uses for the configuration database.

Procedure to back up the configuration databaseTo back up the configuration database to a file:

1. Ensure you are in update mode.The Configuration View displays.

2. In the Configuration View, click Backup configuration database.

You are prompted to supply a file name.

3. Enter the name of the file, on the hub CMS machine, where you want the configuration database backed up. Note the format of the filename is dependant upon the operating system on which the CMS runs:

� If the CMS is on UNIX, this name identifies a file in the candlehome/tables/CMS_Name directory, where candlehome is the directory into which you installed this Tivoli OMEGAMON XE product package and CMS_Name is the name of your Candle Management Server. If the file does not exist, it is created; if it does exist, its current contents are overwritten.



� If the CMS is on Windows, this name identifies a file in the current CMS working directory (for example, c:\Candle\CMS). If the file does not exist, it is created; if it does exist, its current contents are overwritten.

� If the CMS is on z/OS, this name references a predefined sequential dataset. Do not enclose the name in quotes. The DCB information required for this dataset is:

RECFM=FB,LRECL=440,BLKSIZE=<some multiple of 440>

After you have entered the name of the file, click OK.

4. Wait for the message that the configuration database was successfully backed up, and click OK.

Restoring the Configuration Database



About the restoration processThe backup file which is needed for restoration must have been previously created as described in “Backing up the Configuration Database” on page 144.

The restoration process is performed at the hub Candle Management Server.

In the event that it is necessary for you to restore the contents of the configuration database from the backup file, use one of the restore utilities listed below. Use the restore utility that is appropriate for the type of configuration database used by your hub CMS.

Product-provided Internal type configuration database restoration options

– If the CMS is on UNIX, use the RestoreMQConfig utility located in the candlehome/bin directory where candlehome is the directory into which you installed this Tivoli OMEGAMON XE product package.

– If the CMS is on Windows, use the KCFCRSTR utility located in the current CMS working directory (for example, c:\Candle\CMS).

– If the CMS is on z/OS, use the KCFARSM utility.For sample JCL to run the KCFARSM utility, see the member named KCFRCDBJ that is located in the &RHILEV..TKANSAM library.

DB2 Universal Database type configuration database restoration options

– If the CMS is on UNIX, use the RestoreMQConfigDB2 utility located in the candlehome/bin directory where candlehome is the directory into which you installed this Tivoli OMEGAMON XE product package.

– If the CMS is on Windows, use the KCFCRST2 utility located in the current CMS working directory (for example, c:\Candle\CMS).

– If the CMS is on z/OS, use the KCFCRST2 utility.For sample JCL to run the KCFCRST2 utility, see the sample member named KCFRSDB2 that is located in the &RHILEV..TKANSAM library.

Note that the current contents of the configuration database are completely replaced by the contents of the backup file.



Procedure to restore a product-provided internal type configuration databaseTo restore the product-provided Internal type of configuration database from a backup file that you previously created:

1. If the Candle Management Server (CMS) is running, stop it now.

2. If the CMS is on UNIX, execute the following at a command prompt when you are in the candlehome/bin directory:

RestoreMQConfig -i InputBackupFile -t CMS_Name

where:

� InputBackupFile is the full path and name of the configuration database backup file

� CMS_Name is the name of the Candle Management Server

Hint: At the command prompt, you can enter RestoreMQConfig with no operands to display usage information for this utility.

For example, if your configuration database backup file is named MQConfigDB and your CMS is named HUBCMS, your actual input from a command prompt when you are in the candlehome/bin directory might be:

RestoreMQConfig -i /users/candle/tables/HUBCMS/MQConfigDB -t HUBCMS

You are prompted to confirm the operation. Enter y to proceed.

3. If the CMS is on Windows, execute the following at a command prompt when you are in the current CMS working directory:

kcfcrstr -i input_file -o database_name

where:

� input_file is the name of the configuration database backup file

� database_name is the name of the configuration database file (for example: RKCFAPLD)

Hint: At the command prompt, you can enter KCFCRSTR with no operands to display usage information for this utility.

4. If the CMS is on z/OS, see the member named KCFRCDBJ that is located in the &RHILEV..TKANSAM library. Modify the sample JCL found in this member to suit your environment, then submit it to execute the KCFARSM utility.



Procedure to restore a DB2 UDB type configuration databaseTo restore the DB2 UDB type of configuration database from a backup file that you previously created:

1. If the Candle Management Server (CMS) is running, stop it now.

2. If the CMS is on UNIX:

1. Permissions are required for the configuration database. The User ID of the person who will stop then restart the CMS on UNIX must have appropriate permissions in order to successfully work with the configuration database. The CMS will shut down if the user starting the CMS does not have permissions to the Configuration Database schema (KCFT) and tables (KCFT.KCFATTRIBUTES, and KCFT.KCFOBJECT). A restored database has to be granted permissions for users or groups. The appropriate DB2 GRANT commands to allow a user to work with the database are listed below for a user named usr2.GRANT CREATEIN, ALTERIN ON SCHEMA KCFT TO USER usr2

GRANT ALL ON KCFT.KCFATTRIBUTES TO USER usr2

GRANT ALL ON KCFT.KCFOBJECT TO USER usr2

Note these DB2 GRANT commands differ from those used to install and setup the DB2 UDB configuration database on UNIX.

2. Execute the following at a command prompt when you are in the candlehome/bin directory:RestoreMQConfigDB2 -i input_file -t CMS_Name -d database_name -u userid -p password

where:

– input_file is the full name and path of the configuration database backup file

– CMS_name is the name of the Candle Management Server

– database_name is the name of the DB2 configuration database into which the data in input_file is to be restored

– userid is the User ID with write access to the DB2 configuration database

– password is the password used for write access the DB2 configuration database

Hint: At the command prompt, you can enter RestoreMQConfigDB2 with no operands to display usage information for this utility.

3. If the CMS is on Windows, execute the following at a command prompt when you are in the current CMS working directory (for example, c:\Candle\CMS):

kcfcrst2 -i input_file -d database_name -u userid -p password

where:

� input_file is the full name and path of the configuration database backup file

� database_name is the name of the DB2 configuration database into which the data in input_file is to be restored

� userid is the User ID used to administer DB2



� password is the password used to administer DB2

Hint: At the command prompt, you can enter KCFCRST2 with no operands to display usage information for this utility.

For example, if your configuration database backup file is named c:\Candle\CMS\RKCFbackup, your DB2 configuration database is named rkcfaplt, your userid is db2admin, and your password is db2, you execute the following command.

kcfcrst2 -i c:\Candle\CMS\RKCFbackup -d rkcfaplt -u db2admin -p db2

4. If the CMS is on z/OS, see the sample member named KCFRSDB2 that is located in the &RHILEV..TKANSAM library. Modify the sample JCL found in this member to suit your environment, then submit it to execute the KCFCRST2 utility.

Changing the Configuration Database Type



About this processThe configuration database backup file generated by the backup process can be used to change from one supported configuration database type to another supported configuration database type. Currently the product-provided Internal type or the DB2 Universal Database (UDB) type are supported.

After the backup process is complete, the rest of this process is performed at the hub Candle Management Server.

Setting up the configuration database is part of setting up support for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration on your hub CMS. Refer to one of these books:

– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX


You can find these books on the IBM Tivoli OMEGAMON XE for WebSphere Business Integration Documentation CD that accompanied this product.

Changing from DB2 UDB type to Internal type configuration databaseChanging the configuration database type from the DB2 UDB type to the product-provided Internal type is a manual process, the general steps are:

1. Back up your existing configuration database, as described in “Backing up the Configuration Database” on page 144.

2. If the Candle Management Server (CMS) is running, stop it now.3. Use one of the following methods to reconfigure your hub CMS so that the Internal

type of configuration database will be used.– If the CMS is on UNIX, rerun the configuration process that was used to define

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to the Hub CMS. (See Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX.) In the CMS configuration dialog, the database section offers you a choice of database. Specify Internal.

– If the CMS is on Windows, open a command prompt in the current CMS working directory (for example, c:\Candle\CMS) and execute the KCFDataSource.exe program. A dialog with a Database Type choice displays. In the Database Type area of the dialog, select Internal then click OK. The registry entries are adjusted so that the product-provided Internal type configuration database will be used.

Hint: At the command prompt, you can enter “KCFDataSource /?” to display usage information for this utility.



– If the CMS is on z/OS, use the Configuration tool to re-execute the step in which you configure the IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration component product to Register with the local CMS. (See Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS.) In this step, a panel with a Database Type field displays. On this panel, specify the Internal database type. Press Enter, review the JCL, and re-submit the job as usual.

4. Restore the contents of the configuration database from the backup file into the new configuration database. Follow the instructions in “Procedure to restore a product-provided internal type configuration database” on page 147.

5. Start the Candle Management Server.

Changing from Internal type to DB2 UDB type configuration databaseChanging the configuration database type from the product-provided Internal type to the DB2 UDB type is a manual process, the general steps are:

1. Back up your existing configuration database, as described in “Backing up the Configuration Database” on page 144.

2. If the Candle Management Server (CMS) is running, stop it now.3. Setup DB2 UDB for use as the configuration database as described in one of the

following books.– Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business

Integration on Windows and UNIX


4. Use one of the following methods to reconfigure your hub CMS so that the DB2 UDB type of configuration database will be used.– If the CMS is on UNIX, rerun the configuration process that was used to define

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to the Hub CMS. (See Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX.) In the CMS configuration dialog, the database section offers you a choice of database. Specify DB2. Provide the DB2 home directory and the DB2 instance name as described in the book.

– If the CMS is on Windows, open a command prompt in the current CMS working directory (for example, c:\Candle\CMS) and execute the KCFDataSource.exe program. A dialog with a Database Type choice displays. (See Installing and Setting up IBM Tivoli OMEGAMON XE for WebSphere Business Integration on Windows and UNIX.) In the Database Type area of the dialog, select the option that contains the words DB2 UDB. Fill in the required DB2 information, then click OK. The registry entries are adjusted so that the DB2 UDB type configuration database is used.

Hint: At the command prompt, you can enter “KCFDataSource /?” to display usage information for this utility.



– If the CMS is on z/OS, use the Configuration tool to re-execute the step in which you configure the IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration component product to Register with the Local CMS. (See Configuring IBM Tivoli OMEGAMON XE for WebSphere Business Integration on z/OS.) In this step, a panel with a Database Type field displays. On this panel, specify the DB2 database type and fill in the required DB2 information. Press Enter, review the JCL, and re-submit the job as usual.

5. Restore the contents of the configuration database from the backup file into the new configuration database. Follow the instructions in “Procedure to restore a DB2 UDB type configuration database” on page 148.

6. Start the Candle Management Server.

Remote Queue Manager Configuration 153

Remote Queue Manager Configuration

IntroductionThis appendix describes how to set up the WebSphere MQ link between the two queue managers. It also tells you how to add a remote queue manager object to your Defined View.

Appendix contentsWhat Is Remote Configuration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Setting up Queue Managers for Remote Configuration . . . . . . . . . . . . . . . . . . . . . . . 156Examples of Possible WebSphere MQ Configurations . . . . . . . . . . . . . . . . . . . . . . . . 158Creating Remote Queue Manager Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

A

What Is Remote Configuration?



OverviewIt is possible to configure WebSphere MQ environments in which you cannot, or choose not to, install IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration (the configuration agent, hereafter). To do this you must provide a means for two-way communication between a local queue manager and a queue manager on the remote system.

Note: IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration cannot discover or create remote queue managers. Given this limitation, IBM strongly recommends you start a configuration agent for every queue manager running on a supported platform. This includes the node where the CMS is running if it also runs WebSphere MQ.

Remote configuration is a technique for configuring a queue manager even though there is no configuration agent running on the same system. In remote configuration, a configuration agent running with a queue manager on one node performs configuration tasks on another node or on a different queue manager on the same node. It does this using two-way communication between the local queue manager and the queue manager without a configuration agent. You can use remote configuration to configure queue managers running on any supported version platform for which configuration agents are not currently available.



How does remote configuration work?The purpose of setting up two-way communication is to make it possible for the following process to occur:

1. The configuration agent establishes a connection with its local queue manager.2. The configuration agent sends configuration commands to the remote queue

manager’s command server using WebSphere MQ distributed queueing.3. The remote command server processes the configuration message.4. The remote command server sends a response back to the configuration agent

through the local queue manager.

In the figure above, CandleNet Portal sends WebSphere MQ configuration commands to the OMEGAMON configuration agent (the “OCA”) on the AIX node by way of the Candle Management Server on the same node. The configuration agent then passes the commands to the remote queue manager's command server through the local queue manager.

Note: The local queue manager that passes configuration commands is used to make an indirect connection to the remote queue manager. You specify the name of this queue manager when you define the remote queue manager. See “Connecting Queue Managers” on page 75 for instructions.

Once you define both the remote queue manager and the indirect connection to it, the configuration agent can determine its current WebSphere MQ objects (queues, channels, processes, and the like) and use that information in building new objects or redefining current objects.

cmdsvr

WebSphere MQ

cmdsvr

CMS on AIX

OCA on AIX

CandleNet Portal

channel to remote node

channel from remote node

WebSphere MQ

Setting up Queue Managers for Remote Configuration



OverviewThe configuration agent uses normal WebSphere MQ commands to configure a remote queue manager using distributed queueing. However, you will not be able to configure a queue manager on a remote node if you have not provided the means to communicate WebSphere MQ commands between them. You must ensure that you have defined channels and transmission queues for two-way communication between the queue manager on the node running the configuration agent and the queue manager on the node without a configuration agent.

Once you have established two-way communication, you can use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to define the remote queue manager and the local queue manager used for the indirect connection to it.

RequirementsFor each remote queue manager you want to configure, complete the following steps:

� Ensure channels exist for two-way communication between the local and remote queue managers.

� Ensure transmission queues exist on the local queue manager and on the remote queue manager so the configuration agent can communicate with the remote queue manager's command server.

“Examples of Possible WebSphere MQ Configurations” on page 158 describes three different approaches for configuring WebSphere MQ for two-way communication. You may be able to adapt one of these methods for your site.

Checking your existing configuration firstIf you know your site has defined the WebSphere MQ environment such that every queue manager can route a message to every other queue manager using the manager name, you can use your existing definitions. When checking for this, ask yourself two questions for each remote queue manager you plan to configure:

� Does the existing WebSphere MQ environment already have channels and transmission queues I can use, or do I want, or need, to create new channels and transmission queues for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration?

� Is there a direct WebSphere MQ link between the local queue manager and the remote queue manager, or do messages sent from one to the other hop through intermediate WebSphere MQ nodes?

You must answer these questions (and, possibly, define transmissions queues and channels) for every remote queue manager you want to configure.



Ensuring channels exist for two-way communications You must ensure your WebSphere MQ environment has the appropriate channels defined for two-way communication between the remote queue manager to be configured and local queue manager that will communicate with the configuration agent.

IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration supports both sender/receiver and server/requester channels using any WebSphere MQ-supported communications protocol.

“Examples of Possible WebSphere MQ Configurations” on page 158 shows WebSphere MQ commands that define each of these environments.

Defining transmission queues for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration

If your WebSphere MQ network already enables two-way communication between the remote queue manger and the local queue manager, IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration can use your existing configuration. However, you must ensure that one of the following is true:

� You have two transmission queues, one on the remote queue manager that has the same name as the local queue manager and one on the local queue manager that has the same name as the remote queue manager.

or

� If your configuration has existing transmission queues that you want IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration to use but they do not have the same names as the destination queue managers, you have assigned queue manager aliases to them (using the DEFINE QREMOTE command of WebSphere MQ) that reflect the names of the destination queue manager.

“Examples of Possible WebSphere MQ Configurations” on page 158 shows WebSphere MQ commands that define each of these environments.

Multihopping to the remote queue managerThe environment described above must exist when you multihop to the remote system—when there are intermediate WebSphere MQ queue managers for receiving and then retransmitting messages between the local and remote queue managers. However, in this case you must also define queue manager aliases on each intermediate queue manager to identify the destination queue managers. See page 160 for an example of configuring a remote queue manager through multihopping.

Examples of Possible WebSphere MQ Configurations



OverviewThere are many ways to configure WebSphere MQ so the local queue manager can pass commands to the remote queue manager and receive replies. These examples should help you understand how you might configure your WebSphere MQ network for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration.

Example 1The simplest way to configure WebSphere MQ is to create new transmission queues and channels specifically for IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. This example shows how you can configure IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration running on z/OS node MVS1 (queue manager name MQM1) so it can configure the WebSphere MQ environment running on OS/400 node OS400A (queue manager name OS400QM). Note that this example uses sender/receiver channels.

These are the definitions for OS400QM:

DEFINE QLOCAL(MQM1) USAGE(XMITQ)

DEFINE CHANNEL(OS400QM.TO.MQM1) +

CHLTYPE(SDR) TRPTYPE(TCP) +

CONNAME(MVS1) +

XMITQ(MQM1)

DEFINE CHANNEL(MQM1.TO.OS400QM) +

CHLTYPE(RCVR) +

TRPTYPE(TCP)

These are the definitions for MQM1:

DEFINE QLOCAL(OS400QM) USAGE(XMITQ)

DEFINE CHANNEL(MQM1.TO.OS400QM) +

CHLTYPE(SDR) +

TRPTYPE(TCP) +

CONNAME(OS400A) +

XMITQ(OS400QM)

DEFINE CHANNEL(OS400QM.TO.MQM1) +

CHLTYPE(RCVR) +

TRPTYPE(TCP)



Example 2The second example illustrates how you can modify this sample environment by assigning queue manager aliases to your existing transmission queues, which are named according to their destination nodes (that is, MVS1 and OS400A) rather than their destination queue managers. Since both the existing transmission queues and channels are being reused, no new definitions for them are needed.

This is the new definition for queue manager OS400QM:

DEFINE QREMOTE(MQM1) XMITQ(MVS1)

This is the new definition for queue manager MQM1:

DEFINE QREMOTE(OS400QM) XMITQ(OS400A)



Example 3In the third and final example, you also want to use IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration running on MVS1 to configure your company’s Sun Solaris network in Los Angeles; this network comprises nodes SUNLA1, SUNLA2, and SUNLA3 (their queue managers are named the same as the nodes they run on). All messages from one of these nodes pass first to the local z/OS queue manager, QMLA, and then to the z/OS queue manager in Dallas, QMDL, which passes the messages to MQM1. The figure below shows a three-jump link from MQM1 to Solaris Network:

All the necessary connections (that is, transmission queues and channels) are already in place for a WebSphere MQ application running on SUNLA1, SUNLA2, or SUNLA3 to pass messages to and receive messages from a WebSphere MQ application running on MVS1. You need only add the appropriate queue manager aliases to the various queue managers.

This example assumes the existing transmission queues are not named with the queue manager they send messages to. Therefore, each destination queue manager requires a queue manager alias that points to the other destination queue manager. In addition, each intermediate queue manager requires two queue manager aliases, one for each destination queue manager.



SUNLA1, SUNLA2, and SUNLA3 each require this additional definition:

DEFINE QREMOTE(MQM1) XMITQ(local-xmitq-to-QMLA)

QMLA requires these additional definitions to serve as an intermediate queue manager between QMDL and the three Solaris queue managers:

* To pass messages from the Solaris queue managers to MQM1 * (using QMDL)

DEFINE QREMOTE(MQM1) XMITQ(local-xmitq-to-QMDL)

* To pass messages to the Solaris queue managers from MQM1

DEFINE QREMOTE(SUNLA1) XMITQ(local-xmitq-to-SUNLA1)



QMDL requires these additional definitions to serve as an intermediate queue manager between MQM1 and QMLA:

* To pass messages from the Solaris queue managers to MQM1

DEFINE QREMOTE(MQM1) XMITQ(local-xmitq-to-MQM1)

* To pass messages to the Solaris queue managers from MQM1* (using QMLA)

DEFINE QREMOTE(SUNLA1) XMITQ(local-xmitq-to-QMLA)



And finally, MQM1 requires these additional definitions to pass messages to the Solaris queue managers using QMDL and QMLA:

DEFINE QREMOTE(SUNLA1) XMITQ(local-xmitq-to-QMDL)



Creating Remote Queue Manager Objects



OverviewWhen you add a remote queue manager object to your defined configuration, you must specify its indirect connection to a configuration agent.

This section describes how to add a remote queue manager object to your Defined View. The procedure assumes that you have completed the tasks described in “Setting up Queue Managers for Remote Configuration” on page 156.

ProcedureTo define a remote queue manager:



3. In the defined view tree, right-click on the configured system group to which you want to add the remote queue manager and, from the pop-up menu, select Create New Queue Manager. You are prompted to supply a name for the new object.

4. Specify the name of the existing remote queue manager.Note: Remote configuration requires that the remote queue manager already exist. See

“Setting up Queue Managers for Remote Configuration” on page 156.

5. Click OK.The new queue manager object is added to the defined view tree.

6. In the defined view tree, select the new remote queue manager object.The settings list for the object displays on the right side of the Defined View.

7. Expand the Connection section.

8. In the Connection section:� Select the Indirect Connection check box.

� In the Through queue manager field, enter the name of the configuration agent-connected queue manager through which you want to configure this remote queue manager or select one from the drop-down list. Specify the queue manager name exactly as it appears in the Defined View.

9. If your site uses a queue manager alias to connect the remote queue manager to the configuration agent-connected queue manager, specify that alias in the Queue Manager Alias field.

10. If the remote queue manager is running WebSphere MQ for z/OS, select the OS/390 check box.

11. Complete the remaining sections of the settings list as necessary. Click Help to display information about each parameter.






Messages 165

Messages

IntroductionThis appendix documents the KMC-prefixed messages produced by the OMEGAMON XE for WebSphere MQ configuration agent. It also documents the KCF-prefixed messages produced by the configuration manager within the Candle Management Server.

These two groups of messages are broken down into two subgroups each:

� The KMCnnnnx and KCFnnnnx messages are errors which are reported by either the OMEGAMON configuration agent or the configuration manager, respectively; then displayed by CandleNet Portal.

� The KMCRCAnnnx and KCFCMnnnx messages are written to the error log by either the agent or the configuration manager, respectively.

In each case, nnnn is either a three- or four-digit numeric identifier and x is the message type (E for error, W for warning, I informational, S for severe). The messages are listed alphabetically by group, then numerically within each group.

Appendix contentsKMC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166KCF Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260KMCRCA Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289KCFCM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Windows Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

B

KMC Messages


KMC Messages

These messages take the form KMCnnnnx; these are errors which are reported by the OMEGAMON configuration agent for WebSphere MQ then displayed by CandleNet Portal.

KMC0370E Channel listeners are not supported on this version of WebSphere MQExplanation: You attempted to create an actual WebSphere MQ Channel Listener connection channel; however, channel listeners are not supported on this WebSphere MQ version. Channel Listeners are supported on WebSphere MQ Version 6.0 and later.System Action: The current request fails.User Response: Delete the defined channel listener object.

KMC0002E Your request failed. An unanticipated WebSphere MQ error has occurred RC=code Reason=reasonExplanation: The WebSphere MQ Queue Manager returned an unanticipated error to a request from the Configuration Agent. The RC and Reason fields provide the WebSphere MQ return and reason codes, respectively.User Response: Look up the return and reason codes in the WebSphere MQ Application Programming Reference. If necessary, contact IBM Software Support.

KMC0003E Your request failed. Connection to queue manager lostExplanation: Connection to the queue manager from the OMEGAMON configuration agent has been lost. This can occur because the queue manager has ended.System Action: The Configuration Agent will retry the connection.User Response: Investigate why the queue manager connection was broken. If necessary, restart the queue manager and the configuration agent.

KMC0004E Your request failed. Not authorized for WebSphere MQ connectionExplanation: This reason code occurs only on z/OS. It occurs because the OMEGAMON configuration agent is not authorized to connect to the queue manager.System Action: Configuration agent processing is terminated.User Response: Ensure that the OMEGAMON configuration agent is authorized to connect to the queue manager.

KMC0005E Your request failed. WebSphere MQ connection shutting downExplanation: This reason code occurs only on z/OS. It indicates that the connection between the OMEGAMON configuration agent and the queue manager is shutting down.System Action: Configuration agent processing is terminated.User Response: Investigate why the queue manager connection is shutting down. If necessary, restart the queue manager and the OMEGAMON configuration agent.

KMC0012E Your request failed. No more WebSphere MQ handles availableExplanation: The OMEGAMON configuration agent issued an MQOPEN or MQPUT1 call, but the maximum number of open handles allowed for the agent has

Messages 167

KMC Messages

already been reached. Be aware that when a distribution list is specified on the MQOPEN or MQPUT1 call, each queue in the distribution list uses one handle.Explanation: Configuration agent processing terminates.User Response: Manually change the MAXHANDS property for the queue manager. If the problem persists, contact IBM Software Support.

KMC0013E Your request failed. Maximum number of WebSphere MQ connections reachedExplanation: The MQCONN call from the OMEGAMON configuration agent was rejected because the maximum number of concurrent connections has been exceeded.System Action: Configuration agent processing terminates.User Response: Either increase the size of the appropriate install parameter value or reduce the number of concurrent connections.

KMC0015E Your request failed. WebSphere MQ message too big for channelExplanation: The OMEGAMON configuration agent put a message to a remote queue, but the message is larger than the maximum message length allowed by the channel. This can occur for a queue manager that is being configured via an indirect connection.System Action: The current request is terminated.User Response: Increase the maximum message size of the channel to the remote queue manager.

KMC0016E Your request failed. WebSphere MQ message too big for queueExplanation: The OMEGAMON configuration agent attempted to put a message to a queue, but the message is larger than the maximum message length allowed by the queue. This can be caused by the definition for SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COM.System Action: The current request is terminated.User Response: Increase the maximum message size of the queue.

KMC0017E Your request failed. WebSphere MQ message too big for queue managerExplanation: The OMEGAMON configuration agent attempted to put a message to a queue, but the message is larger than the maximum message length allowed by the queue manager.System Action: The current request is terminated.User Response: Manually increase the MAXMSGL property for the queue manager.

KMC0018E Your request failed. An MQOPEN call was issued to create a dynamic queue, but a queue with the same name as the dynamic queue already existsExplanation: The configuration issued an MQOPEN call to create a dynamic queue, but a queue with the same name as the dynamic queue already exists.System Action: The current request is terminated.User Response: Restart the OMEGAMON configuration agent. Collect the agent log files, and contact IBM Software Support.

KMC Messages


KMC0019E Your request failed. The configuration agent is not authorized for WebSphere MQ accessExplanation: The OMEGAMON configuration agent is not authorized to perform the operation attempted. If the Client userid is defined at Queue Manager property is set for the queue manager, the problem could lie with the WebSphere MQ authorities associated with the user ID.System Action: Configuration agent processing is terminated.User Response: If the Client userid is defined at Queue Manager property is set, ensure that the user ID has sufficient authority to perform the action. Also ensure that the configuration agent has the required authority.

KMC0020E Your request failed. WebSphere MQ message data not convertedExplanation: The configuration made an MQGET call with the MQGMO_CONVERT option included in the GetMsgOpts parameter, and an error occurred during conversion of the data in the message.System Action: The current request is terminated.User Response: Collect the agent log files, and contact IBM Software Support.

KMC0021E Your request failed. WebSphere MQ object already existsExplanation: The OMEGAMON configuration agent made an MQOPEN call create a dynamic queue, but a queue with the same name as the dynamic queue already exists.System Action: The current request is terminated.User Response: Restart the configuration agent. Collect the agent log files, and contact IBM Software Support.

KMC0022E Your request failed. WebSphere MQ object damagedExplanation: The object accessed by the OMEGAMON configuration agent is damaged and cannot be used. For example, this may be because the definition of the object in main storage is not consistent, or because it differs from the definition of the object on disk, or because the definition on disk cannot be read.System Action: Configuration agent processing is terminated.User Response: It may be necessary to stop and restart the queue manager, or to restore the queue manager data from back-up storage. On OS/400, HP NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem.

KMC0023E Your request failed. WebSphere MQ object in useExplanation: An MQOPEN call was issued by the OMEGAMON configuration agent, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input; it also arises if the request is for exclusive input, but the object is already open for input (of any sort).System Action: Configuration agent processing is terminated.User Response: Restart the configuration agent. Collect the agent log files, and contact IBM Software Support.

Messages 169

KMC Messages

KMC0024E Your request failed. WebSphere MQ pageset errorExplanation: The OMEGAMON configuration agent encountered an error with the page set while attempting to access it for a locally defined queue. This could be because the queue is on a page set that does not exist. A console message is issued that tells you the number of the page set in error.System Action: Configuration agent processing is terminated.User Response: Check that the storage class for the queue maps to a valid page set using these commands:

DISPLAY Q(xx) STGCLASSDISPLAY STGCLASS(xx)DISPLAYUSAGE PSID

commands. If you are unable to resolve the problem, notify the system programmer, who should:1. Collect the following diagnostic information:

– A description of the actions that led to the error.

– A listing of the application program being run at the time of the error.

– Details of the page sets defined for use by WebSphere MQ.

2. Attempt to recreate the problem, and take a system dump immediately after the error occurs.

3. Contact IBM Software Support.

KMC0025E Your request failed. WebSphere MQ pageset fullExplanation: On an MQOPEN, MQPUT or MQPUT1 call from the Configuration Agent, a page set data set was found to be full while attempting to open or put a message on a locally defined queue. This reason code occurs only on z/OS.System Action: Configuration agent processing is terminated.User Response: Check which queues contain messages and look for any looping programs that might be unnecessarily filling up queues. Otherwise, request the system programmer to increase the size of the page set data sets.

KMC0026E Your request failed. WebSphere MQ queue is put inhibitedExplanation: The OMEGAMON configuration agent attempted to get a message from a queue, but MQGET calls are currently inhibited for the queue. This can be caused by the definition for SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COMMAND.INPUT (for z/OS). This can also be caused by the definition of SYSTEM.MQSC.REPLY.QUEUE (for distributed platforms), or SYSTEM.COMMAND.REPLY.MODEL (for z/OS).System Action: Configuration agent processing is terminated.User Response: Manually reset the put inhibited property for the queue.

KMC0028E Your request failed. WebSphere MQ queue deletedExplanation: The OMEGAMON configuration agent attempted to refer to a dynamic queue that has been deleted since the queue was opened.System Action: Configuration agent processing is terminated.

KMC Messages


System Action: Restart the configuration agent. Collect the agent log files, and contact IBM Software Support.

KMC0029E Your request failed. WebSphere MQ queue is fullExplanation: The OMEGAMON configuration agent attempted to put a message into a queue, but the maximum number of messages in the queue had already been reached. This can be caused by the definition for SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COMMAND.INPUT (for z/OS).System Action: Configuration agent processing is terminated.User Response: Manually reset the MAXMSGS property for the queue. This problem can also occur if the WebSphere MQ command server or a sender or server channel stops running.

KMC0031E Your request failed. WebSphere MQ queue manager not activeExplanation: The OMEGAMON configuration agent could not connect to the queue manager because the queue manager is not active.System Action: Processing for the queue manager is terminated.User Response: Start the queue manager.

KMC0032E Your request failed. WebSphere MQ queue manager not availableExplanation: The OMEGAMON configuration agent could not connect to the queue manager because it is not available for connection at this time.System Action: Processing for the queue manager is terminated.User Response: Ensure that the queue manager has been started.

KMC0033E Your request failed. WebSphere MQ queue manager quiescingExplanation: The OMEGAMON configuration agent could not communicate with the queue manager because it is quiescing.System Action: Processing for the queue manager is terminated.User Response: Wait until the queue manager has stopped, then restart it and the configuration agent, and restart the request.

KMC0034E Your request failed. WebSphere MQ queue manager stoppingExplanation: The OMEGAMON configuration agent could not communicate with the queue manager because it is shutting down.System Action: Processing for the queue manager is terminated.User Response: Wait until the queue manager has stopped, then restart it and the configuration agent, and restart the request.

KMC0035E Your request failed. No space available for WebSphere MQ queueExplanation: The OMEGAMON configuration agent attempted to put a message to a WebSphere MQ queue, but there is no space available for the queue on disk or other storage device.System Action: Configuration agent processing is terminated.User Response: Make more disk space available for the queue.

Messages 171

KMC Messages

KMC0036E Your request failed. Insufficient WebSphere MQ system resource availableExplanation: WebSphere MQ has insufficient system resources to complete the request successfully.System Action: Processing for the queue manager is terminated.System Action: Run the application when the machine is less heavily loaded. On OS/400, HP NonStop Kernel, and UNIX systems, consult the FFST record to obtain more detail about the problem.

KMC0037E Your request failed. WebSphere MQ security errorExplanation: The OMEGAMON configuration agent issued an MQCONN, MQOPEN, MQPUT1, or MQCLOSE call, but it failed because a security error occurred. On z/OS, the security error was returned by the External Security Manager.System Action: Processing for the queue manager is terminated.User Response: Note the error from the security manager, and contact your system programmer or security administrator. On OS/400, the FFST log contains the error information.

KMC0038E Your request failed. WebSphere MQ coded character set id invalidExplanation: The OMEGAMON configuration agent attempted to get a message from a WebSphere MQ queue, but the coded character-set identifier from which character data is to be converted is not valid or not supported.System Action: Configuration agent processing is terminated.User Response: Check the character-set identifier that was specified when the message was put or that was specified for the SourceCCSID parameter on the MQXCNVC call. If this is correct, check that it is one for which queue manager conversion is supported.

KMC0039E Your request failed. Integer encoding in WebSphere MQ message not recognizedExplanation: On an MQGET call issued by the OMEGAMON configuration agent, with the MQGMO_CONVERT option included in the GetMsgOpts parameter, the Encoding value in the message being retrieved specifies an integer encoding that is not recognized.System Action: Configuration agent processing is terminated.User Response: Check the integer encoding that was specified when the message was put. If this is correct, check that it is one for which queue manager conversion is supported.

KMC0040E Your request failed. Insufficient WebSphere MQ storage availableExplanation: A call from the OMEGAMON configuration agent cannot complete because sufficient storage is not available to the Queue Manager.System Action: Processing for the queue manager is terminated.System Action: Make more storage available. On z/OS, if no application problems are found, ask your systems programmer to increase the size of the region in which the queue manager runs.

KMC Messages


KMC0041E Your request failed. Unexpected WebSphere MQ error The call was rejected because an unexpected error occurred.Explanation: The request was rejected because an unexpected error occurred with WebSphere MQ.System Action: Processing for the current request is terminated.User Response: On z/OS, check whether any information has been displayed on the console. If this error occurs on an MQCONN call, check that the subsystem named is an active MQ subsystem. In particular, check that it is not a DB2 subsystem. If the problem cannot be recreated, contact your system programmer.

KMC0045E Your request failed. Unknown WebSphere MQ queue nameExplanation: The queue name is unknown.System Action: Processing for the current request is terminated.User Response: Specify a valid queue name.

KMC0047E Your request failed. Unknown WebSphere MQ transmission queueExplanation: On an MQOPEN or MQPUT1 call issued by the OMEGAMON configuration agent, a message is to be sent to a remote queue manager. The ObjectName or the ObjectQMgrName in the object descriptor specifies the name of a local definition of a remote queue (in the latter case).System Action: Processing for the current request is terminated.User Response: Ensure that the definition of the remote queue is correct and that the XMITQ specifies the name of a valid local transmit queue.

KMC0048E Your request failed. WebSphere MQ transmission queue not localExplanation: On an MQOPEN or MQPUT1 call issued by the OMEGAMON configuration agent, a message is to be sent to a remote queue manager. The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue, but one of the following applies to the XmitQName attribute of the definition:

� XmitQName is not blank, but specifies a queue that is not a local queue.

� XmitQName is blank, but RemoteQMgrName specifies a queue that is not a local queue.

System Action: Processing for the current request is terminated.System Action: Ensure that the definition of the remote queue is correct and that the XMITQ specifies the name of a valid local transmit queue.

KMC0049E Your request failed. WebSphere MQ transmission queue has incorrect usageExplanation: On an MQOPEN or MQPUT1 call, a message is to be sent to a remote Queue Manager, but one of the following occurred:

� ObjectQMgrName specifies the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION.

� The ObjectName or ObjectQMgrName field in the object descriptor specifies the name of a local definition of a remote queue but one of the following applies to the XmitQName attribute of the definition:

Messages 173

KMC Messages

– XmitQName is not blank, but specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION.

– XmitQName is blank, but RemoteQMgrName specifies a queue that does not have a Usage attribute of MQUS_TRANSMISSION.

– The queue name is resolved through a cell directory, and the remote queue manager name obtained from the cell directory is the name of a local queue, but it does not have a Usage attribute of MQUS_TRANSMISSION.

System Action: Processing for the queue manager is terminated.User Response: Ensure that the definition of the remote queue is correct and that the XMITQ specifies the name of a valid local transmit queue.

KMC0067E Your request failed. WebSphere MQ channel type invalidExplanation: The channel type associated with this channel is invalid.System Action: Validation fails.User Response: Ensure that the channel type is valid for the target platform.

KMC0069E Your request failed. WebSphere MQ transmit protocol type invalidExplanation: The transmit protocol specified on the channel definition is invalid.System Action: Validation fails.User Response: Ensure that the transmit protocol type is valid for the target platform.

KMC0070E Your request failed. WebSphere MQ batch size invalidExplanation: The batch size specified for the channel is not valid.System Action: Validation fails.User Response: Correct the batch size. The value must be greater than zero, and less than or equal to 9999.

KMC0071E Your request failed. WebSphere MQ disconnect interval invalidExplanation: The disconnect interval specified for the channel is not valid.System Action: Validation fails.User Response: Correct the disconnect interval. The value must be greater than or equal to zero and less than or equal to 999,999.

KMC0072E Your request failed. WebSphere MQ short retry count invalidExplanation: The short retry count specified for the channel is not valid.System Action: Validation fails.User Response: Correct the short retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0073E Your request failed. WebSphere MQ short timer value invalidExplanation: The short interval specified for the channel is not valid.System Action: Validation fails.User Response: Correct the short interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC Messages


KMC0074E Your request failed. WebSphere MQ long retry count invalidExplanation: The long retry count specified for the channel is not valid.System Action: Validation fails.User Response: Correct the long retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0075E Your request failed. WebSphere MQ long timer value invalidExplanation: The long interval specified for the channel is not valid.System Action: Validation fails.User Response: Correct the long interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0076E Your request failed. WebSphere MQ sequence number wrap invalidExplanation: The sequence number wrap specified for the channel is not valid.System Action: Validation fails.User Response: Correct the sequence number wrap. The value must be greater than or equal to 100, and less than or equal to 999,999,999.

KMC0077E Your request failed. WebSphere MQ maximum message length invalidExplanation: The maximum message length specified for the queue or channel is not valid.System Action: Validation fails.User Response: Correct the maximum message length. On AIX, HP-UX, Solaris, and Windows, specify a value greater than or equal to zero, and less than or equal to the maximum message length for the queue manager. On other platforms, specify a value greater than 0, and less than or equal to 4,194,304.

KMC0078E Your request failed. WebSphere MQ put authority invalidExplanation: The put authority specified for the channel is not valid.System Action: Validation fails.User Response: Correct the put authority.

KMC0081E Your request failed. MSSeries message truncatedExplanation: The command server received a message from the OMEGAMON configuration agent that is larger than its maximum valid message size.System Action: Validation fails.User Response: Ensure that the MAXMSGL property of the SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COMMAND.INPUT (for z/OS) is large enough.

KMC0084E Your request failed. WebSphere MQ data conversion value invalidExplanation: The convert property specified for the channel is not valid.System Action: Validation fails.User Response: Correct the convert property.

KMC0088E Your request failed. WebSphere MQ MCA type invalidExplanation: The message channel agent type specified for the channel is invalid.

Messages 175

KMC Messages

System Action: Validation fails.User Response: Correct the message channel agent type.

KMC0092E Your request failed. WebSphere MQ like object has wrong typeExplanation: An attempt was made to create an object based on the definition of an existing object, but the new and existing objects had different types. This can result from the incorrect definition of the WebSphere MQ default resources.System Action: Validation fails.User Response: Ensure that the IBM-provided default resources for the actual queue manager are valid.

KMC0093E Your request failed. WebSphere MQ object is open. An attempt was made to delete or change an object that was in use.Explanation: An attempt was made to delete or change an object that was in use.System Action: Processing for the current request is terminated.User Response: Wait until the object is no longer in use, then retry the operation.

KMC0097E Your request failed. WebSphere MQ object name not validExplanation: You attempted to create a new resource with an invalid name.System Action: Processing for the current request is terminated.User Response: Ensure that the name is valid for the type of object. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z

� Lowercase a-z (however, on systems using EBCDIC Katakana, you cannot use lowercase characters, and there are also restrictions on the use of lowercase letters for z/OS console support).

� Numerics 0-9

� Period (.)

� Forward slash (/)

� Underscore (_)

� Percent sign (%). The percent sign (%) is a special character to RACF.

If you are using RACF as the external security manager for WebSphere MQ for z/OS, you should not use % in object names. If you do, these names are not included in any security checks when using RACF generic profiles.

KMC0098E Your request failed. WebSphere MQ allocation failed. An attempt to allocate a conversation to a remote system failedExplanation: WebSphere MQ attempted to allocate a conversation to a remote system failed. The error may be due to an invalid entry in the channel definition, or it may be that the listening program at the remote system is not running.System Action: Processing for the current request is terminated.User Response: Ensure that the channel definition is correct, and start the listening program if necessary. If the error persists, consult your WebSphere MQ systems administrator.

KMC Messages


KMC0099E Your request failed. WebSphere MQ remote system not availableExplanation: WebSphere MQ’s attempt to allocate a conversation to a remote system was unsuccessful. The error may be transitory, and the allocation may succeed later. This reason can occur if the listening program at the remote system is not running.System Action: Processing for the current request is terminated.User Response: Ensure that the listening program is running, and retry the operation.

KMC0100E Your request failed. WebSphere MQ channel configuration errorExplanation: A configuration error was detected in the channel definition or communication subsystem, and allocation of a conversation was not possible. This may be caused by one of the following:

� For LU 6.2, either the ModeName or the TpName is incorrect. The ModeName must match that on the remote system, and the TpName must be specified. (On OS/400, these are held in the communications Side Object.)

� For LU 6.2, the session may not be established.

� For TCP, the ConnectionName in the channel definition cannot be resolved to a network address. This may be because the name has not been correctly specified, or because the name server is not available. The requested communications protocol may not be supported on the platform.

System Action: Processing for the current request is terminated.User Response: Identify the error and take appropriate action.

KMC0101E Your request failed. WebSphere MQ connection refusedExplanation: The attempt by WebSphere MQ to establish a connection to a remote system was rejected. The remote system might not be configured to allow a connection from this system.

� For LU 6.2 either the user ID or the password supplied to the remote system is incorrect.

� For TCP the remote system may not recognize the local system as valid, or the TCP listener program may not be started.

System Action: Processing for the current request is terminated.User Response: Correct the error or restart the listener program.

KMC0102E Your request failed. WebSphere MQ connection name invalidExplanation: The connection name in the channel definition could not be resolved into a network address. Either the name server does not contain the entry, or the name server was not available.System Action: Processing for the current request is terminated.User Response: Ensure that the connection name is correctly specified and that the name server is available.

Messages 177

KMC Messages

KMC0103E Your request failed. WebSphere MQ send failedExplanation: An error occurred while WebSphere MQ was sending data to a remote system. This may be caused by a communications failure.System Action: Processing for the current request is terminated.User Response: Consult your WebSphere MQ systems administrator.

KMC0104E Your request failed. WebSphere MQ received data errorExplanation: An error occurred while receiving data from a remote system. This may be caused by a communications failure.System Action: Processing for the current request is terminated.User Response: Consult your WebSphere MQ systems administrator.

KMC0107E Your request failed. Insufficient WebSphere MQ storage availableExplanation: Insufficient storage is available for WebSphere MQ.System Action: Processing for the current request is terminated.User Response: Consult your WebSphere MQ systems administrator.

KMC0108E Your request failed. Communication manager not available for WebSphere MQExplanation: The WebSphere MQ communications subsystem is not available.System Action: Processing for the current request is terminated.User Response: Ensure that the WebSphere MQ communications subsystem has been started.

KMC0109E Your request failed. WebSphere MQ bind failedExplanation: The bind to a remote system by WebSphere MQ during session negotiation has failed.System Action: Processing for the current request is terminated.User Response: Consult your WebSphere MQ systems administrator.

KMC0110E Your request failed. WebSphere MQ channel in-doubtExplanation: The requested operation cannot complete because the WebSphere MQ channel is in doubt.System Action: Processing for the current request is terminated.User Response: Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or resolve the channel.

KMC0111E Your request failed. WebSphere MQ channel in useExplanation: An attempt was made to perform an operation on a WebSphere MQ channel, but the channel is currently active.System Action: Processing for the current request is terminated.User Response: Stop the channel or wait for it to terminate, then retry the operation.

KMC0112E Your request failed. WebSphere MQ channel not foundExplanation: You attempted an operation on a WebSphere MQ channel, but the channel does not exist in the actual configuration.System Action: Processing for the current request is terminated.

KMC Messages


User Response: Use the Update defined from Actual menu option to create the channel in the actual configuration, then retry the original operation.

KMC0113E Your request failed. Unknown remote WebSphere MQ channelExplanation: There is no definition of the referenced channel at the remote system.System Action: Processing for the current request is terminated.User Response: Ensure that the local channel is correctly defined. If it is, add an appropriate channel definition at the remote system.

KMC0114E Your request failed. Remote WebSphere MQ queue manager not availableExplanation: The channel cannot be started because the remote queue manager is not available.System Action: Processing for the current request is terminated.User Response: Start the remote queue manager; then retry the operation.

KMC0115E Your request failed. Remote WebSphere MQ queue manager terminatingExplanation: The channel is ending because the remote queue manager is terminating.System Action: Processing for the current request is terminated.User Response: Restart the remote queue manager; then retry the operation.

KMC0117E Your request failed. WebSphere MQ queue is not a transmission queueExplanation: The queue specified in the channel definition is not a transmission queue.System Action: Processing for the current request is terminated.User Response: Ensure that the queue is specified correctly in the channel definition and that it is correctly defined to the queue manager. Retry the operation.

KMC0120E Your request failed. WebSphere MQ channel name invalidExplanation: You attempted to create a new channel with an invalid name.System Action: Processing for the current request is terminated.User Response: Ensure that the channel name is valid for the type of object. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z

� Lowercase a-z (however, on systems using EBCDIC Katakana you cannot use lowercase characters, and there are also restrictions on the use of lowercase letters for z/OS console support).

� Numerics 0-9

� Period (.)


� Underscore (_)


Messages 179

KMC Messages

If you are using RACF as the external security manager for WebSphere MQ for z/OS, you should not use % in object names. If you do, these names are not included in any security checks when RACF generic profiles are used.

KMC0121E Your request failed. WebSphere MQ transmission queue name invalidExplanation: You specified an invalid transmit queue name for this channel.System Action: Validation fails.User Response: Ensure the queue name is valid for the type of object. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0123E Your request failed. WebSphere MQ channel send exit name invalidExplanation: The send exit name specified for the channel contained characters that are not allowed for program names on the platform in question.System Action: Validation fails.User Response: Specify a valid name for the send exit. The format and maximum length of the name depends on the environment:� On Windows, it is of the form dllname(functionname), where dllname is

specified without the suffix (".DLL). The maximum length of the string is 128 characters.

� On OS/400, it is of the form progname libname, where progname occupies the first 10 characters, and libname the second 10 characters (both blank-padded to the right if necessary). The maximum length of the string is 20 characters.

� On z/OS, it is a load module name, maximum length 8 characters (128 characters are allowed for exit names for client-connection channels).

KMC0124E Your request failed. WebSphere MQ channel security exit name invalidExplanation: The Security exit name specified for the channel contained characters that are not allowed for program names on the platform in question.System Action: Validation fails.User Response: Specify a valid name for the security exit. The format and maximum length of the name depends on the environment:

KMC Messages


� On Windows it is of the form dllname(functionname), where dllname is specified without the suffix (".DLL). The maximum length of the string is 128 characters.



KMC0125E Your request failed. WebSphere MQ channel message exit name invalidExplanation: The Message exit name specified for the channel contained characters that are not allowed for program names on the platform in question.System Action: Validation fails.User Response: Specify a valid name for the message exit. The format and maximum length of the name depends on the environment:� On Windows it is of the form dllname(functionname), where dllname is




KMC0126E Your request failed. WebSphere MQ channel receive exit name invalidExplanation: The Receive exit name specified for the channel contained characters that are not allowed for program names on the platform in question.System Action: Validation fails.User Response: Specify a valid name for the receive exit. The format and maximum length of the name depends on the environment:� On Windows it is of the form dllname(functionname), where dllname is




KMC0135E Your request failed. Missing WebSphere MQ connection nameExplanation: The Connection Name property is required for sender or requester channel types, but is not present.

Messages 181

KMC Messages

System Action: Validation fails.User Response: Specify the Connection Name for the channel.

KMC0136E Your request failed. WebSphere MQ connection name invalidExplanation: The Connection Name property contains one or more blanks at the start of the name.System Action: Validation fails.User Response: Specify a valid connection name for the channel. The value you specify depends on the transport type (TRPTYPE) to be used:For tranport type LU 6.2� On z/OS, there are two forms in which to specify the value:

– Logical unit name—the logical unit information for the queue manager, comprising the logical unit name, TP name, and optional mode name. This can be specified in one of three forms, as shown in these examples:

luname: IGY12355luname/TPname: IGY12345/APINGluname/TPname/modename: IGY12345/APINGD/#INTER

When using this form, the TP name and mode name must be specified for the TPNAME and MODENAME attributes; otherwise these attributes must be blank.

– Symbolic name—The symbolic destination name for the logical unit information for the queue manager, as defined in the side information data set. The TPNAME and MODENAME attributes must be blank.

Note: For cluster-receiver channels, the side information is on the other queue managers in the cluster. Alternatively, in this case it can be a name that a channel auto-definition exit can resolve into the appropriate logical unit information for the local queue manager.

� On OS/400, Windows, and UNIX systems, this is the name of the CPI-C communications side object or, if the TPNAME is not blank, this is the fully qualified name of the partner logical unit. See the information about configuration parameters for an LU 6.2 connection for your platform in the WebSphere MQ Intercommunication manual for more information.

For transport type NetBIOS specify a unique NetBIOS name (limited to 16 characters). If you are using any of the special characters in your connection name (for example, parentheses) you must enclose the string in single quotes.For transport type SPX specify the 4-byte network address, the 6-byte node address, and the 2-byte socket number. These values must be entered in hexadecimal, with a period separating the network and node addresses. The socket number must be enclosed in brackets. Example: CONNAME('0a0b0c0d.804abcde23a1(5e86)')

If the socket number is omitted, the WebSphere MQ default value (X'5e86') is assumed.

KMC Messages


For transport type TCP specify either the host name or the network address of the remote machine (or the local machine for cluster-receiver channels). This can be followed by an optional port number, enclosed in parentheses.This parameter is required for channels with a channel type (CHLTYPE) of SDR, RQSTR, CLNTCONN, CLUSSDR, and CLUSRCVR. It is optional for SVR channels, and is not valid for RCVR or SVRCONN channels.

KMC0137E Your request failed. WebSphere MQ MQSET failedExplanation: WebSphere MQ MQSET call failed.System Action: The current request is terminated.User Response: Check whether the queue manager is active.

KMC0138E Your request failed. WebSphere MQ channel not activeExplanation: An attempt was made to stop a WebSphere MQ channel, but the channel was already stopped.System Action: Processing continues.User Response: None.

KMC0139E Your request failed. WebSphere MQ channel terminated by security exitExplanation: A channel security exit terminated the WebSphere MQ channel.System Action: The current request is terminated.User Response: Check that the channel is attempting to connect to the correct queue manager, and if so that the security exit is specified correctly, and is working correctly, at both ends.

KMC0141E Your request failed. WebSphere MQ cell directory not availableExplanation: The Scope property of the queue is to be CELL, but no name service supporting a cell directory has been configured.System Action: The current request is terminated.User Response: Configure the queue manager with a suitable name service.

KMC0142E Your request failed. WebSphere MQ message retry count not validExplanation: The message retry count specified for the channel is not valid.System Action: Validation fails.User Response: Correct the message retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0144E Your request failed. WebSphere MQ message retry exit name invalidExplanation: The message retry exit name specified for the channel contained characters that are not allowed for program names on the platform in question.System Action: Validation fails.User Response: Specify a valid name for the receive exit. The format and maximum length of the name depends on the environment:� On Windows, it is of the form dllname(functionname), where dllname is


Messages 183

KMC Messages



KMC0146E Your request failed. WebSphere MQ message retry interval invalidExplanation: The message retry interval specified for the channel is not valid.System Action: Validation fails.User Response: Correct the message retry interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0148E Your request failed. WebSphere MQ cluster queue cannot be a transmission queueExplanation: WebSphere MQ rejected the request because it would have resulted in a cluster queue also being a transmission queue. This is not supported.System Action: The current request fails.

KMC0149E Your request failed. WebSphere MQ ClusterName and ClusterNamelist attributes conflictExplanation: The request was rejected because it would have resulted in the Cluster Name property and the Cluster Namelist property both being nonblank. At least one of these properties must be blank.System Action: The current request fails.User Response: Specify either a blank Cluster Name, or a blank Cluster Namelist for the object.

KMC0150E Your request failed. WebSphere MQ Channel Status not foundExplanation: You attempted to view the status of a WebSphere MQ channel; however, no channel status is available for the specified channel. This may indicate that the channel has not been used.System Action: The current request fails.User Response: No action is required unless this is unexpected, in which case consult your WebSphere MQ systems administrator.

KMC0151E You cannot move cluster managed object object into a non-cluster managed object targetExplanation: You are attempting to move cluster-generated object object into non-cluster-generated object target. This is not supported.System Action: The current request fails.User Response: You can move a cluster-generated object only into another cluster-generated object.

KMC0152E Your request failed. WebSphere MQ Queue contains one or more messages or uncommitted put or get requestsExplanation: You attempted to delete an WebSphere MQ queue that is not empty.

KMC Messages


System Action: The current request fails.User Response: Ensure that the queue you wish to delete does not contain any messages. Retry the request.

KMC0153E The Queue Manager is already a member of this clusterExplanation: You have attempted to make a queue manager participate in a managed cluster by dragging and dropping the queue manager to the cluster. However, the queue manager in question is already participating in the cluster.System Action: The current request fails.User Response: None.

KMC0154E The Configuration Manager detected a conflict in the definition of two or more cluster queuesExplanation: While attempting to merge the attributes from the new cluster queue with the existing cluster queue conflicting attributes were found.System Action: The current request fails.User Response: Review the attributes defined for each queue, and adjust any conflicting atributes.

KMC0155E This Queue Manager is not at the proper WebSphere MQ version to support cluster participationExplanation: You have attempted to make a queue manager participate in a managed cluster by dragging and dropping the queue manager to the cluster. However, the queue manager in question is not at the proper WebSphere MQ version to support clustering. For a queue manager to participate in a cluster, it must be at least at version 5.1 (distributed platforms) or 2.1 (z/OS).System Action: The current request fails.User Response: Upgrade the WebSphere MQ software to the proper version.

KMC0156E You cannot delete queue manager manager because is it still activeExplanation: You are attempting to delete an actual Queue Manager. However, the Queue Manager cannot be deleted because it is still active.System Action: The current request fails.User Response: To stop the queue manager, select the Action option on the pop-up menu for the queue manager, and then select the Stop option. Retry the delete request once the queue manager has been successfully stopped.

KMC0157E The configuration agent was unable to delete queue manager managerExplanation: You are attempting to delete an actual queue manager; however, the OMEGAMON configuration agent cannot delete the queue manager.System Action: The current request fails.User Response: Examine the agent and CMS log files to determine why the queue manager could not be deleted.System Action: The current request fails.

KMC0158E You cannot delete an actual queue manager on this platformExplanation: You are attempting to delete an actual queue manager on a platform on which queue manager deletion is not supported.

Messages 185

KMC Messages

System Action: The current request fails.User Response: None.

KMC0159E The actual queue manager does not existExplanation: You are attempting to delete an actual queue manager; however, the actual queue manager does not exist.System Action: The current request fails.User Response: None.

KMC0160E You cannot stop the queue manager because there are pending configuration requestsExplanation: You are attempting to stop a queue manager; however, the agent currently has pending configuration requests with the queue manager.System Action: The current request fails.User Response: Wait until all pending configuration requests have completed with this queue manager; then retry the request.

KMC0161E You cannot stop an indirectly-connected queue managerExplanation: You are attempting to stop a queue manager that is defined as an indirect connection; this is not supported.System Action: The current request fails.User Response: You must manually stop an indirectly connected queue manager.

KMC0162E The queue manager is not activeExplanation: You are attempting to stop a queue manager; however, the queue manager is not currently active.System Action: The current request is ignored.User Response: None.

KMC0163E Your request to stop the queue manager failedExplanation: You are attempting to stop a queue manager; however, the OMEGAMON configuration agent cannot stop the queue manager.System Action: The current request fails.User Response: Examine the agent and CMS log files to determine why the queue manager could not be stopped.

KMC0164W The WebSphere MQ queue manager is already runningExplanation: You are attempting to start a queue manager; however, the queue manager is already active.System Action: The current request is ignored.User Response: None.

KMC0165E An invalid action code was detected by the configuration agentExplanation: The Configuration Manager sent an unsupported action request to the OMEGAMON configuration agent.System Action: The current request fails.User Response: Collect the agent and CMS log files, and contact IBM Software Support.

KMC Messages


KMC0166E A failure occurred in the WebSphere MQ DSPMQFLS commandExplanation: The OMEGAMON configuration agent issued the WebSphere MQ DSPMQFLS command to obtain the name of the authorization file for the object; however, the DSPMQFLS command failed.System Action: The current request fails.User Response: Determine why the DSPMQFLS command failed by examining the agent and CMS log files. If the problem persists, contact IBM Software Support.

KMC0167E The configuration agent was unable to find the authorization file name in the output from DSPMQFLSExplanation: The OMEGAMON configuration agent issued the WebSphere MQ DSPMQFLS command to obtain the name of the authorization file for the object; however, the agent was unable to determine the name of the authorization file from the output from DSPMQFLS.System Action: The current request fails.User Response: Investigate why the DSPMQFLS command failed by examining the agent and CMS log files. It may be necessary to manually enter the DSPMQFLS command and view the output. If the problem persists, contact IBM Software Support.

KMC0168E The WebSphere MQ authorization filename as reported by DSPMQFLS is in an incorrect formatExplanation: The OMEGAMON configuration agent issued the WebSphere MQ DSPMQFLS command to obtain the name of the authorization file for the object; however, the file name as reported by DSPMQFLS is in an incorrect format, and cannot be located.System Action: The current request fails.User Response: Investigate why the DSPMQFLS command failed by examining the agent and CMS log files. It may be necessary to manually enter the DSPMQFLS command and view the output. If the problem persists, contact IBM Software Support.

KMC0169E The configuration agent was unable to open the WebSphere MQ authorization fileExplanation: The OMEGAMON configuration agent was unable to open the WebSphere MQ authorization file for the object in question.System Action: The current request fails.User Response: Ensure the authorization file for the WebSphere MQ object exists and that the OMEGAMON configuration agent has read access to this file. Review the topic "Authorization Files" in the appropriate WebSphere MQ system administration guide for more information.

KMC0170E The WebSphere MQ authorization file is in an incorrect formatExplanation: The OMEGAMON configuration agent attempted to read the WebSphere MQ authorization file for the object in order to determine the object's authorization properties; however, the authorization file is in an incorrect format.System Action: The current request fails.

Messages 187

KMC Messages

User Response: Ensure that the authorization file for the WebSphere MQ object is in the correct. Review the topic "Authorization Files" in the appropriate WebSphere MQ system administration guide for more information. If the problem persists, contact IBM Software Support.

KMC0171E WebSphere MQ authorization configuration is not supported on this platformExplanation: You attempted to configure authorization properties for a queue manager that is running on a platform for which authorization properties are not supported. Currently, authorization properties are only supported on Windows, UNIX, OS/400, and HP NonStop Kernel platforms.System Action: The current request fails.User Response: Deselect the Configure WebSphere MQ authorization option on the autostart page of the queue manager settings.

KMC0172E An error occurred processing the SETMQAUT commandExplanation: The OMEGAMON configuration agent issued the WebSphere MQ SETMQAUT command to modify the authorization properties of the object; however, the SETMQAUT command failed.System Action: The current request fails.User Response: Investigate why the SETMQAUT command failed by examining the agent and CMS log files. If the problem persists, contact IBM Software Support.

KMC0173E An authorization principal or group name was invalidExplanation: The authorization page for the object specified the name of a principal or group which does not exist.System Action: The current request fails.User Response: Correct the authorization page for the object, and retry the request.

KMC0174E An invalid WebSphere MQ command argument was detectedExplanation: The OMEGAMON configuration agent passed a bad argument to the SETMQAUT command.System Action: The current request fails.User Response: Collect the agent and CMS log files, and contact IBM Software Support.

KMC0175E An unexpected error occurred on a SETMQAUT commandExplanation: An internal WebSphere MQ error occurred while processing the SETMQAUT command.System Action: The current request fails.User Response: Attempt to enter the SETMQAUT command manually for the object. If the problem persists, contact IBM Software Support.

KMC0176E The queue manager has insufficient disk space to process WebSphere MQ commandExplanation: The WebSphere MQ SETMQAUT command cannot be completed due to shortage of disk space.

KMC Messages


System Action: The current request fails.User Response: Make more disk space available to WebSphere MQ.

KMC0177E The WebSphere MQ authorization file has a bad stanza - SETMQAUT could not be processedExplanation: The WebSphere MQ SETMQAUT command failed because the authority file contains an authority stanza that is not valid.System Action: The current request fails.User Response: Correct the contents of the incorrect authorization file by editing it. Review the topic "Authorization Files" in the appropriate WebSphere MQ system administration guide for more information.

KMC0178E The configuration agent has insufficient authority to process the SETMQAUT commandExplanation: The OMEGAMON configuration agent does not have the proper authority to issue the SETMQAUT command for the object.System Action: The current request fails.User Response: Ensure that the OMEGAMON configuration agent is running with sufficient authority to issue the SETMQAUT command.

KMC0179E Your request failed. The configuration agent has reached the maximum number of queue manager connections on this platform typeExplanation: You issued a request that would have caused the OMEGAMON configuration agent to connect with a queue manager; however, the agent is already connected to the maximum number of queue managers allowed for the platform—on HP NonStop Kernel and OS/400, only one queue manager.System Action: The current request fails.User Response: Restart the OMEGAMON configuration agent, and retry the request.

KMC0180E WebSphere MQ namelists are not supported on this platformExplanation: You attempted to create a new IBM Software Support namelist; however, namelists are not supported on this platform or WebSphere MQ version. Namelists are supported on:� queue managers running on z/OS

� queue managers running on distributed systems at version 5.1 of WebSphere MQ.

System Action: The current request fails.User Response: Delete the defined namelist objects, or upgrade to a version of WebSphere MQ that supports namelists.

KMC0181E WebSphere MQ storage classes are not supported on this platformExplanation: You attempted to create a new WebSphere MQ storage class; however, storage classes are not supported on this platform. Storage classes are supported on z/OS only.System Action: The current request fails.User Response: Delete the defined storage class objects.

Messages 189

KMC Messages

KMC0182E Your request failed. The configuration agent was unable to create the Queue ManagerExplanation: You attempted to create a new actual queue manager; however, the CRTMQM command issued by the OMEGAMON configuration agent failed.System Action: The current request fails.User Response: Investigate why the CRTMQM command failed by examining the agent and CMS log files. If necessary, issue the CRTMQM command manually. If the problem persists, contact IBM Software Support.

KMC0183E Your request failed. The configuration agent was unable to start the Queue ManagerExplanation: You attempted to start a queue manager; however, the STRMQM command issued by the OMEGAMON configuration agent failed.System Action: The current request fails.User Response: Investigate why the STRMQM command failed by examining the agent and CMS log files. If necessary, issue the STRMQM command manually. If the problem persists, contact IBM Software Support.

KMC0184E Your request failed. The configuration agent was unable to start the WebSphere MQ Command ServerExplanation: You attempted to start a queue manager; however, the STRMQCSV command issued by the OMEGAMON configuration agent failed.System Action: The current request fails.User Response: Investigate why the STRMQCSV command failed by examining the agent and CMS log files. If necessary, issue the STRMQCSV command manually. If the problem persists, contact IBM Software Support.

KMC0185E Your request failed. The configuration agent was unable to connect with the Queue ManagerExplanation: The OMEGAMON configuration agent attempted to connect with the queue manager; however, the MQCONN request failed.System Action: The current request fails.User Response: If you were attempting to create a new queue manager by performing the Update actual from defined operation, ensure that the Auto create check box is selected (in the Auto create section of the queue manager settings). Otherwise, investigate why the MQCONN failed by examining the agent and CMS log files. If the problem persists, contact IBM Software Support.

KMC0186E Your request failed. The configuration agent was unable to create the IBM default resources on the Queue ManagerExplanation: You attempted to create a new actual queue manager; however, the OMEGAMON configuration agent was unable to create the IBM-provided default resources.System Action: The current request fails.User Response: Investigate why the agent was unable to create the IBM default resources by examining the agent and CMS log files. If necessary, create the default resources manually. If the problem persists, contact IBM Software Support.

KMC Messages


KMC0187E Your request failed. The configuration agent was unable to open the WebSphere MQ reply-to queueExplanation: The OMEGAMON configuration agent attempted to connect with the queue manager; however, the agent was unable to open the reply-to queue used to communicate with the WebSphere MQ command server.System Action: The current request fails.User Response: Investigate why the agent was unable to open the queue by examining the agent and CMS log files. If the problem persists, contact IBM Software Support.

KMC0188E Your request failed. The configuration agent was unable to open the WebSphere MQ command queueExplanation: The OMEGAMON configuration agent attempted to connect with the queue manager; however, the agent was unable to open the WebSphere MQ command queue used to communicate with the WebSphere MQ command server. This can be caused by the definition for SYSTEM.ADMIN.COMMAND.QUEUE.System Action: The current request fails.User Response: Investigate why the agent was unable to open the queue by examining the agent and CMS log files. Check the definition of SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COMMAND.INPUT (for z/OS). If the problem persists, contact IBM Software Support.

KMC0189E Your request failed. The configuration agent was unable to perform an MQINQ request for the WebSphere MQ command queueExplanation: The OMEGAMON configuration agent attempted to connect with the queue manager; however, the agent was unable to perform an MQINQ request against the WebSphere MQ command queue used to communicate with the WebSphere MQ command server. This can be caused by the definition of the SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or the SYSTEM.COMMAND.INPUT queue (for z/OS).System Action: The current request fails.User Response: Investigate why the agent was unable to perform an MQINQ against the queue by examining the agent and CMS log files. Check the definition of SYSTEM.ADMIN.COMMAND.QUEUE (for distributed platforms) or SYSTEM.COMMAND.INPUT (for z/OS). If the problem persists, contact IBM Software Support.

KMC0190E Your request failed. The configuration agent cannot communicate with the Queue Manager because the command server is not activeExplanation: The OMEGAMON configuration agent attempted to connect with the queue manager; however, the agent determined that the WebSphere MQ command server is not currently active.System Action: The current request fails.User Response: Manually start the WebSphere MQ command server by issuing the STRMQCSV command on the target system. Retry the request.

Messages 191

KMC Messages

KMC0191E Your request failed. The configuration agent could not establish communication with the remote WebSphere MQ queue managerExplanation: The OMEGAMON configuration agent attempted to connect with an indirectly connected queue manager; however, the agent did not receive a response from the queue manager.System Action: The current request fails.User Response: Ensure that the indirectly connected queue manager is active, and that all channels used for bidirectional communication with the pass-through queue manager are running. Check the definitions of all channels, transmit queues, and (if specified) remote queues.

KMC0192E WebSphere MQ processes are not supported on this platformExplanation: You attempted to create an actual WebSphere MQ process; however, processes are not supported on this platform or WebSphere MQ version. Processes are not supported on WebSphere MQ Version 2.1 for Windows.System Action: The current request fails.User Response: Delete the defined process objects.

KMC0193E WebSphere MQ server connection channels are not supported on this platformExplanation: You attempted to create an actual WebSphere MQ server connection channel; however, server connection channels are not supported on this platform or WebSphere MQ version. Server connection channels are not supported on WebSphere MQ Version 2.1 for Windows.System Action: The current request fails.User Response: Delete the defined server connection channel objects.

KMC0194E Your request failed. The configuration agent is unable to create the queue manager with this version of WebSphere MQExplanation: You attempted to create an actual queue manager; however, queue manager creation is not supported on this platform or WebSphere MQ version. The OMEGAMON configuration agent cannot create queue managers on z/OS or on WebSphere MQ Version 2.1 for Windows.System Action: The current request fails.User Response: Create the queue manager manually.

KMC0195E Your request failed. The configuration agent is unable to start the queue manager with this version of WebSphere MQExplanation: You attempted to start a queue manager; however, queue manager start is not supported on this platform or WebSphere MQ version. The OMEGAMON configuration agent cannot start queue managers on z/OS or on WebSphere MQ Version 2.1 for Windows.System Action: The current request fails.User Response: Start the queue manager manually.

KMC Messages


KMC0196E Cluster sender channels are not supported on this version of WebSphere MQExplanation: You attempted to create an actual cluster sender channel. However, the queue manager in question is not at the proper WebSphere MQ version to support clustering. For a queue manager to participate in a cluster, WebSphere MQ must be at least at the 5.1 version (for distributed platforms) or the 2.1 version (for z/OS).System Action: The current request fails.User Response: Upgrade the WebSphere MQ software to the proper version.

KMC0197E Cluster receiver channels not supported on this version of WebSphere MQExplanation: You attempted to create an actual cluster receiver channel; however, the queue manager in question is not at the proper WebSphere MQ version to support clustering. For a queue manager to participate in a cluster, WebSphere MQ must be at least at the 5.1 version (for distributed platforms) or the 2.1 version (for z/OS).System Action: The current request fails.User Response: Upgrade the WebSphere MQ software to the proper version.

KMC0198E The configuration object contains an undefined attribute attribute = valueExplanation: The property indicated by attribute having value value was found in the definition of this configuration object. This property is unsupported.System Action: The current request fails.User Response: Collect the CMS log files and contact IBM Software Support.

KMC0199E The WebSphere MQ object contains an invalid queue name queueExplanation: The queue name that you specified for this object is not a valid WebSphere MQ queue name.System Action: The current request fails.User Response: Ensure that the queue name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



Messages 193

KMC Messages

KMC0200E The WebSphere MQ object contains an invalid Queue Manager name managerExplanation: The queue manager name that you specified for this object is not a valid WebSphere MQ queue manager name.System Action: The current request fails.User Response: Ensure that the queue manager name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0201E The WebSphere MQ object contains an invalid channel name channelExplanation: The channel name that you specified for this object is not a valid WebSphere MQ channel name.System Action: The current request fails.User Response: Ensure that the channel name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC Messages


KMC0202E The WebSphere MQ object contains an invalid process name processExplanation: The process name that you specified for this object is not a valid WebSphere MQ process name.System Action: The current request fails.User Response: Ensure that the process name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0203E The WebSphere MQ object contains an invalid namelist name namelistExplanation: The namelist name you specified for this object is not a valid WebSphere MQ namelist name.System Action: The current request fails.User Response: Ensure that the namelist name is valid. The character set for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0204E The contents of the namelist are invalidExplanation: The namelist contents contain one or more invalid entries.System Action: The current request fails.

Messages 195

KMC Messages

User Response: Ensure that the namelist contents are valid. Each entry in the contents must contain a valid WebSphere MQ name. The character set for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0205E The through queue manager field field is not defined in the configurationExplanation: You have selected the Indirect connection option for the queue manager; however, the Through Queue Manager name is not defined anywhere in the configuration.System Action: The current request fails.User Response: Correct the Through Queue Manager field.

KMC0206E The exit name exit associated with this object is invalidExplanation: You have specified an invalid exit name for the object.System Action: The current request fails.User Response: Specify a valid name for the exit. The format and maximum length of the name depends on the environment:� On Windows, it is of the form dllname(functionname), where dllname is




KMC0207E The connection name connection associated with this object is invalidExplanation: You specified an invalid connection name for the channel.System Action: The current request fails.User Response: Specify a valid connection name for the channel. The value you specify depends on the transport type (TRPTYPE) to be used:For tranport type LU 6.2

KMC Messages


� On z/OS, there are two forms in which to specify the value:

– Logical unit name—the logical unit information for the queue manager, comprising the logical unit name, TP name, and optional mode name. This can be specified in one of three forms, as shown in these examples:

luname: IGY12355luname/TPname: IGY12345/APINGluname/TPname/modename: IGY12345/APINGD/#INTER

When using this form, the TP name and mode name must be specified for the TPNAME and MODENAME attributes; otherwise these attributes must be blank.

– Symbolic name—The symbolic destination name for the logical unit information for the queue manager, as defined in the side information data set. The TPNAME and MODENAME attributes must be blank.

Note: For cluster-receiver channels, the side information is on the other queue managers in the cluster. Alternatively, in this case it can be a name that a channel auto-definition exit can resolve into the appropriate logical unit information for the local queue manager.

� On OS/400, Windows, and UNIX systems, this is the name of the CPI-C communications side object or, if the TPNAME is not blank, this is the fully qualified name of the partner logical unit. See the information about configuration parameters for an LU 6.2 connection for your platform in the WebSphere MQ Intercommunication manual for more information.

For transport type NetBIOS specify a unique NetBIOS name (limited to 16 characters). If you are using any of the special characters in your connection name (for example, parentheses) you must enclose the string in single quotes.For transport type SPX specify the 4-byte network address, the 6-byte node address, and the 2-byte socket number. These values must be entered in hexadecimal, with a period separating the network and node addresses. The socket number must be enclosed in brackets. Example: CONNAME('0a0b0c0d.804abcde23a1(5e86)')

If the socket number is omitted, the WebSphere MQ default value (X'5e86') is assumed.For transport type TCP specify either the host name or the network address of the remote machine (or the local machine for cluster-receiver channels). This can be followed by an optional port number, enclosed in parentheses.This parameter is required for channels with a channel type (CHLTYPE) of SDR, RQSTR, CLNTCONN, CLUSSDR, and CLUSRCVR. It is optional for SVR channels, and is not valid for RCVR or SVRCONN channels.

KMC0208E The modename mode associated with this object has an invalid lengthExplanation: You specified an invalid modename for the channel.System Action: The current request fails.User Response: Specify a valid mode name for the channel. On HP NonStop Kernel, this should be set to the SNA mode name. On other platforms the mode name

Messages 197

KMC Messages

can only be set to blanks; the actual name is then taken from the CPI-C Communications Side Object, or APPC side information data set.

KMC0209E The storage class name class associated with this object has an invalid lengthExplanation: You specified an invalid storage class name for the queue.System Action: The current request fails.User Response: Specify a valid storage class name for the queue. Storage class names are restricted to a maximum of 8 characters in length.

KMC0210E The MCA user id mcaid associated with this object has an invalid lengthExplanation: You specified an invalid message channel agent userid for the channel.System Action: The current request fails.User Response: Specify a valid message channel agent user ID. Message channel agent user IDs are restricted to a maximum of 12 characters.

KMC0211E The user id userid associated with this object has an invalid lengthExplanation: You specified an invalid LU6.2 task userid for the channel.System Action: The current request fails.User Response: Specify a valid LU6.2 task user id. LU6.2 task userids are restricted to a maximum of 12 characters in length.

KMC0212E The password password associated with this object has an invalid lengthExplanation: You specified an invalid LU6.2 password for the channel.System Action: The current request fails.User Response: Specify a valid LU6.2 password. Passwords are restricted to a maximum of 12 characters in length.

KMC0213E The MCA name mca associated with this object has an invalid lengthExplanation: You specified an invalid MCANAME for the channel.System Action: The current request fails.User Response: Specify a valid MCANAME. MCANAMEs are restricted to 20 characters in length.

KMC0214E The Do not check resources prefixed with prefix associated with this object has an invalid lengthExplanation: You specified an invalid value for the Don’t check resources prefixed with property on the Validation page of the queue manager settings.System Action: The current request fails.User Response: Specify a valid value for this field. The value specified is limited to 255 characters in length.

KMC0215E The Exit user data data associated with this object has an invalid lengthExplanation: You specified invalid exit data for the channel.System Action: The current request fails.User Response: Specify valid exit data. Exit data is restricted to 32 characters in length on this version of WebSphere MQ.

KMC Messages


KMC0216E The Environmental data data associated with this object has an invalid lengthExplanation: You specified invalid environment data for the process.System Action: The current request fails.User Response: Specify a valid environment data. Environment data is restricted to a maximum of 128 characters in length.

KMC0217E The User data data associated with this object has an invalid lengthExplanation: You specified invalid user data for the process.System Action: The current request fails.User Response: Specify valid user data. User data is restricted to a maximum of 128 characters in length.

KMC0218E The Trigger data data associated with this object has an invalid lengthExplanation: You specified invalid trigger data for the queue.System Action: The current request fails.User Response: Specify valid trigger data. Trigger data is restricted to a maximum of 64 characters in length.

KMC0219E The TPNAME tpname associated with this object has an invalid lengthExplanation: You specified an invalid LU6.2 Transaction program name for the channel.System Action: The current request fails.User Response: Specify a valid LU6.2 transaction program name. On HP NonStop Kernel, this should be set to the local TP name. This can be followed by the name of the TP on the remote machine, for example: TPNAME('localtp[.remotetp]')

Both names can be up to 16 characters in length. On other platforms, this should be set to the SNA transaction program name, unless the CONNAME contains a side-object name in which case it should be set to blanks. The actual name is taken instead from the CPI-C Communications Side Object, or the APPC side information data set. See the information about configuration parameters for an LU 6.2 connection for your platform in the WebSphere MQ intercommunication manual for more information.On Windows SNA Server and in the side object on z/OS, the TPNAME is wrapped to upper case. This parameter is not valid for channels with a channel type (CHLTYPE) of RCVR.

KMC0220E The event event type is invalidExplanation: You specified an invalid event control for the queue manager.System Action: The current request fails.User Response: Specify a valid Event control.

KMC0221E The validation validation type is invalidExplanation: You specified an invalid validation control for the object.System Action: The current request fails.User Response: Specify a valid validation control.

Messages 199

KMC Messages

KMC0222E The application application type is invalidExplanation: You specified an invalid application type for the process.System Action: The current request fails.User Response: Specify a valid application type. Valid application types are:� CICS—represents a CICS® transaction.

� DOS—represents a DOS application.

� IMS—represents an IMS™ transaction.

� z/OS—represents a z/OS application (batch or TSO).

� NSK—represents an HP NonStop Kernel application.

� OS400—represents an OS/400 application.

� UNIX—represents a UNIX application.

� VMS—represents a Digital OpenVMS application.

� WINDOWS—represents a Windows application.

� WINDOWSNT—represents a Windows NT application.

KMC0223E The get inhibit type is invalidExplanation: You specified an invalid get inhibit property for the queue.System Action: The current request fails.User Response: Specify a valid get inhibit property.

KMC0224E The default open for input type is invalidExplanation: You specified an invalid default open property for the queue.System Action: The current request fails.User Response: Specify a valid default open property.

KMC0225E The syncpoint type is invalidExplanation: You specified an invalid put syncpoint property for the queue.System Action: The current request fails.User Response: Specify a valid put syncpoint property.

KMC0226E The put inhibit type is invalidExplanation: You specified an invalid put inhibit property for the queue.System Action: The current request fails.User Response: Specify a valid put inhibit property.

KMC0227E The queue definition type is invalidExplanation: You specified an invalid definition type property for the queue.System Action: The current request fails.User Response: Specify a valid definition type property.

KMC0228E The harden get backout type is invalidExplanation: You specified an invalid harden backout property for the queue.System Action: The current request fails.User Response: Specify a valid harden backout property.

KMC Messages


KMC0229E The delivery sequence type is invalidExplanation: You specified an invalid message sequence property for the queue.System Action: The current request fails.User Response: Specify a valid message sequence property.

KMC0230E The shareability type is invalidExplanation: You specified an invalid shareable property for the queue.System Action: The current request fails.User Response: Specify a valid shareable property.

KMC0231E The default persistence type is invalidExplanation: You specified an invalid default persistence property for the queue.System Action: The current request fails.User Response: Specify a valid default persistence property.

KMC0232E The service interval event type is invalidExplanation: You specified an invalid service interval milliseconds property for the queue.System Action: The current request fails.User Response: Specify a valid service interval milliseconds property.

KMC0233E The dead letter queue queue associated with the queue manager is not defined as a local queueExplanation: You defined a dead-letter queue in the queue manager definition. However, the DLQ name that you specified is not defined as a local queue within the Queue Manager's subordinate resources.System Action: The current request fails.User Response: Ensure that the name you specify as a dead-letter queue for the Queue Manager is defined as a local queue.

KMC0234E The dead letter queue queue associated with the queue manager is not defined as USAGE(NORMAL)Explanation: You defined a dead-letter queue in the queue manager definition. However, the DLQ name that you specified identifies a local queue that is defined as a Transmit queue.System Action: The current request fails.User Response: Change the usage for the dead-letter queue to normal, or identify a different dead-letter queue for the queue manager.

KMC0235W One or more IBM standard WebSphere MQ resources are not defined name1 name2 name3 name4Explanation: At least one of the default IBM-provided resources that should be associated with the queue manager are not present in the defined configuration. Up to four of the missing resource names are displayed.System Action: The current request fails.

Messages 201

KMC Messages

User Response: This message is only a warning. If these resources are not defined at the time of an Update Actual from Defined or Update Defined from Actual request against the queue manager, they will be added dynamically into the defined configuration by copying the definitions from the actual queue manager.

KMC0236E The default transmit queue queue is not defined as a local queue within the queue managerExplanation: You defined a default transmit queue in the queue manager definition. However, the queue name that you specified is not defined as a local queue within the queue manager's subordinate resources.System Action: The current request fails.User Response: Ensure that the name you specify as a default transmit queue for the queue manager is defined as a local queue.

KMC0237E The default transmit queue queue is not defined as USAGE(XMITQ)Explanation: You defined a default transmit queue in the queue manager definition. However, the DLQ name that you specified identifies a local queue that is defined with Usage Normal.System Action: The current request fails.User Response: Change the usage for the default transmit queue to Transmit queue, or identify a different default transmit queue for the queue manager.

KMC0238E The trigger process process associated with the queue is not defined within queue managerExplanation: Triggering is enabled for the queue. However the defined trigger process name associated with the queue is not defined within the queue manager.System Action: The current request fails.User Response: Either disable triggering for the queue, or ensure that the process name property identifies a process that is defined within the queue manager.

KMC0239E Triggering is enabled for the queue but the initiation queue is not specifiedExplanation: Triggering is enabled for the queue. However, you did not specify the name of an Initiation queue.System Action: The current request fails.User Response: Either disable triggering for the queue, or identify the name of a local queue defined on the queue manager which is to be used as the initiation queue.

KMC0240E The initiation queue queue has the same name as the queue nameExplanation: Triggering is enabled for the queue. However, you specified the name of the queue as the initiation queue. This is not supported.System Action: The current request fails.User Response: Either disable triggering for the queue, or identify another local queue defined on the queue manager to be used as the initiation queue.

KMC Messages


KMC0241W The queue is defined as a transmit queue but it is not referenced by a channel within the Queue ManagerExplanation: The local transmit queue will not be used because there are no sender or server channels defined in the queue manager that reference this queue as a transmit queue.System Action: The current request fails.User Response: This message is only a warning. You can stop the message from appearing by either specifying Usage=Normal for the queue, or by specifying the name of the queue as the transmit queue name for a sender or server channel within the queue manager.

KMC0242E The transmit queue queue associated with the channel is not defined as a local queue within the queue managerExplanation: You defined a transmit queue in the remote queue definition. However, the queue name that you specified is not defined as a local queue within the queue manager's subordinate resources.System Action: The current request fails.User Response: Ensure that the name you specify as a transmit queue for the remote queue is defined as a local queue within the queue manager.

KMC0243E The transmit queue queue associated with the channel is not defined as USAGE(XMITQ)Explanation: You defined a transmit queue in the remote queue definition. However, the queue name that you specified identifies a local queue that is defined with Usage Normal.System Action: The current request fails.User Response: Change the usage for the transmit queue to Transmit, or identify a different transmit queue for the remote queue.

KMC0244E The maximum message length length associated with the queue is larger than the maximum message length associated with the queue managerExplanation: The maximum message length associated with the queue is larger than the maximum message length associated with the queue manager.System Action: The current request fails.User Response: Correct the maximum message length. On AIX, HP-UX, Solaris, and Windows, specify a value greater than or equal to zero, and less than or equal to the maximum message length for the queue manager. On other platforms, specify a value greater than 0, and less than or equal to 4,194,304.

KMC0245E The remote queue manager name not specified for the remote queueExplanation: You defined a remote queue, but the remote manager name is not specified. This property is required.System Action: The current request fails.User Response: Specify a valid WebSphere MQ name for the remote manager name. If an application opens the local definition of a remote queue, the remote queue manager must not be blank or the name of the local queue manager. When the open occurs, if the transmit queue is blank there must be a local queue of this name, which is to be used as the transmission queue. If this definition is used for a queue-

Messages 203

KMC Messages

manager alias, remote queue manager is the name of the queue manager that is being aliased. It can be the name of the local queue manager. Otherwise, if XMITQ is blank when the open occurs, there must be a local queue of this name, which is to be used as the transmission queue. If this definition is used for a reply-to alias, this name is the name of the queue manager that is to be the reply-to queue manager.

KMC0246E The remote queue queue is not defined as a local queue within the queue managerExplanation: You defined a remote queue, but the transmit queue is empty and the remote manager name does not specify the name of a local queue defined on the queue manager.System Action: The current request fails.System Action: Specify the name of a local queue defined within this queue manager which is defined with Usage=Transmit for the remote manager name. If an application opens the local definition of a remote queue, the remote Queue Manager must not be blank or the name of the local Queue Manager. When the open occurs, if the transmit queue is blank, there must be a local queue of this name, which is to be used as the transmission queue.

KMC0247E The remote queue queue is not defined as USAGE(XMITQ) within the queue managerExplanation: You defined a remote queue, but the transmit queue is empty and the remote manager name identifies a local queue which is defined with Usage=Normal.System Action: The current request fails.User Response: Specify the name of a local queue defined within this queue manager which is defined with Usage=Transmit for the remote manager name. If an application opens the local definition of a remote queue, the remote queue manager must not be blank or the name of the local queue manager. When the open occurs, if the transmit queue is blank there must be a local queue of this name, which is to be used as the transmission queue.

KMC0248W The process is not referenced by a local or model queue within the Queue ManagerExplanation: The defined process will not be used because it is not referenced as the process name by a local or model queue within the queue manager.System Action: Processing continues.User Response: This message is only a warning. You can stop the message from appearing by defining a local or model queue within the queue manager that references the process on the Triggers settings page.

KMC0249E The target queue not defined as local or remote queue within the Queue ManagerExplanation: The target queue name associated with this alias queue is not defined as a local or remote queue within the queue manager.System Action: The current request fails.User Response: Specify the name of a local or remote queue within the queue manager as the alias queue's target queue.

KMC Messages


KMC0250W The process is not referenced by a queue with triggering enabled within the Queue ManagerExplanation: The defined process will not be used because it is not referenced as the process name by a local or model queue within the queue manager that has triggering enabled.System Action: The current request fails.User Response: This message is only a warning. You can stop the message from appearing by defining a local or model queue within the queue manager that references the process on the Triggers settings page and has triggering enabled.

KMC0251E The name list contains entry entry which is not defined as a queue on the Queue ManagerExplanation: An entry on the contents of the namelist is not defined as a queue within the queue manager.System Action: The current request fails.User Response: Ensure that each entry in the namelist contents identifies the name of a queue on the queue manager.

KMC0252E The heartbeat interval interval1 is larger than disconnect interval interval2Explanation: You specified a heartbeat interval for the channel that is larger than the channel's disconnect interval.System Action: The current request fails.User Response: Correct either the heartbeat interval, or the disconnect interval. IBM recommends that you should set the heartbeat interval to be significantly less than the disconnect interval.

KMC0253E Sender/Server channel does not contain a reference to a transmit queueExplanation: You defined a sender or server channel, but the transmit queue name is not specified. This is required.System Action: The current request fails.User Response: Specify the name of a local queue defined within this queue manager which is defined with Usage=Transmit for the transmit queue name.

KMC0254E The channel references a transmit queue queue which is not defined as a local queue within the queue managerExplanation: You defined a transmit queue in the channel definition. However, the queue name that you specified is not defined as a local queue within the queue manager's subordinate resources.System Action: The current request fails.User Response: Ensure that the name you specify as a transmit queue for the channel is defined as a local queue within the queue manager.

KMC0255E The channel references a transmit queue queue which is not not defined as USAGE(XMITQ)Explanation: You defined a transmit queue in the channel definition. However, the queue name that you specified identifies a local queue that is defined with Usage Normal.System Action: The current request fails.

Messages 205

KMC Messages

User Response: Change the usage for the transmit queue to Transmit, or identify a different transmit queue for the remote queue.

KMC0256E The maximum message length of the transmit queue queue exceeds the maximum message length of the channelExplanation: You have defined a sender or server channel and its associated transmit queue. However, the maximum message of the transmit queue is larger than the maximum message length of the channel. This could result in problems if messages are put to the transmission queue which are larger than the maximum message length for the channel.System Action: The current request fails.User Response: Specify a maximum message length for the channel which is at least as large as the maximum message length for the transmit queue.

KMC0257W The connected Queue Manager manager does not existExplanation: You defined a value for the connected queue manager on the Transmit page for this channel. However, the connected queue manager does not identify a defined queue manager within the configuration.System Action: The current request fails.User Response: Either blank out the Connected Queue Manager field, or specify the name of a queue manager that is currently defined.

KMC0258W A Receiver/requester channel with the same name as this channel does not exist on the receiving queue manager managerExplanation: You defined a value for the connected queue manager on the Transmit page for this channel. However, a receiver or requester channel with the same name as this channel does not exist within the queue manager referenced by the connected queue manager. A sender or server channel must be able to communicate with a receiver or requester channel of the same name.System Action: The current request fails.User Response: Either blank out the connected queue manager field, or define a receiver or requester channel within the connected queue manager that has the same name as this channel.

KMC0259W The receiver/requester channel on queue manager manager is defined with an inconsistent transport type to this channelExplanation: You defined a value for the connected queue manager on the Transmit page for this channel. However, the corresponding receiver or requester channel defined within the connected queue manager specifies a different transport type.System Action: The current request fails.User Response: Correct the definition either of this channel or of the corresponding receiver or requester channel on the other queue manager, so that the transport types are consistent.

KMC Messages


KMC0260W The maximum message length definition for this channel is inconsistent with the receiver/requester channel on queue manager managerExplanation: You defined a value for the connected queue manager on the Transmit page for this channel. However, the corresponding receiver or requester channel defined within the connected queue manager specifies a different maximum message length.System Action: The current request fails.User Response: This message is only a warning. The maximum message length is compared with the value for the partner and the actual maximum used is the lower of the two values. To eliminate this warning message, correct the definition of either this channel, or of the channel on the connected queue manager.

KMC0261E Triggering is enabled for the queue but initiation queue queue is not foundExplanation: Triggering is enabled for the queue. However, the value that you specified as an initiation queue did not reference a local queue on this queue manager.System Action: The current request fails.User Response: Either disable triggering for the queue, or identify the name of a local queue defined on the queue manager to be used as the initiation queue.

KMC0262E The initiation queue queue associated with the queue is not USAGE(NORMAL)Explanation: Triggering is enabled for the queue. However, the value that you specified as an initiation identified a local queue defined with Usage=Transmit.System Action: The current request fails.User Response: Either disable triggering for the queue, or identify the name of a local queue defined on the queue manager with Usage=Normal which is to be used as the initiation queue.

KMC0263W The batch size associated with the channel is inconsistent with the receiver/requester channel on queue manager managerExplanation: You defined a value for the connected queue manager on the Transmit page for this channel. However, the corresponding receiver or requester channel defined within the connected queue manager specifies a different batch size.System Action: The current request fails.User Response: This message is only a warning. The maximum batch size actually used is the lowest of the following:� the batch size of the sending channel

� the batch size of the receiving channel

� the maximum number of uncommitted messages allowed at the sending queue

KMC0264E The queue depth high limit hilimit for the queue is less than the queue depth low limitExplanation: You defined a queue in which the upper queue depth threshold is less than the lower queue depth threshold.System Action: The current request fails.

Messages 207

KMC Messages

User Response: Correct the queue definition so that the upper queue depth threshold is greater than the lower queue depth threshold.

KMC0265E Namelists are not allowed on this platformExplanation: You defined a namelist object on a queue manager that does not support namelists. Namelists are only supported on:� z/OS

� distributed systems running WebSphere MQ 5.1 or greater

System Action: The current request fails.User Response: Delete the namelist definition, or upgrade your WebSphere MQ software to a version that supports namelists.

KMC0266E Storage classes are not allowed on this platformExplanation: You defined a storage class object on a queue manager that does not support storage classes. Storage classes are supported only on z/OS.System Action: The current request fails.User Response: Delete the storage class definition.

KMC0267E Invalid scope typeExplanation: You specified an invalid scope type property for the queue.System Action: The current request fails.User Response: Specify a valid scope type property.

KMC0268E Invalid trigger typeExplanation: You specified an invalid trigger type property for the queue.System Action: The current request fails.User Response: Specify a valid trigger type property.

KMC0269E Invalid queue typeExplanation: You specified an invalid queue type property for the queue.System Action: The current request fails.User Response: Specify a valid queue type property.

KMC0270E Invalid queue usageExplanation: You specified an invalid usage property for the queue.System Action: The current request fails.User Response: Specify a valid usage property.

KMC0271E Invalid data conversionExplanation: You specified an invalid convert property for the channel.System Action: The current request fails.User Response: Specify a valid convert property.

KMC0272E Invalid channel typeExplanation: You specified an invalid channel type property for the channel.System Action: The current request fails.User Response: Specify a valid channel type property.

KMC Messages


KMC0273E Invalid protocol type protocolExplanation: You specified an invalid protocol type property for the channel.System Action: The current request fails.User Response: Specify a valid protocol type property:� LU62—SNA LU 6.2

� NETBIOS—NetBIOS (supported only on Windows, though it also applies to z/OS for defining client-connection channels that will connect to servers on the platforms supporting NetBIOS).

� SPX—sequenced packet exchange (supported only on Windows, though it also applies to z/OS for defining client-connection channels that will connect to servers on the platforms supporting SPX).

� TCP—Transmission Control Protocol, a part of the TCP/IP protocol suite.

� UDP—User Datagram Protocol, a part of the TCP/IP protocol suite (supported only on AIX).

KMC0274E Invalid put authorityExplanation: You specified an invalid put authority property for the channel.System Action: The current request fails.User Response: Specify a valid put authority property.

KMC0275E Invalid autostart valueExplanation: You specified an invalid auto start property for the queue manager.System Action: The current request fails.User Response: Specify a valid auto start property.

KMC0276E Invalid indirect connection valueExplanation: You specified an invalid indirect connection property for the queue manager.System Action: The current request fails.User Response: Specify a valid indirect connection property.

KMC0277E Invalid default queue manager valueExplanation: You specified an invalid default queue manager property for the queue manager.System Action: The current request fails.User Response: Specify a valid default queue manager property.

KMC0278E Invalue autocreate valueExplanation: You specified an invalid autocreate property for the queue manager.System Action: The current request fails.User Response: Specify a valid auto create property.

KMC0279E Invalid MVS valueExplanation: You specified an invalid z/OS property for the queue manager.

Messages 209

KMC Messages

System Action: The current request fails.User Response: Specify a valid z/OS property.

KMC0280E Invalid channel autodefine valueExplanation: You specified an invalid channel autodefine property for the queue manager.System Action: The current request fails.User Response: Specify a valid channel autodefine property.

KMC0281E Invalid index typeExplanation: You specified an invalid index type property for the queue.System Action: The current request fails.User Response: Specify a valid index type property.Note: The index type can only be specified for queues defined on queue managers

running on z/OS.

KMC0282E Invalid distribution listExplanation: You specified an invalid distribution list property for the queue.System Action: The current request fails.User Response: Specify a valid distribution list property.

KMC0283E Invalid NPM speedExplanation: You specified an invalid nonpersistent delivery property for the channel.System Action: The current request fails.User Response: Specify a valid nonpersistent delivery property.

KMC0284E Invalid trigger controlExplanation: You specified an invalid trigger control property for the queue.System Action: The current request fails.User Response: Specify a valid trigger control property.

KMC0285E Invalid queue depth high value depthExplanation: You specified an invalid upper queue depth threshold for the queue.System Action: The current request fails.User Response: Specify a valid upper queue depth threshold. The value is expressed as a percentage of the maximum queue depth, and must be greater than or equal to zero, and less than or equal to 100.

KMC0286E Invalid queue depth low value depthExplanation: You specified an invalid lower queue depth threshold for the queue.System Action: The current request fails.User Response: Specify a valid lower queue depth threshold. The value is expressed as a percentage of the maximum queue depth, and must be greater than or equal to zero, and less than or equal to 100.

KMC Messages


KMC0287E Invalid maximum uncommitted messages value messagesExplanation: You specified an invalid maximum uncommitted messages value for the queue manager.System Action: The current request fails.User Response: Specify a valid maximum uncommitted messages value in the range 1 through 999,999,999.

KMC0288E Invalid disconnect interval intervalSystem Action: You specified an invalid disconnect interval for the channel.System Action: The current request fails.User Response: Specify a valid disconnect interval. The value must be greater than or equal to zero, and less than or equal to 999,999.

KMC0289E Invalid maximum priority priorityExplanation: You specified an invalid maximum priority value for the queue manager.System Action: The current request fails.User Response: Specify a valid maximum priority value. Specify a value in the range 0 through 9.

KMC0290E Invalid heartbeat interval intervalExplanation: You specified an invalid heartbeat interval for the channel.System Action: The current request fails.User Response: Specify a valid heartbeat interval. The value must be greater than or equal to zero, and less than or equal to 999,999.

KMC0291E Invalid batch interval intervalExplanation: You specified an invalid batch interval for the channel.System Action: The current request fails.User Response: Specify a valid batch interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0292E Invalid max handles value handlesExplanation: You specified an invalid maximum open handles value for the queue manager.System Action: The current request fails.User Response: Specify a valid maximum open-handles value. Do not specify a value less than zero or greater than 999,999,999.

KMC0293E Invalid trigger interval intervalExplanation: You specified an invalid trigger interval for the queue manager.System Action: The current request fails.User Response: Specify a valid trigger interval. Do not specify a value less than zero or greater than 999,999,999.

KMC0294E Invalid service interval intervalExplanation: You specified an invalid service interval for the queue.System Action: The current request fails.

Messages 211

KMC Messages

User Response: You specified an invalid service interval for the queue.

KMC0295E Invalid retention interval intervalExplanation: You specified an invalid retention interval for the queue.System Action: The current request fails.User Response: Specify a valid retention interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0296E Invalid trigger depth depthExplanation: You specified an invalid trigger depth for the queue.System Action: The current request fails.User Response: Specify a valid trigger depth. The value must be greater than zero, and less than or equal to 999,999,999.

KMC0297E Invalid long retry value retryExplanation: You specified an invalid long retry count for the channel.System Action: The current request fails.User Response: Specify a valid long retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0298E Invalid long timer value timerExplanation: You specified an invalid long retry interval for the channel.System Action: The current request fails.User Response: Specify a valid long retry interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0299E Invalid sequence number wrap value wrapExplanation: You specified an invalid sequence number wrap value for the channel.System Action: The current request fails.User Response: Specify a valid sequence number wrap value. The value must be greater than or equal to 100, and less than or equal to 999,999,999.

KMC0300E Invalid short retry value retryExplanation: You specified an invalid short retry count for the channel.System Action: The current request fails.User Response: Specify a valid short retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0301E Invalid short timer value timerExplanation: You specified an invalid short retry interval for the channel.System Action: The current request fails.User Response: Specify a valid short retry interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0302E Invalid message retry count retryExplanation: You specified an invalid message retry count for the channel.System Action: The current request fails.

KMC Messages


User Response: Specify a valid message retry count. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0303E Invalid message retry interval retryExplanation: You specified an invalid message retry interval for the channel.System Action: The current request fails.User Response: Specify a valid message retry interval. The value must be greater than or equal to zero, and less than or equal to 999,999,999.

KMC0304E Invalid backout threshold backoutExplanation: You specified an invalid backout threshold for the queue.Explanation: The current request fails.User Response: Specify a valid backout threshold. Specify a value greater than or equal to zero, and less than or equal to 999,999,999.

KMC0305E Invalid default priority priorityExplanation: You specified an invalid default message priority for the queue.System Action: The current request fails.User Response: Specify a valid default message priority. The value must be greater than or equal to zero, (the lowest priority) and less than or equal to the maximum message priority specified for the queue manager.You specified an invalid trigger message priority for the queue.

KMC0306E Invalid trigger message priority priorityExplanation: You specified an invalid trigger message priority for the queue.System Action: The current request fails.User Response: Specify a valid trigger message priority. The value must be greater than or equal to zero, (the lowest priority) and less than or equal to the maximum message priority specified for the queue manager.

KMC0307E Invalid maximum queue depth depthExplanation: You specified an invalid maximum queue depth for the queue.System Action: The current request fails.User Response: Specify a valid maximum queue depth. Specify a value greater than or equal to zero, and less than or equal to:� 999,999,999 if the queue is on z/OS/ESA.

� 640,000 if the queue is on any other WebSphere MQ platform.

KMC0308E Invalid batch size sizeExplanation: You specified an invalid batch size for the channel.System Action: The current request fails.User Response: Specify a valid batch size. The value must be greater than zero, and less than or equal to 9,999.

KMC0309E Invalid MCA typeExplanation: You specified an invalid message channel agent type for the channel.System Action: The current request fails.

Messages 213

KMC Messages

User Response: Specify a valid message channel agent type.

KMC0310E Invalid maximum message length lengthExplanation: You specified an invalid maximum message length for the queue or channel.System Action: The current request fails.User Response: Specify a valid maximum message length. On AIX, HP-UX, Solaris, and Windows, specify a value greater than or equal to zero, and less than or equal to the maximum message length for the queue manager. See the MAXMSGL parameter of the ALTER Q.

KMC0312E Invalid autostart listener valueExplanation: You specified an invalid autostart listener property for the queue manager.System Action: The current request fails.User Response: Specify a valid autostart listener property.

KMC0313E Invalid connection port portExplanation: You specified an invalid port number for the queue manager.System Action: The current request fails.User Response: Specify a valid, numeric IP port number.

KMC0314E Invalid Queue Manager autoconnect protocol protocolExplanation: You specified an invalid autoconnect protocol for the queue manager.System Action: The current request fails.User Response: Specify a valid protocol type property:� LU62—SNA LU 6.2.

� NETBIOS—NetBIOS (supported only on Windows, though it also applies to z/OS for defining client-connection channels that will connect to servers on the platforms supporting NetBIOS).

� SPX—sequenced packet exchange (supported only on Windows, though it also applies to z/OS for defining client-connection channels that will connect to servers on the platforms supporting SPX).

� TCP—Transmission Control Protocol, a part of the TCP/IP protocol suite.

� UDP—User Datagram Protocol, a part of the TCP/IP protocol suite (supported only on AIX).

KMC0315E Invalid autostart channel initiator valueExplanation: You specified an invalid start channel initiator property for the queue manager.System Action: The current request fails.User Response: Specify a valid start channel initiator property.

KMC Messages


KMC0316E Invalid autoconnect prototype resource group groupExplanation: You specified an invalid autoconnect prototype resource group for the queue manager.System Action: The current request fails.User Response: Specify a valid autoconnect prototype resource group.

KMC0317E Invalid storage class name classExplanation: You specified an invalid name for the storage class.System Action: The current request fails.User Response: Specify a valid name for the storage class. Storage class names are restricted to a maximum of 8 characters in length.

KMC0318E Invalid XCF group name groupExplanation: You specified an invalid IMS Bridge XCF Configuration Group name for the storage class.System Action: The current request fails.User Response: Specify a valid IMS Bridge XCF Configuration Group name for the storage class. IMS Bridge XCF Configuration Group names are restricted to a maximum of 8 characters in length.

KMC0319E Invalid XCF member name nameExplanation: You specified an invalid IMS Bridge XCF Configuration Member name for the storage class.System Action: The current request fails.User Response: Specify a valid IMS Bridge XCF Configuration Member name for the storage class. IMS Bridge XCF Configuration Member names are restricted to a maximum of 8 characters in length.

KMC0320E Invalid page set id pagesetExplanation: You specified an invalid page set ID for the storage class.System Action: The current request fails.User Response: Specify a valid page set ID for the storage class. The string consists of two numeric characters, in the range 00 through 99.

KMC0321E Invalid authorization eventExplanation: You specified an invalid authorization event property for the queue manager.System Action: The current request fails.User Response: Specify a valid authorization event property.

KMC0322E Invalid Dead Letter Queue queueExplanation: You specified an invalid dead-letter queue name for the queue manager.System Action: The current request fails.User Response: Specify a valid dead-letter queue name. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z

Messages 215

KMC Messages


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0323E Processes are not allowed on this version of WebSphere MQExplanation: You defined a process object on a queue manager that does not support processes. Processes cannot exist on a queue manager running WebSphere MQ 2.1 for Windows.System Action: The current request fails.User Response: Delete the process definition.

KMC0324E Server connection channels are not allowed on this version of WebSphere MQSystem Action: You defined a server connection channel on an unsupported version of WebSphere MQ. Server connection channels cannot exist on a queue manager running WebSphere MQ 2.1 for Windows.System Action: The current request fails.User Response: Delete the definition of the server connection channel.

KMC0325E The storage class name referenced by this queue is not definedExplanation: You defined a local or model queue containing a reference to a storage class. This storage class is not defined within the queue manager.System Action: The current request fails.User Response: Change the storage class definition to the name of a storage class defined within the queue manager.

KMC0326E Queue manager Log type invalidExplanation: You specified an invalid logging type property for the queue manager.System Action: The current request fails.User Response: Specify a valid logging type.

KMC0327E Number of primary logs invalid logs The value should be between 2 and 62Explanation: You specified an invalid number of primary logs for the queue manager.System Action: The current request fails.

KMC Messages


User Response: Specify a valid number of primary logs. The minimum is 2, and the maximum is 62.

KMC0328E Number of secondary logs invalid logs The value should be between 1 and 61Explanation: You specified an invalid number of secondary logs for the queue manager.System Action: The current request fails.User Response: Specify a valid number of secondary logs. The minimum is 1, and the maximum is 61.

KMC0329E Invalid log file size sizeExplanation: You specified an invalid log file size for the queue manager.System Action: The current request fails. Specify a valid log file size.

� In WebSphere MQ for UNIX, the minimum value is 64, and the maximum is 16384.

� In WebSphere MQ for Windows, the minimum value is 32, and the maximum is 4095.

KMC0330E Invalid log file path pathExplanation: You specified an invalid log file path for the queue manager.System Action: The current request fails.User Response: Specify the name of a valid file path for the platform the queue manager is to be created on.

KMC0331E Invalid default .INI file file for HP NonStop KernelExplanation: You specified an invalid default ini file for the queue manager.System Action: The current request fails.User Response: Specify a valid HP NonStop Kernel file name.

KMC0332E Invalid number of execution controllers controllers for HP NonStop Kernel The value should be between 1 and 256Explanation: You specified an invalid number of execution controllers for the queue manager.System Action: The current request fails.User Response: Specify a valid number of execution controllers. The minimum is 1, and the maximum is 256.

KMC0333E Invalid CCSID ccsid. The value should be between 1 and 65535Explanation: You specified an invalid CCSID for the queue manager.System Action: The current request fails.User Response: Specify a valid CCSID. Specify a number between 1 and the maximum number as indicated in the message text.

KMC0334E Invalid volume volume for HP NonStop KernelExplanation: You specified an invalid volume for the queue manager.System Action: The current request fails.

Messages 217

KMC Messages

User Response: Specify a valid volume. Specify a valid HP NonStop Kernel volume.

KMC0335E Invalid TS/MP PATHMON process name process for HP NonStop KernelExplanation: You specified an invalid process name for the queue manager.System Action: The current request fails.User Response: Specify a valid HP NonStop Kernel TS/MP PATHMON process name.

KMC0336E Invalid home terminal name terminal for HP NonStop KernelExplanation: You specified an invalid home terminal name for the queue manager.System Action: The current request fails.User Response: Specify a valid HP NonStop Kernel home terminal name.

KMC0337E Invalid WebSphere MQ Status Server process name process for HP NonStop KernelExplanation: You specified an invalid WebSphere MQ Status Server for the queue manager.System Action: The current request fails.User Response: Specify a valid HP NonStop Kernel MQSS server process name.

KMC0338E Invalid local queue definition - cluster queue cannot be a transmit queueExplanation: You defined a local or model queue containing a reference to a cluster, but the queue is also defined with Usage=Transmit. This is not supported.System Action: The current request fails.User Response: Either remove the cluster or cluster namelist reference from the local queue definition, or change the usage of the queue to Normal.

KMC0339W The corresponding receiver channel is not associated with the sender channels cluster setExplanation: You have defined a cluster sender channel and associated the channel with one or more cluster names. However, at least one of the cluster names is not associated with the corresponding cluster receiver channel.System Action: The current request fails.User Response: Modify the definition of the cluster sender and cluster receiver channels so that each cluster associated with sender channel is also associated with the receiver channel.

KMC0340W A cluster receiver channel corresponding to this cluster sender is not defined on another queue managerExplanation: You have defined a cluster sender channel; however, there is no corresponding cluster receiver channel on any other queue manager in the configuration with a matching name.System Action: The current request fails.User Response: You can either rename the cluster sender channel to have the same name as the cluster receiver on the queue manager you wish the sender to

KMC Messages


connect to; or you can define a cluster receiver channel with the same name on the connected queue manager.

KMC0341W The receiving Queue manager manager is not a repository for the clusters associated with the sender channelExplanation: You have defined a cluster sender channel; however, the queue manager that the sender will connect to is not defined as a full repository for all the clusters that the sender is associated with.System Action: The current request fails.User Response: This message is a warning. Normally, predefined cluster sender channels are only required to at least one queue manager which is acting as a full repository for the cluster.

KMC0342W Duplicate cluster receiver channels were detected in the configuration which match this cluster senderExplanation: You have defined a cluster sender channel; however, the Configuration Manager found more than one cluster receiver channel on other queue managers in the configuration which could match up with this cluster sender.System Action: The current request fails.User Response: This message is a warning. Duplicate cluster receiver names can create confusion, and can prevent the configuration product from performing complete validation. You might consider adopting a naming standard for your cluster receiver channels that prevents duplicate names.

KMC0343E Cluster sender channels are not allowed on this version of WebSphere MQExplanation: You defined a cluster sender channel on a queue manager that does not support them. Cluster sender channels are only supported on:

� WebSphere MQ for z/OS Version 2.1 and above.

� WebSphere MQ for distributed systems versions 5.1 and above.

System Action: The current request fails.User Response: Either delete the cluster sender, or upgrade WebSphere MQ to a version that supports clustering.

KMC0344E Cluster receiver channels are not allowed on this version of WebSphere MQExplanation: You defined a cluster receiver channel on a queue manager which does not support them. Cluster receiver channels are only supported on:

� WebSphere MQ for z/OS Version 2.1 and above.

� WebSphere MQ for distributed systems versions 5.1 and above.

System Action: The current request fails.User Response: Either delete the cluster receiver or upgrade WebSphere MQ to a version that supports clustering.

KMC0345E Cluster and cluster namelist cannot both be specifiedExplanation: You defined a queue or channel which specifies both the Cluster Name and Cluster Namelist properties. These properties are mutually exclusive.System Action: The current request fails.

Messages 219

KMC Messages

User Response: Change the definition of the object so that either Cluster Name or Cluster Namelist is blank.

KMC0346E The referenced cluster namelist namelist is not found within the queue managerExplanation: You defined a value for the cluster namelist for the queue or channel. However, the name that you specified is not defined as a namelist within the queue manager's subordinate resources.System Action: The current request fails.User Response: Ensure that the name you specify as a cluster namelist is defined as a namelist within the queue manager.

KMC0347E The repository cluster associated with the queue manager has no cluster receiver channel defined in the queue managerSystem Action: You defined a queue manager that is to act as full repository for one or more clusters. However, at least one of these clusters does not have a defined cluster receiver channel within this queue manager.System Action: The current request fails.User Response: Ensure there is a cluster receiver channel defined within this queue manager associated with each cluster that the queue manager is to act as a full repository for.

KMC0348E Invalid cluster name clusterExplanation: The cluster name associated with this object is not a valid WebSphere MQ cluster name.System Action: The current request fails.User Response: Ensure that the cluster name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0349E Invalid cluster workload exit data dataExplanation: You specified an invalid cluster workload management exit data for the queue manager.System Action: The current request fails.

KMC Messages


User Response: Specify a valid cluster workload management exit data. The maximum length is 32 characters.

KMC0350E Invalid maximum cluster workload data length lengthExplanation: You specified invalid cluster workload management maximum message data for the queue manager.System Action: The current request fails.User Response: Specify a valid cluster workload management maximum message data. Specify a value between zero and 4 MB for z/OS, or between zero and 999,999,999 on other platforms.

KMC0351E Invalid cluster namelist namelistExplanation: The cluster namelist associated with this object is not a valid WebSphere MQ namelist.System Action: The current request fails.User Response: Ensure that the namelist name is valid. The character set that can be used for naming all WebSphere MQ objects is as follows:� Uppercase A-Z


� Numerics 0-9

� Period (.)


� Underscore (_)



KMC0352E Invalid default bindExplanation: You specified an invalid default binding property for the queue.System Action: The current request fails.User Response: Specify a valid default binding property.

KMC0353E Invalid network priority priorityExplanation: You specified an invalid network priority for the channel.System Action: The current request fails.User Response: Specify a valid network priority. The value must be in the range 0 through 9.

KMC0359E Invalid autostart inhibit typeExplanation: You specified an invalid autostart property for the channel.System Action: The current request fails.User Response: Specify a valid autostart property.

Messages 221

KMC Messages

KMC0360E Triggering is enabled for the transmit queue but the channel channel is not definedExplanation: You have enabled triggering for the transmit queue, but the process name is blank, and the trigger data field does not contain the name of a channel defined within the queue manager.System Action: The current request fails.User Response: Correct the trigger data for queue. It should contain the name of the channel to be started when the trigger occurs. Optionally, you can leave both the process name and the trigger data blank for the queue, in which case the channel initiator will search for a channel associated with the transmit queue.

KMC0361E Invalid default protocol for managed clusterExplanation: You specified an invalid default network protocol for the managed cluster.System Action: The current request fails.User Response: Specify a valid default network protocol.

KMC0362E Invalid full repository settingExplanation: You specified an invalid Acts as cluster repository property for the cluster queue manager.System Action: The current request fails.User Response: Specify a valid Acts as cluster repository property.

KMC0363E The managed cluster does not have at least one full repository queue managerExplanation: You defined a managed cluster, but none of the cluster queue managers associated with the cluster are defined to act as a full repository.System Action: The current request fails.User Response: Ensure that at least one of the cluster queue managers is designated as a full repository for the cluster.

KMC0364E Cluster queue manager should have at least one connection to a full repositoryExplanation: This cluster queue manager is not a full repository, and it does not have any defined connections to any full repositories.System Action: The current request fails.User Response: Ensure that this cluster queue manager has a predefined connection to at least one full repository queue manager by configuring the Channels page in the cluster queue manager's settings.

KMC0365W The cluster queue must reside on at least one queue managerExplanation: You have defined a cluster queue, but you have not indicated on which cluster queue managers the queue is to reside.System Action: The current request fails.User Response: Use the Cluster Queue Location page in the cluster queue's settings to indicate on which cluster queue manager the queue is to reside. At least one cluster queue manager must be selected.

KMC Messages


KMC0366E The cluster queue definition conflicts with an identically name queue in cluster clusterExplanation: You have defined at least one other cluster queue in the configuration that has the same name as this one, and is defined to reside on one or more of the same queue managers. However, there is a conflict in the definitions of these two cluster queues. For example, the maximum message length of one cluster queue is 5000, while on the other cluster queue it is defined as 9,999.System Action: The current request fails.User Response: Examine the definitions of both cluster queues to resolve any conflicts.

KMC0367E Unable to locate the queue manager for this cluster queue managerExplanation: The queue manager that corresponds to this cluster queue manager definition could not be found.System Action: The current request fails.User Response: Collect the CMS log files, and contact IBM Software Support.

KMC0368E The Queue Manager is not at the minimum WebSphere MQ version to support cluster participationExplanation: The queue manager that is participating in this managed cluster is not at the proper WebSphere MQ version to support clustering. For a queue manager to participate in a cluster, WebSphere MQ must be at least at the 5.1 version (for distributed platforms) or the 2.1 version (for z/OS).System Action: The current request fails.User Response: Upgrade the WebSphere MQ software to the proper version.

KMC0369E Client connection channels are not allowed on this platformExplanation: You attempted to create an actual WebSphere MQ client connection channel; however, client connection channels are not supported on this platform or WebSphere MQ version. Client connection channels are not supported on WebSphere MQ Version 2.1 for Windows.System Action: The current request fails.User Response: Delete the defined client connection channel objects.

KMC0432E The queue manager is empty. Update Actual from Defined would result in all resources being deletedExplanation: The object that you selected from the topology display no longer exists within the configuration. It may have been deleted by another user.System Action: The current request fails.User Response: Close the topology window, select the View, Refresh now option, and recreate the topology window. Retry the request.

KMC0433E Invalid expired messages scan intervalExplanation: The OMEGAMON configuration agent for WebSphere MQ workstation component is running with an incompatible version of the configuration framework workstation component.System Action: The current request fails.

Messages 223

KMC Messages

User Response: Upgrade either the configuration agent or the configuration framework workstation component to a level of full compatibility.

KMC0436E This Configuration agent does not support the definition of client connection channelsExplanation: You have defined a client connection channel; however, the OMEGAMON configuration agent responsible for configuring the queue manager is backlevel and does not support the definition of client connection channels.System Action: The current request fails.User Response: Upgrade the OMEGAMON configuration agent on the system running this queue manager to at least the 3.5 level of OMEGAMON XE for WebSphere MQ.

KMC0437E A KEYPOSITION error was encountered attempting to read the HP NonStop Kernel OAM Data Base.Explanation: You have indicated that the configuration product should manage WebSphere MQ authorizations for this queue manager, running on the HP NonStop Kernel platform. However, the OMEGAMON configuration agent encountered an error from the KEYPOSITION service for the OAMDB file.System Action: The current request fails.User Response: Examine the OMEGAMON configuration agent log to determine the cause of the failure. If the problem persists, contact IBM Software Support.

KMC0438E A READ error was encountered attempting to read the HP NonStop Kernel OAM Data Base.Explanation: You have indicated that the configuration product should manage WebSphere MQ authorizations for this queue manager, running on the HP NonStop Kernel platform. However, the Configuration Agent encountered an error from the READ service for the OAMDB file.System Action: The current request fails.User Response: Examine the agent log to determine the cause of the failure. If the problem persists, contact IBM Software Support.

KMC0439E Your request failed. The configuration manager was unable to locate the WebSphere MQ Monitoring agent.Explanation: You entered a WebSphere MQ command to be executed for the resource; however, the request cannot be processed because the OMEGAMON Monitoring Agent for the queue manager is not currently connected.System Action: The current request fails.User Response: Start the WebSphere MQ monitoring agent for the queue manager.

KMC0440E Your request failed. The WebSphere MQ Monitoring agent agent returned an unknown code code.Explanation: You entered a WebSphere MQ command to be executed for the resource; however, the request could not be processed by the OMEGAMON Monitoring Agent, and an unanticipated return code was issued by WebSphere MQ.System Action: The current request fails.

KMC Messages


User Response: Look up the reason code among the Error Codes in the WebSphere MQ Programmable System Management manual. Take the action recommended. If the problem persists, contact IBM Software Support.

KMC0441E The command text is too long for the WebSphere MQ Monitoring agent to handle.Explanation: You entered a WebSphere MQ command to be executed for the resource; however, the request could not be processed because the text of the command is too long.System Action: The current request fails.User Response: Enter a shorter command.

KMC0442E Your request failed. The configuration manager was unable to find the command text.Explanation: You selected the WebSphere MQ command facility; however, the request could not be processed because the command text is missing.System Action: The current request fails.User Response: Enter a valid WebSphere MQ command.

KMC0443I Your WebSphere MQ command was successfully submitted.Explanation: Your WebSphere MQ command was successfully processed.System Action: Processing continues.User Response: None.

KMC0444E Your request failed. The command was rejected by WebSphere MQ.Explanation: You entered a WebSphere MQ command to be executed for the resource; however, the request could not be processed by WebSphere MQ, probably because of invalid syntax.System Action: The current request fails.User Response: Correct the syntax of the WebSphere MQ command and resubmit the command.

KMC0445E Your request to delete queue manager manager failed. The queue manager is a member of a managed cluster.Explanation: You attempted to delete a queue manager; however, the queue manager is currently part of a managed cluster, and cannot be deleted.System Action: The current request fails.User Response: Delete all cluster queue manager objects referencing this queue manager; then reattempt the delete request.

KMC0448E Queue manager manager could not be started. There was an error starting the channel listener.Explanation: The Configuration Manager attempted to start the queue manager, and you had previously indicated in the queue manager settings that the channel listener should be automatically started. However, an error was encounted attempting to start the channel listener.System Action: The current request fails.

Messages 225

KMC Messages

User Response: Examine the log for the OMEGAMON configuration agent to determine why the channel listener could not be started.

KMC0449E Queue manager manager could not be started. There was an error starting the channel initiator.Explanation: The Configuration Manager attempted to start the queue manager, and you had previously indicated in the queue manager settings that the channel initiator should be automatically started. However, an error was encounted attempting to start the channel initiator.System Action: The current request fails.User Response: Examine the log for the OMEGAMON configuration agent to determine why the channel initiator could not be started.

KMC0450E Queue manager manager could not be started. There was an error starting the trigger monitor.Explanation: The Configuration Manager attempted to start the queue manager, and you had previously indicated in the queue manager settings that the trigger monitor should be automatically started. However, an error was encounted attempting to start the trigger monitor.System Action: The current request fails.User Response: Examine the log for the OMEGAMON configuration agent to determine why the trigger monitor could not be started.

KMC0451E Invalid autostart trigger monitor valueExplanation: You specified an invalid start trigger monitor property for the queue manager.System Action: The current request fails.User Response: Specify a valid start trigger monitor property.

KMC0452E Invalid QSGDISP valueExplanation: You specified an invalid queue sharing group disposition property for the queue manager.System Action: The current request fails.User Response: Specify a valid queue sharing group disposition property.

KMC0453E This QSGDISP value is not supported on this version of WebSphere MQExplanation: You specified a queue sharing group disposition other than Queue Manager on a unsupported version of WebSphere MQ.System Action: The current request fails.User Response: Specify a valid queue sharing group disposition property.Note: The queue manager must be running on WebSphere MQ 2.2 for z/OS for you

to specify a value other than Queue Manager.

KMC0454E Invalid CLUSDISP valueExplanation: You specified an invalid queue sharing group cluster disposition property.System Action: The current request fails.User Response: Specify a valid queue sharing group cluster disposition property.

KMC Messages


KMC0455E This CLUSDISP value is not supported on this version of WebSphere MQExplanation: You specified a queue sharing group cluster disposition other than Queue Manager on a unsupported version of IBM Software Support.System Action: The current request fails.User Response: Specify a valid queue sharing group cluster disposition property.Note: The queue manager must be running on WebSphere MQ 2.2 for z/OS for you

to specify a value other than queue manager.

KMC0456E Invalid CFSTRUCT value cfstructExplanation: You specified an invalid queue-sharing group-coupling facility structure name.User Response: The current request fails.User Response: Specify a valid name for the coupling facility structure. Coupling facility structure names are restricted to a maximum of 12 characters in length. The first character must be in the range A through Z, and the subsequent characters must be in the range A-Z, 0-9.

KMC0457E You cannot alter the QSGDISP value once the actual /nresource has been createdExplanation: You are attempting to alter the queue sharing group disposition property. However, the property cannot be changed, either because this object is based on a prototype, or because the actual object corresponding to this defined object already exists. WebSphere MQ does not permit the QSGDISP property of an object to be modified once the actual object exists.System Action: The current request fails.User Response: You must delete and redefine this object to change the queue sharing group disposition property.

KMC0458E You cannot alter the CLUSDISP value once the actual /nresource has been createdExplanation: You are attempting to alter the queue-sharing group-coupling facility structure name; however, the name cannot be changed, either because this object is based on a prototype or because the actual object corresponding to this defined object already exists. WebSphere MQ does not permit the QSGDISP property of an object to be modified once the actual object exists.System Action: The current request fails.User Response: You must delete and redefine this object in order to change the queue sharing group coupling facility structure name.

KMC0459E Your request failed. Unknown WebSphere MQ object nameExplanation: The actual object does not exist.System Action: The current request fails.User Response: Specify a valid object name.

KMC0460E Invalid Intragroup queueing valueExplanation: You specified an invalid Intragroup queueing value.System Action: The current request fails.

Messages 227

KMC Messages

User Response: Replace the Intragroup queuing value with a valid value; valid values are ENABLE or DISABLE.

KMC0461E An error occurred processing the AMQOAMD commandExplanation: An error occurred when the OMEGAMON configuration agent issued a WebSphere MQ AMQOAMD Command.System Action: The current request fails.User Response: Review the agent log and the operating system’s log to find the cause of the error. If necessary, contact the IBM Software Support.

KMC0462E The authorization specification provided to the SETMQAUT command contained one or more items that could not be interpreted.Explanation: An error occurred when the OMEGAMON configuration agent issued a WebSphere MQ SETMQAUT command.System Action: The current request fails.User Response: Review the agent log and the operating system’s log to find the cause of the error. If necessary, contact the IBM Software Support.

KMC0463E Invalid LDAP Password name valueExplanation: You specified an invalid LDAP password.System Action: The current request fails.User Response: Replace the LDAP password with a valid value, up to 32 characters in length.

KMC0464E The channel is defined with QSGDISP(SHARED), but the transmit queue queue is not sharedExplanation: You defined a sender or server channel with a queue-sharing group disposition of Shared; however, the transmit queue referenced by the channel is not a shared queue.System Action: The current request fails.User Response: Either change the definition of the QSGDISP property for the channel to something other than Shared, or reference a shared transmit queue within the channel definition.

KMC0465E Index type of Message Token is not value for shared queuesExplanation: You defined a local queue with an index type of MSGTOKEN; however, the queue sharing group disposition for the queue is Shared. These properties are mutually exclusive.System Action: The current request fails.User Response: Either specify a different value for the index type, or change the QSGDISP of the queue to something other than Shared.

KMC0466E The maximum message length for a shared queue cannot exceed 64,512Explanation: You specified a maximum message length greater than 64,512 for a shared queue.System Action: The current request fails.User Response: Specify a smaller maximum message length.

KMC Messages


KMC0467E An error occurred processing the ALTMQUSR command.Explanation: An error occurred when the OMEGAMON configuration agent issued a WebSphere MQ ALTMQUSR command.System Action: The current request fails.User Response: review the agent log and the operating system’s log to find the cause of the error. If necessary, contact the IBM Software Support.

KMC0468E Channel listener on queue manager manager could not be stopped.Explanation: An error occurred when the OMEGAMON configuration agent issued a WebSphere MQ ENDMQLSR Command.System Action: The current request fails.User Response: Review the agent log and the operating system’s log to find the cause of the error. If necessary, contact the IBM Software Support.

KMC0469E Invalid LDAP user name valueExplanation: You specified an invalid LDAP user name value.System Action: The current request fails.User Response: Replace the LDAP user name value with a valid value: a valid LDAP user name is up to 256 characters in length for z/OS and up to 1024 characters in length for other platforms.

KMC0470E Invalid CFStruct name valueExplanation: You specified an invalid CFStruct name value.System Action: The current request fails.User Response: Replace the CFStruct name value with a valid value: a valid CFStruct name is up to 12 alphanumeric characters in length, with the first character alphabetic.

KMC0471E Invalid CFStruct level valueExplanation: You specified an invalid CFStruct level value.System Action: The current request fails.User Response: Replace the CFStruct level value with a valid value: a valid CFStruct level is 1 through 3 on pre-WebSphere MQ systems and 1 through 4 on WebSphere MQ Version 6 and higher.

KMC0472E This Expiry Interval value is not supported on this version of WebSphere MQExplanation: You specified a value for the expiry interval; however, this attribute is not supported on this level of WebSphere MQ. It is also not supported on the z/OS platform.System Action: The current request fails.User Response: Remove the expiry interval, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0473E Invalid Expiry Interval valueExplanation: You specified an invalid value for the expiry interval.System Action: The current request fails.

Messages 229

KMC Messages

User Response: Replace the expiry interval with a valid value: 0 through 99,999,999.

KMC0474E CFstructs are not allowed on this platformExplanation: You atttempted to define a CFStruct on an unsupported platform.System Action: The current request fails.User Response: Delete the CFStruct definition. CFStructs are supported only on the z/OS platform.

KMC0475E Authinfos are not supported on this version of WebSphere MQExplanation: You atttempted to define a authinfo on an unsupported WebSphere MQ version.System Action: The current request fails.User Response: Delete the authinfo definition, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0476E This Batch Heartbeat value is not supported on this version of WebSphere MQExplanation: You specified a value for batch heartbeat; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the batch heartbeat value, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0477E Invalid Batch Heartbeat valueExplanation: You specified an invalid value for batch heartbeat.System Action: The current request fails.User Response: Replace the Batch Heartbeat with a valid value; 0 thru 999,999.

KMC0478E This Configuration Event value is not supported on this version of WebSphere MQExplanation: You specified a value for configuration event; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the configuration event value, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0479E Invalid Configuration Event valueExplanation: You specified an invalid value for configuration event.System Action: The current request fails.User Response: Replace the configuration event with a valid value, ENABLE or DISABLE.

KMC0480E Invalid Keep Alive valueExplanation: You specified an invalid value for keep alive.System Action: The current request fails.User Response: Replace the keep alive with a valid value: 0 thru 9999.

KMC Messages


KMC0481E This Keep Alive value is not supported on this version of WebSphere MQExplanation: You specified a value for keep alive, however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the keep alive value, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0482E This Local Address value is not supported on this version of WebSphere MQExplanation: You specified a value for local address; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the local address value, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0483E Invalid Namelist Type valueExplanation: You specified an invalid value for namelist type.System Action: The current request fails.User Response: Replace the namelist type with a valid value: NONE, QUEUE, CLUSTER, AUTHINFO or ALL.

KMC0484E This Namelist Type value is not supported on this version of WebSphere MQExplanation: You specified a value for namelist type; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the namelist type, or upgrade the version of WebSphere MQ to version 5.3 or greater.

KMC0485E Invalid SSL Cipher Spec valueExplanation: You specified an invalid value for SSL Cipher Spec.System Action: The current request fails.User Response: Replace the SSL Cipher Spec with a valid value; refer to the WebSphere MQ Script (MQSC) Command Reference for valid SSL cipher specifications and platforms: see the SSLCIPH parameter.

KMC0486E This SSL Cipher Spec value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL Cipher Spec; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL Cipher Spec value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms: see the SSLCIPH parameter.

KMC0487E Invalid SSL Client Auth valueExplanation: You specified an invalid value for SSL Client Auth.System Action: The current request fails.

Messages 231

KMC Messages

User Response: Replace the SSL Client Auth with a valid value, OPTIONAL or REQUIRED.

KMC0488E This SSL Client Auth value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL Client Auth; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL Client Auth value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms.

KMC0489E Invalid SSL CRL Namelist valueExplanation: You specified an invalid value for SSL CRL Namelist.System Action: The current request fails.User Response: Replace the SSL CRL Namelist with a valid value; refer to the WebSphere MQ Script (MQSC) Command Reference for valid SSL CRL Namelist specifications and platforms.

KMC0490E This SSL CRL Namelist value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL CRL Namelist; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL CRL Namelist value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms.

KMC0491E Invalid SSL Key Repository valueExplanation: You specified an invalid value for SSL Key Repository.System Action: The current request fails.User Response: Replace the SSL Key Repository with a valid value; refer to the WebSphere MQ Script (MQSC) Command Reference for valid SSL Key Repository specifications and platforms.

KMC0492E This SSL Key Repository value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL Key Repository; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL Key Repository value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms.

KMC0493E Invalid SSL Peer Name valueExplanation: You specified an invalid value for SSL Peer Name.System Action: The current request fails.

KMC Messages


User Response: Replace the SSL Peer Name with a valid value: a maximum of 256 characters on z/OS; a maximum of 1024 characters on other platforms.

KMC0494E This SSL Peer Name value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL Peer Name; however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL Peer Name value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms.

KMC0495E Invalid SSL Tasks valueExplanation: You specified an invalid value for SSL Tasks.System Action: The current request fails.User Response: Replace the SSL Tasks with a valid value, 0 thru 9999.

KMC0496E This SSL Tasks value is not supported on this version of WebSphere MQExplanation: You specified a value for SSL Tasks, however, this attribute is not supported on this level of WebSphere MQ.System Action: The current request fails.User Response: Remove the SSL Tasks value, or upgrade the version of WebSphere MQ to version 5.3 or greater. Also refer to the WebSphere MQ Script (MQSC) Command Reference for valid platforms.

KMC0497E You must include the actual group/userid: principal(group.userid)Explanation: You specified an invalid authorzation string when creating a new principle on the HP NonStop Kernel platform.System Action: The current request fails.User Response: Correct the authorization string in line with HP NonStop Kernel principles.

KMC0498E You can only create Principals on HP NonStop Kernel.Explanation: You have attempted to create a principle on a non-HP NonStop Kernel platform.System Action: The current request fails.User Response: Remove the principle specification.

KMC0500E Error Positioning in the PRIDB FileExplanation: An error occurred trying to position to a record in the HP NonStop Kernel principle database (PRIDB).System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0501E Error Reading the PRIDB FileExplanation: An error occurred trying to read a record from the HP NonStop Kernel principle database (PRIDB).

Messages 233

KMC Messages

System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0502E WebSphere MQ Principles are not supported on this platformExplanation: You have attempted to create a principle on a non-HP NonStop Kernel platform.System Action: The current request fails.User Response: Remove the principle specification.

KMC0503E Shared Queues require a CFStructExplanation: You have defined a queue designated as Shared, but no CFStruct name has been specified.System Action: The current request fails.User Response: Define a CFStruct name in the Shared Queue definition.

KMC0504E Unable to open the PRIDB FileExplanation: An error occurred trying to open the HP NonStop Kernel principle database (PRIDB).System Action: The current request fails.User Response: Review the HP NonStop Kernel System Log before calling the IBM Software Support.

KMC0505E USER_GETINFO Invalid ParameterSystem Action: An error occurred trying to get the user information using the HP NonStop Kernel USER)GETINFO facility.System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0506E USER_GETINFO Missing ParameterExplanation: An error occurred trying to get the user information using the HP NonStop Kernel USER)GETINFO facility.System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0507E USER_GETINFO No Record FoundExplanation: An error occurred trying to get the user information using the HP NonStop Kernel USER)GETINFO facility.System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0508E USER_GETINFO Parameter Out of BoundsExplanation: An error occurred trying to get the user information using the HP NonStop Kernel USER)GETINFO facility.System Action: The current request fails.

KMC Messages


User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0509E USER_GETINFO Unknown Return CodeExplanation: An error occurred trying to get the user information using the HP NonStop Kernel USER)GETINFO facility.System Action: The current request fails.User Response: Review the HP NonStop Kernel system log before calling IBM Software Support.

KMC0510E An unexpected error occurred on a ALTMQAUT commandExplanation: An error occurred when the OMEGAMON configuration agent issued a WebSphere MQ ALTMQAUT command.System Action: The current request fails.User Response: Review the agent log and the operating system’s log to find the cause of the error. If necessary, contact IBM Software Support.

KMC0511E AuthInfo requires a Connection NameExplanation: You have defined an authinfo, but no connection name has been specified. A connection name is required.System Action: The current request fails.User Response: Define a connection name in the authinfo definition.

KMC0512E Single Quote found in DescriptionExplanation: A single quotation mark was found in a resource description. This is not valid.System Action: The current request fails.User Response: Append a second quotation mark to the single quotation mark.

KMC0513E Unable to Delete the Item from at least one QSGExplanation: While attempting to delete an existing QSG item from all queue managers in a QSG, at least one item could not be deleted.System Action: Processing continues.User Response: Retry the command at a later time.

KMC0514E Unable to Create the Item in at least one QSGExplanation: While attempting to propogate a new QSG Item to all queue managers in a QSG, at least one item could not be defined.System Action: Processing continues.User Response: Retry the command at a later time.

KMC0515E Invalid Adapter valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 235

KMC Messages

KMC0516E This Adapter Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0517E Invalid Backlog valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0518E This Backlog Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0519E Invalid Command Count valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0520E This Command Count Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0521E Invalid IP Address valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0522E This IP Address Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.Explanation: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0523E Invalid Listener Name valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0524E This Listener Name Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0525E Invalid Local Name valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0526E This Local Name Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0527E Invalid Name Count valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 237

KMC Messages

KMC0528E This Name Count Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0529E Invalid Port valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0530E This Port Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0531EInvalid Session Count valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0532E This Session Count Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0533E Invalid Socket valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0534E This Socket Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0535E Invalid Listener Control valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0536E This Listener Control Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0537E Invalid Channel Priority valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0538E This Channel Priority Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0539E Invalid Channel Rank valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 239

KMC Messages

KMC0540E This Channel Rank Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0541E Invalid Channel Weight valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0542E This Channel Weight Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0543E Invalid Channel Monitoring valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0544E This Channel Monitoring Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0545E Invalid Queue Monitoring valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0546E This Queue Monitoring Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0547E Invalid Auto Cluster Sender Monitoring valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0548E This Auto Cluster Sender Monitoring Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0549E Invalid Accounting Queue valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0550E This Accounting Queue Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0551E Invalid Queue Priority valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 241

KMC Messages

KMC0552E This Queue Priority Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0553E Invalid Queue Rank valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0554E This Queue Rank Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for IBM Software Support version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for IBM Software Support version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0555E Invalid Remote MQPUT valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0556E This Remote MQPUT Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0557E Invalid Active Channels valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0558E This Active Channels Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0559E Invalid Adopt MCA Check valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0560E This Adopt MCS Check Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0561E Invalid Adopt MCA Type valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0562E This Adopt MCA Type Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0563E Invalid Bridge Event valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 243

KMC Messages

KMC0564E This Bridge Event Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0565E Invalid Adapter Subtasks valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0566E This Adapter Subtasks Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0567E Invalid Dispatcher valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0568E This Dispatcher Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0569E Invalid Channel Event valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0570E This Channel Event Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0571E Invalid Outbound Cluster Channels valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0572E This Outbound Cluster Channels Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0573E Invalid Command Event valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0574E This Command Event Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0575E Invalid DNS Group valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 245

KMC Messages

KMC0576E This DNS Group Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0577E Invalid DNS WLM valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0578E This DNS WLM Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0579E Invalid Intra group Queueing valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0580E This Intra group Queueing Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0581E Invalid IGQ Put Authority valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0582E This IGQ Put Authority Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0583E Invalid IGQ UserID valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0584E This IGQ UserID Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0585E Invalid IP Address Version valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0586E This IP Address Version Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0587E Invalid Logger Events valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 247

KMC Messages

KMC0588E This Logger Events Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0589E Invalid Listener Timer valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0590E This Listener Timer Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0591E Invalid LU Group Name valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0592E This LU Group Name Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0593E Invalid LU Name valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0594E This LU Name Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0595E Invalid APPCPM Member Suffix valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0596E This APPCPM Member Suffix Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0597E Invalid LU62 Channels valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0598E This LU62 Channels Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0599E Invalid Max Channels valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 249

KMC Messages

KMC0600E This Max Channels Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0601E Invalid Max Outbound Ports valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0602E This Max Outbound Ports Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0603E Invalid Min Outbound Ports valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0604E This Min Outbound Ports Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0605E Invalid Receive Timeout valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0606E This Receive Timeout Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0607E Invalid Min Receive Timeout valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0608E This Min Receive Timeout Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0609E Invalid Receive Timeout Type valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0610E This Receive Timeout Type Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0611E Invalid Channel Initiator Start valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 251

KMC Messages

KMC0612E This Channel Initiator Start Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0613E Invalid Command Server Start valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0614E This Command Server Start Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0615E Invalid QSG Queue Manager Name Usage valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0616E This QSG Queue Manager Name Usage Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0617E Invalid SSL Events valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0618E This SSL Events Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0619E Invalid FIPS Algorithms Required valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0620E This FIPS Algorithms Required Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0621E Invalid SSL Reset Count valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0622E This SSL Reset Count Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0623E Invalid TCP Channels valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 253

KMC Messages

KMC0624E This TCP Channels Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0625E Invalid TCP Keep-Alive valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0626E This TCP Keep-Alive Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0627E Invalid TCP Name valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0628E This TCP Name Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0629E Invalid TCP Stack Type valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0630E This TCP Stack Type Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0631E Invalid Channel Initiator Trace Start valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0632E This Channel Initiator Trace Start Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0633E Invalid Channel Initiator Trace Table Size valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0634E This Channel Initiator Trace Table Size Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0635E Invalid Pass Ticket Application valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 255

KMC Messages

KMC0636E This Pass Ticket Application Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0637E Invalid Accounting Override valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0638E This Accounting Override Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0639E Invalid Accounting Interval valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0640E This Accounting Interval Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0641E Invalid Accountinq MQI valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0642E This Accounting MQI Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0643E Invalid Activity Recording valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0644E This Activity Recording Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0645E Invalid Header Compression valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0646E This Header Compression Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0647E Invalid Message Compression valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 257

KMC Messages

KMC0648E This Message Compression Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0649E Invalid Statistics Auto Cluster-Sender valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0650E This Statistics Auto Cluster-Sender Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0651E Invalid Channel Statistics valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0652E This Channel Statistics Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0653E Invalid Statistics Interval valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC Messages


KMC0654E This Statistics Interval Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0655E Invalid Statistics MQI valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Referenceto determine the range of values allowed.

KMC0656E This Statistics MQI Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0657E Invalid Queue Statistics valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

KMC0658E This Queue Statistics Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KMC0659E Invalid Trace Route Recording valueExplanation: The value specified for this attribute is outside the range of allowable values.System Action: Validation for the item fails.User Response: Review the WebSphere MQ Script (MQSC) Command Reference to determine the range of values allowed.

Messages 259

KMC Messages

KMC0660E This Trace Route Recording Parameter is not supported on this Platform or Version of WebSphere MQExplanation: This parameter is valid only for WebSphere MQ version 6 and above.System Action: Validation for the item fails.User Response: If this parameter is being defined for WebSphere MQ version 6 or later, ensure that it is supported on the platform for which you are trying to define it.

KCF Messages


KCF Messages

These messages take the form KCFnnnnx; these are errors which are reported by the Configuration Manager and displayed by CandleNet Portal.

KCF0006E Source object object is locked by another user userExplanation: You copied or moved configuration object object, but the object is currently being used by user user.User Response: Wait until user user is done with the configuration object.

KCF0007E Target object object is locked by another user userExplanation: You are attempting to perform an action against configuration object object, but the object is currently being used by user userUser Response: Wait until user user is done with the configuration object.

KCF0008E The source object object has been altered. A refresh of the object is recommendedExplanation: The configuration object object has recently been altered. The information contained in your workstation about the object may be inaccurate.User Response: Right click on the object, and select the Refresh option from the pop-up menu, or select the Refresh now option from the View pulldown menu. If the object information still does not appear refreshed, recycle the CandleNet Portal to reload the changes.

KCF0009E The target object object has been altered. A refresh of the object is recommendedExplanation: The configuration object object has recently been altered. The information contained in your workstation about the object may be inaccurate.User Response: Right click on the object, and select the Refresh option from the pop-up menu, or select the Refresh now option from the View pulldown menu. If the object information still does not appear refreshed, recycle the CandleNet Portal to reload the changes.

KCF0010E Not authorized to access target objectExplanation: You are attempting to create a scheduled action, but you are not authorized to access one or more of the target objects.User Response: Ensure that you are authorized to access the targets of the scheduled action.

KCF0011E A program exception occurred in Configuration Manager within the Candle Management ServerExplanation: A fatal error has been detected at the Candle Management Server.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support

KCF0012E A severe error has occurred attempting to update configuration data base within the Candle Management ServerExplanation: A fatal error has been detected within the configuration database manager.

Messages 261

KCF Messages

System Action: The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0013E The Configuration Manager is unavailable within the Candle Management ServerExplanation: The Configuration Manager has shut itself down because of a prior error. Your request cannot be processed.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0014E Source source and target target are incompatible types for move/copy requestExplanation: Your have requested that configuration object source be copied to configuration object target; however, object source cannot exist within object target.User Response: Ensure that the source and target objects of a drag/drop operation are compatible.

KCF0015E The Configuration Manager within the Candle Management Server was unable to create data base work unitExplanation: Your request cannot be processed, because the configuration data base manager within the CMS was unable to create an internal resource.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0016E The selected object is unavailable because it is scheduled for action actionExplanation: You have attempted to access an object in the configuration; however, this object is the target of scheduled action action, and the Prevent updates if enabled option is selected for the scheduled action.User Response: Wait until the scheduled action action has completed execution; if you cannot wait, you must either disable the scheduled action or reset the Prevent updates if enabled option.

KCF0017E You cannot do this because you are not currently in update modeExplanation: You are attempting to modify the configuration data; however, your session is not currently in update mode.User Response: Select Update mode from the Configuration Manager pulldown menu on the Configuration Manager’s Icons window.

KCF0018E The Configuration Manager was unable to locate or create the default resource group for configured system system. Possible authorization problem.Explanation: Either you attempted a Discover or Update Defined from Actual operation against configured system system; however, the Configuration Manager was unable to create the default resource group, or you attempted a copy to database operation, which cannot be done because the default resource group does not exist and you do not have sufficient authority for the queue manager.

KCF Messages


User Response: Verify that you have sufficient authority to perform the operation on the queue manager. If the problem persists, collect the CMS log files, and contact IBM Software Support.

KCF0019E The update actual from defined cannot be performed because of a validation failure. Select the validate option for the objectExplanation: You requested an Update Actual from Defined operation; however, the Configuration Manager detected a validation error in the target defined configuration object.User Response: Right-click the configuration object and select the Validate option to view the validation error(s). Correct the errors, and retry the Update Actual from Defined operation.

KCF0020E The Configuration manager was unable to build the resource name for the objectExplanation: The Configuration Manager was unable to determine the name of a resource contained within a resource group for an Update or View discrepancies request.User Response: Ensure that each resource contained within each targeted resource group has a valid name. If necessary, collect the CMS log files. Contact IBM Software Support.

KCF0021E The Configuration manager was unable to locate the configured system for the objectExplanation: The Configuration Manager was unable to locate the configured system associated with the target object.User Response: Collect the CMS log files. Contact IBM Software Support.

KCF0022E The Configuration manager was unable to create a handle set for selection groupExplanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0023E The selection group is empty. No action takenExplanation: You have attempted to access one or more objects which no longer exist within the configuration.User Response: Select the Refresh now option from the View pulldown menu; then retry the original request.

KCF0024E The object cannot be deleted because it is in useExplanation: The object that you are attempting to delete is currently in use and cannot be deleted.User Response: Wait until the object is no longer being used, and retry.

Messages 263

KCF Messages

KCF0025E The prototype proto cannot be deleted because it is in useExplanation: You have requested that prototype object proto be deleted; however, this prototype is currently referenced by one or more defined objects or prototype reference objects.User Response: Right-click on prototype object proto, and select the Disinherit objects option. This breaks the link between defined and prototype objects. After this, retry the Delete request.

KCF0026E The configuration is not owned by the user session. No action takenExplanation: You have requested that ownership of the entire configuration be released; however, your session does not currently own the entire configuration.User Response: No action is required. There is no need to release ownership of the configuration if you do not own it.

KCF0027E Your request failed because the entire configuration is owned by user userExplanation: You attempted to access one or more configuration objects; however, you cannot do this at this time because another user user currently owns the entire configuration.User Response: Wait until user user is done with the entire configuration.

KCF0028E Configuration ownership cannot be obtained because other work is in progressExplanation: You cannot obtain ownership of the entire configuration while other work (such as other sessions, or scheduled actions) is being processed.User Response: Reattempt this request when there is no other work being performed by the Configuration Manager.


KCF0030E One or more selected objects no longer existExplanation: You have attempted to access one or more objects which no longer exist within the configuration.User Response: Select the Refresh now option from the View pulldown menu; then retry the original request.


KCF Messages


KCF0032E One or more of the selected objects has been altered. A refresh is recommendedExplanation: One or more of the selected objects has recently been altered. The information contained in your workstation about the objects may be inaccurate.User Response: Select the Refresh now option from the View pulldown menu. If the object information still does not appear refreshed, recycle the CandleNet Portal to reload the changes.

KCF0033E The Configuration Manager within the Candle Management Server is quiescingExplanation: The Configuration Manager cannot process your request because it is shutting down.User Response: End the CandleNet Portal server session and wait until the CMS has been restarted; then restart the CandleNet Portal server and reattempt the operation.

KCF0034E The requested system variable variable cannot be updated or deletedExplanation: You have attempted to modify a global variable that is not a User or Product variable.User Response: Ensure that the variable that you are trying to modify is not a System variable.

KCF0035E The Configuration Manager was unable to find the import file directoryExplanation: The files containing initial resouce and prototype definitions to be imported, were not found by the Configuration Manager. Either the files were not installed or were not installed in the usual location.User Response: Locate the import files (KMC*.CDI files) in the installation, in this location:� For a CMS running on a distributed platform, the files are in the RKCFCDI

CMS’s subdirectory.

� For a CMS running on z/OS, these files are located in dataset RKANDATV.

Note the location of import data files, and collect the CMS log. Contact IBM Software Support.

KCF0036E The Configuration Manager had an error opening the import fileExplanation: The Configuration Manager encountered error while opening the import files containing initial resouce and prototype definitions. This may be due to insufficient access assigned to these files.User Response: Ensure that the user starting the CMS process has at least read access to the import (KMC*.CDI) files, in this location:� For a CMS running on a distributed platform, the files are in the CMS’s

RKCFCDI directory.

� For a CMS running on the z/OS platform, these files are in dataset RKANDATV.

If the user does not have read access to these files, grant user the access, and restart the CMS.

Messages 265

KCF Messages

KCF0037E The import file is in an incorrect format and cannot be processedExplanation: The import file containing initial resource and prototype data contain invalid data.User Response: Collect the import files KMC*.CDI from the following locations:� For a CMS running on a distributed platform, the import files are in the CMS’s

RKCFCDI directory.

� For a CMS running on the z/OS platform, these files are in dataset RKANDATV.

Then contact IBM Software Support.

KCF0038E The Configuration Manager encountered a severe error attempting to read from the configuration databaseExplanation: A fatal error has been detected within the configuration database manager.System Action: The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0039E The Configuration Manager encountered a severe error opening the file fileExplanation: You entered a command requiring the Configuration Manager to open an external file; however, the file could not be opened.User Response: Ensure that the file name specified is valid. On z/OS, the file must be a preexisting data set. Ensure there is sufficient disk space available to write into this file.

KCF0040E The Configuration Manager encountered a severe error writing the fileExplanation: A fatal error has been detected within the configuration database manager.System Action: The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0041E Dynamic allocation of output file failedExplanation: While performing an Export or Backup command, the requested output file could not be allocated. The requested action is terminated.User Response: If the allocation is being attempted on z/OS, then the requested file must be preallocated (also ensure that you do not enclose the name in quotes). For all platforms, ensure you specified a valid file name for that platform and that you have the appropriate authority to access that file.

KCF0042E The Configuration Manager was unable to find or create auto discovery groupExplanation: The Configuration Manager's Auto Discover feature has been turned on. But Configuration Manager was unable to create the Configured Systems Group object to insert discovered Configured Systems. Auto Discover will not work.User Response: Collect the CMS log, and contact IBM Software Support.

KCF Messages


KCF0043E One of the objects using the prototype is being used by another userExplanation: You attempted a Disinherit operation; however, the defined object cannot be disinherited from the prototype because it is currently in use.User Response: Wait until all defined objects associated with the prototype are no longer in use before attempting a Disinherit operation.

KCF0044E An invalid action request was sent to the configuration manager by the workstationExplanation: The workstation sent a request to the CMS which is not supported by the Configuration Manager.User Response: Collect the CMS log files. Contact IBM Software Support.

KCF0045E The requested object does not exist in the configuration database.Explanation: You attempted, from a workspace in OMEGAMON XE for WebSphere MQ Monitoring, to directly configure a resource managed by OMEGAMON XE for WebSphere MQ Configuration, but the selected WebSphere MQ resource is not defined in the configuration database. The attempted action cannot be completed.User Response: From OMEGAMON XE for WebSphere MQ Configuration, first ensure that the queue manager that owns the resource you selected is defined in the configuration database. If it is not, use the Discover feature to add the queue manager definition into the configuration database. If the owning queue manager is defined, next ensure that the WebSphere MQ resource you selected is defined in the configuration database. If it is not, select the queue manager, and use the Discover New Resources feature to add the resource to the database. Note that permanent dynamic queue definitions are not created in the database unless you have enabled that option in the Auto Start section of the queue manager settings.

KCF0046I The validation request completed successfully. No validation errors were detectedExplanation: You requested a Validate operation, and the Configuration Manager did not find any validation errors in the select objects.User Response: None.

KCF0047I The view discrepancies request completed successfully. No discrepancies were detectedExplanation: You requested a View discrepancies operation, and the Configuration Manager did not find any discrepancies between the defined and actual objects.User Response: None.

KCF0048E The request to move or copy the selected object failed because of a failure moving or copying another selected objectExplanation: You attempted to move or copy two or more objects. The request could not be processed on the second or subsequent objects because of a failure moving or copying a prior selected object.User Response: Determine why the move or copy of the prior object in the group failed. Correct the problem, and retry the request.

Messages 267

KCF Messages

KCF0049E The configuration manager did not recognize your session. Please restart the WorkstationExplanation: Because of a probable communications or other workstation problem, the Configuration Manager in the CMS no longer recognizes your session.User Response: Restart the CandleNet Portal server. Collect the CMS and CandleNet Portal server log files. If necessary, contact IBM Software Support.

KCF0050E The import file is in an incorrect format and cannot be processedExplanation: The import file containing initial resource and prototype data contains invalid data.User Response: Collect the import files KMC*.CDI from the following locations:� For a CMS running on a distributed platform, the import files are in the CMS’s

RKCFCDI directory.

� For a CMS running on the z/OS platform, the import files are in dataset RKANDATV.

Contact IBM Software Support.

KCF0051E The configuration agent agent is not at the proper version to process this requestExplanation: You have entered a request requiring processing by the OMEGAMON configuration agent agent; however, this agent is running a back-level version and is unable to perform your request.User Response: Ensure that the OMEGAMON configuration agent is running at the most current software level.

KCF0052E Your request failed because the Configuration Manager was unable to create an internal SQL requestExplanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0053E Your request failed because the Configuration Manager was unable to open an internal SQL requestExplanation: The Configuration Manager was unable to open the internal request required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0054E Your request failed because the Configuration Manager received a bad return code agent from configuration agent codeExplanation: Your request was sent to OMEGAMON configuration agent agent; however, the agent was unable to process the request and returned a code of code.User Response: Collect the CMS and agent log files. Contact IBM Software Support.

KCF Messages


KCF0055E Your request failed because the Configuration Manager did not receive requested configuration data from configuration agent agentExplanation: A request for actual configuration information was sent to OMEGAMON configuration agent agent; however, the agent did not provide the requested data; the reason for this is unknown.User Response: Collect the CMS and agent log files. Contact IBM Software Support.

KCF0056E Your request failed because the configuration agent agent reported an undefined Application Name applicationExplanation: The OMEGAMON configuration agent agent reported that it was associated with application name application. This application name is unknown or unsupported.User Response: Ensure that the proper OMEGAMON configuration agent is running. If you cannot see any problem, collect the CMS and agent log files. Contact IBM Software Support.

KCF0057E Your request failed because the configured system required to communicate with the target configured system is not currently definedExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is not currently defined within the configuration.User Response: Ensure that the intermediate system is defined correctly within the configuration.

KCF0058E Your request failed because the configured system required to communicate with the target configured system is an indirect connectionExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is also defined as requiring an intermediate system. This is not supported.User Response: Ensure that the definition of the intermediate system does not itself require an intermediate system.

KCF0059E Your request failed because the Configuration Agent agent does not exist in the Managed Systems folderExplanation: The targeted configured system is defined with OMEGAMON configuration agent agent; however, this OMEGAMON configuration agent does not exist in the CandleNet Portal Managed Systems folder.User Response: Ensure that the OMEGAMON configuration agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

KCF0060E Your request failed because the Configuration Agent agent is offlineExplanation: The targeted configured system is defined with OMEGAMON configuration agent agent; however, this OMEGAMON configuration agent is not online in the CandleNet Portal Managed Systems folder.

Messages 269

KCF Messages

User Response: Ensure that the OMEGAMON configuration agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

KCF0061E Your request failed because the configured system required to communicate with the target configured system system is not currently onlineExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is not currently online.User Response: Ensure that the intermediate system is defined correctly and is running. Also ensure that the OMEGAMON configuration agent associated with the intermediate configured system is online within the CandleNet Portal Managed Systems folder.

KCF0062E Your request failed because the Configuration Agent agent cannot connect with Configured System system. The configured system may not be startedExplanation: OMEGAMON configuration agent agent was unable to communicate with configured system system. This may be because the configured system is not started, and the autostart option is not selected for the configured system.User Response: Ensure that configured system is started. If you want the OMEGAMON configuration agent to automatically start the system, select the autostart option in the configured system definition. Check the agent and CMS logs for more details as to why the agent was unable to communicate with the configured system.

KCF0063E Your request failed because the Configuration Agent agent was unable to start Configured System systemExplanation: You have the autostart option enabled for configured system system, but the OMEGAMON configuration agent agent was unable to start the configured system.User Response: Ensure the configured system is defined. If you want the OMEGAMON configuration agent to automatically define the system, select the autocreate option in the configured system definition. Check the agent and CMS logs for more details as to why the agent was unable to start the configured system.

KCF0064E Your request failed because the Configuration Agent agent was unable to create Configured System systemExplanation: You have the autocreate option enabled for configured system system, but the OMEGAMON configuration agent agent could not create the configured system.User Response: Check the agent and CMS logs for more details as to why the agent was unable to create the configured system. If necessary, attempt to define the configured system manually.

KCF Messages


KCF0065E Your request failed because the Configuration Manager received invalid data from agent agentExplanation: A request for actual configuration information was made to OMEGAMON configuration agent agent; however, the agent returned invalid data to the Configuration Manager.User Response: Collect the CMS and agent log files. Contact IBM Software Support.

KCF0066E Your request failed because the Configuration Manager did not receive all requested data from configuration agent agent quickly enough. Possible agent timeoutExplanation: A request for actual configuration information was made to OMEGAMON configuration agent agent; however, the agent did not return the requested information within the required time period.User Response: This problem can be caused by communication problems, or by poor performance by either the OMEGAMON configuration agent or the configured system. You can increase the amount of time allowed for the return of configuration data from the Configuration Manager Option.

KCF0067E The configuration manager did not recognize your session. Please restart the WorkstationExplanation: Because of a probable communications or other workstation problem, the Configuration Manager in the CMS no longer recognizes your session.User Response: Restart the CandleNet Portal server. Collect the CMS and CandleNet Portal server log files. If necessary, contact IBM Software Support.

KCF0068E Your request failed because the Configuration Manager was unable to recognize session affinity affinityExplanation: Your workstation does not have the proper affinity affinity to access the configuration object.User Response: Ensure that you are using a workstation in which the proper CandleNet Portal server products have been installed. If so, restart the CandleNet Portal server. Collect the CMS and CandleNet Portal server log files. If necessary, contact IBM Software Support.

KCF0069E You do not have authority to perform this operation on objectExplanation: Your workstation does not have the proper affinity to access configuration object object.User Response: Ensure that you are using a workstation in which the proper CandleNet Portal server products have been installed. If so, restart the CandleNet Portal server. Collect the CMS and CandleNet Portal server log files. If necessary, contact IBM Software Support.

KCF0070E Your request failed because the actual resource does not existExplanation: You have requested to view or modify an actual configuration object; however, the object does not exist.User Response: Perform an Update Actual from Defined operation against the appropriate defined resource in order to create the actual resource.

Messages 271

KCF Messages

KCF0071E Your request failed because a required configuration property could not be locatedExplanation: Your request to view an actual object failed because a required property was not present in the defined configuration object.User Response: Collect the CMS log files. If necessary, contact IBM Software Support.

KCF0072E You cannot enable the scheduled action because of a conflicting scheduled actionExplanation: You have attempted to create or modify a scheduled action with the 'Prevent updates if enabled' option. However, one or more of the target configuration objects are already the target of another scheduled action with the Prevent updates if enabled option.User Response: Use the Schedules > View option to find the conflicting scheduled action. Wait until the conflicting scheduled action completes before defining or enabling the new scheduled action.

KCF0073I Your update request was successfully performedExplanation: Your request to Update actual from defined or Update defined from actual was completed successfully.User Response: None.

KCF0074E You cannot copy selected objects that are not owned by the same applicationExplanation: You have attempted an operation on multiple selected objects; however, the request cannot be processed because the objects are associated with different configuration application.User Response: Ensure that all selected configuration objects are associated with the same configuration application.

KCF0075E Your request failed. The copy target object target belongs to a different application than source object sourceExplanation: You have requested that one or more configuration objects be copied to a new target object; however, the target object is associated with an different configuration application.User Response: Ensure that the target object is associated with a compatible configuration application to the objects being copied.

KCF0076E Auto-define failed because the Configuration Manager found an invalid connection groupExplanation: You requested to connect two configured queue managers. Autodefinition of connection resources was attempted but failed because the prototype definitions corresponding to queue managers was not found.User Response: Open the Prototype View of Configuration Navigation tree. Expand Resource Group Prototypes. Ensure that Resource Group Prototypes $DefaultAutoConnectPrototype and $DefaultAutoConnectPrototypeMQWindows are defined.

KCF Messages


KCF0080E Your request failed because the configured system system cannot be started on the platform it resides onExplanation: You have selected the auto-start option for configured system system; however, the configured system is not currently running, and it cannot be automatically started on this platform.User Response: You must manually start the configured system on this platform.

KCF0081E Your request failed because the configured system system cannot be created on the target platform typeExplanation: You have selected the auto-create option for configured system system; however, the configured system does not exist, and it cannot be automatically created on this platform.User Response: You must manually create the configured system on this platform.

KCF0082E Your request failed because an exception occurred on configuration agent agent RC= code Reason= reasonExplanation: A request for actual configuration information was sent to OMEGAMON configuration agent agent; however, a program exception occurred on the agent. The RC code and Reason reason fields provide more detailed information.User Response: Collect the agent log files, and restart the agent. If necessary, contact IBM Software Support.

KCF0083E Auto-define failed because a duplicate configured system was foundExplanation: A configured system already existed with that name.User Response: Use another name.

KCF0084E Configured system could not be discovered because it is already definedExplanation: A configured system was discovered by a OMEGAMON configuration agent, but the configured system name already exists within the defined configuration. No action was taken.User Response: If you want to obtain the resource information for this configured system, in the Defined View right-click the configured system and, from the pop-up menu, select Update Defined from Actual.

KCF0085W Configured system system defined but its resources could not be discoveredExplanation: Configured system system was discovered and has been added to the defined configuration; however, the OMEGAMON configuration agent was unable to obtain any information from the configured system on its subordinate resources. This may be because the configured system was not active.User Response: If you want to obtain information on the resources subordinate to the configured system, you can set the auto-start option for the configured system, and select the Update Defined from Actual operation from the pop-up menu.

KCF0086W The Configuration Manager did not discover any configured systemsExplanation: You selected the Discover option for a configured system group, but no configured systems were detected.

Messages 273

KCF Messages

User Response: Ensure your OMEGAMON configuration agents are online by checking the CandleNet Portal Managed Systems folder.

KCF0087E The copy/move request is not allowed because a circular prototype reference was detected between target target and source sourceExplanation: You are trying to create a reference to a prototype within another prototype that would result in a circular set of prototype references. This is not supported.User Response: Ensure that the prototype that you are dragging does not contain a reference (either directly or indirectly) to the prototype you are dropping on.

KCF0088E The copy/move request is not allowed because target target is a descendant of the source sourceExplanation: You are trying to move or copy an object to a new target, but the target object is a direct or indirect descendant of the object being moved or copied. This is not supported.User Response: Ensure that the object that you are dragging does not contain (either directly or indirectly) the object you are dropping on.

KCF0089I The configured system and all resources were added to configurationExplanation: The configured system and all of it's subordinate resources were successfully added to the defined configuration.User Response: No action is required.

KCF0090E The Configuration Manager was unable to authorize your session with the System Authorization FacilityExplanation: The OMEGAMON configuration agent was unable to define your session because of a RACROUTE REQUEST=VERIFY failure. This could indicate a problem with the definition of your user id to RACF (or other equivalent service).User Response: Check the CMS log to determine the exact cause of the failure. If RACF is being used for authorization checking, consult IBM’s documentation.

KCF0091E The Configuration Manager was unable to terminate your session with the System Authorization FacilityExplanation: The Configuration Manager was unable to terminate your session because of a RACROUTE REQUEST=VERIFY failure. This could indicate a problem with the definition of your user id to RACF (or other equivalent service).User Response: Check the CMS log to determine the exact cause of the failure. If RACF is being used for authorization checking, consult IBM documentation.

KCF0092E You are not authorized to access configuration object objectExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to configuration object object.User Response: Contact your local security administrator to provide you with access to this configuration object.

KCF Messages


KCF0094E You are not authorized to delete object object from its parent parentExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to delete object object from its parent object parent.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the parent object.

KCF0095E You are not authorized to rename object object with new name newnameExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to rename configuration object object with the new name newname.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have ALTER access to the object under both the old and new names.

KCF0096E You are not authorized to update the actual resourceExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to update the actual resource associated with the defined resource.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have CONTROL access to the defined object.

KCF0097E You are not authorized to update the defined resourceExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to update the defined resource from the defined resource.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the defined object.

KCF0098E You are not authorized to modify the source object objectExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to the target object object of the move/copy request.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the defined object.

KCF0099E You are not authorized to modify the parent object objectExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to modify the defined object object.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the configured system.

Messages 275

KCF Messages

KCF0100E You are not authorized to move this objectExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to modify the defined object object.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the configured system.

KCF0101E You are not authorized to create object objectExplanation: Based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access to create a new defined object with name object.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have ALTER access to the new object name.

KCF0102E Your request failed because the audit log is not availableExplanation: The Configuration Manager was unable to write to or receive messages from the audit log because it is currently unavailable.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0103E Your request failed because the requested audit log record was not foundExplanation: You made a request to obtain the detailed information for a record in the audit log; however, the specified audit log record could not be found.User Response: Recreate the audit log details repor,t and retry. If necessary, collect the CandleNet Portal server and CMS log files, and contact IBM Software Support.

KCF0104E Your request failed because the requested audit log record has an invalid typeExplanation: You made a request to obtain the detailed information for a record in the audit log; however, the specified audit log record has an invalid type.User Response: Recreate the audit log details report, and retry. If necessary, collect the CandleNet Portal server and CMS log files and contact IBM Software Support.

KCF0105W No audit records were found in requested time periodExplanation: You made a request to view all the audit log records within a specified time span; however, no audit records were found which were created within the time span.User Response: Retry the request, specifying a different time span.

KCF0106E Your request failed because of a failure writing to the audit logExplanation: A failure was encountered writing a record to the audit log.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF Messages


KCF0107E Your request cannot be processed because the Configuration Manager was shut downExplanation: The Configuration Manager is not available within the CMS because it has been shut down. This could be because of a normal shutdown request for the CMS, or because of a previously-detected error.User Response: Unless you know a normal shutdown was requested, you should collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0108E Your request cannot be processed because the Configuration Manager shut down due to a data base errorExplanation: The Configuration Manager is not available within the CMS because it has been shut down due to a database failure.User Response: Collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0109E Your request cannot be processed because the Configuration Manager shut down due to a program exceptionExplanation: The Configuration Manager is not available within the CMS because it has been shut down due to a fatal program exception.User Response: Collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0110E Your request cannot be processed because the Configuration Manager is not currently activeExplanation: The Configuration Manager is not available within the CMS because it has been shut down or was never started. The shutdown could be due to a normal shutdown request for the CMS, or because of a previously detected error.User Response: Unless you know that a normal shutdown was requested, or that the Configuration Manager was never started, you should collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0111E Your request cannot be processed because the CMS was unable to start the Configuration ManagerExplanation: The Configuration Manager is not available within the CMS because it was not successfully started.User Response: Collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0112E Your request cannot be processed because the Configuration Manager was shut down. No applications were installedExplanation: The Configuration Manager shut itself down at startup time because it did not detect the installation of any configuration applications.User Response: Ensure that the appropriate configuration applications are installed at the hub CMS.

Messages 277

KCF Messages

KCF0113E Your request cannot be processed because the Configuration Manager was shut down. The Managed Systems list could not be updatedExplanation: The Configuration Manager is not available within the CMS because it has been shut down due to a problem updating the CandleNet Portal Managed Systems folder. This could be due to the fact that the hub CMS is configured for hot standby, and a Hub switch has taken place.User Response: The Configuration Manager will not run in a backup CMS. Ensure that the Configuration Manager is only running on a primary hub CMS.

KCF0114W Actual resource does not existExplanation: On a View Discrepancies request, this resource was found in the defined configuration, but not in the actual configuration.User Response: Right click on the resource type in the left-hand column, and select either the Build actual option (to create the actual resource) or the Delete from database option (to delete the defined resource from the configuration).

KCF0115W Defined resource does not existExplanation: On a View Discrepancies request, this resource was found in the actual configuration, but not in the defined configuration.User Response: Right click on the resource type in the left-hand column, and select either the Copy to database option (to create the defined resource from the actual definition) or the Delete actual option (to delete the actual resource).

KCF0116W Property definition conflict between defined and actualExplanation: Your request to view discrepancies between the defined and actual resource definitions was executed and discrepancies were found.User Response: The details of discrepancies between actual and defined resouces is displayed at the CandleNet Portal. If this is the result of a scheduled action, then select action details from the Scheduled Action Summary report to view discrepancy results.

KCF0117E A severe error has occurred attempting to update the configuration data base within the Candle Management ServerExplanation: A fatal error has been detected within the Configuration database manager. The Configuration Manager has shut itself down.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0118E A duplicate resource name was found in systemExplanation: The validation request against the configured system has encountered two subordinate resources which are duplicately named.User Response: Rename or delete one of the duplicate resources.

KCF0119E The Configuration Manager did not receive an acknowledgment from the agent indicating that the update for resource resource completed successfullyExplanation: The Configuration Manager sent a request to the OMEGAMON configuration agent to modify actual configuration data. The agent did not send back

KCF Messages


an acknowledgement that the request was processed successfully. The status of the update request is unknown.User Response: Collect the CMS and agent log files. Restart the agent. Contact IBM Software Support.

KCF0120E Your request failed. Configured system system is not online.Explanation: Configured system system is not currently active, or some other problem is preventing the OMEGAMON configuration agent from contacting it.User Response: If the configured system is currently active, you can either start the system manually, or you can indicate that you want the OMEGAMON configuration agent to start the system for you. To do this, select the autostart option for the configured system.

KCF0121E Your request failed because of an internal error within the Configuration ManagerExplanation: An unanticipated condition occurred within the Configuration Manager, causing your request to fail.User Response: Collect the CMS log files, and contact IBM Software Support.

KCF0122E Your request failed because of an error on configured system system RC=code Reason=reasonExplanation: An error on configured system system caused your request to fail. The RC code and Reason reason fields provide additional information.User Response: Collect the agent and CMS log files, and restart the agent. If necessary, contact IBM Software Support.

KCF0123E Your Update Actual from Defined request failed because the defined object was not successfully validated. Select the Validate option for the object to fix the problem.Explanation: You requested an Update Actual from Defined operation; however, the Configuration Manager detected a validation error in the target defined configuration object.User Response: Right-click the configuration object, and select the Validate option to view the validation errors. Correct the errors, and retry the Update Actual from Defined operation.

KCF0124E The request action is not applicable for this type of objectExplanation: The requested action is not application to this type of object.User Response: Collect the CMS log files. If necessary, contact IBM Software Support.

KCF0125E Your request failed because the Configuration Agent agent does not exist in the Managed Systems folderExplanation: The targeted configured system is defined with OMEGAMON configuration agent agent; however, this OMEGAMON configuration agent does not exist in the CandleNet Portal Managed Systems folder.User Response: Ensure that the OMEGAMON configuration agent is properly installed and is communicating with the CMS. Also, ensure that the name of the agent in the Managed Systems folder matches the name defined for the configured system.

Messages 279

KCF Messages

KCF0126E Your request failed because the Configuration Manager was unable to create an internal SQL request RC=request Reason=reasonExplanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0127E The configuration manager was unable to obtain configuration data from the agent RC=code Reason=reasonExplanation: A request for actual configuration information was sent to the OMEGAMON configuration agent; however, the agent did not provide the requested data; the RC and Reason fields may provide additional information.User Response: Collect the CMS and agent log files. Contact IBM Software Support.

KCF0128E Your request failed because the Configuration Manager was unable to open an internal SQL request RC=code Reason=reasonExplanation: The Configuration Manager was unable to open the internal request required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0129E Your request failed because the configured system required to communicate with the target configured system system is not currently definedExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is not currently defined within the configuration.User Response: Ensure that the intermediate system is defined correctly within the configuration.

KCF0130E Your request failed because the configured system required to communicate with the target configured system system is an indirect connectionExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is also defined as requiring an intermediate system. This is not supported.User Response: Ensure that the definition of the intermediate system does not itself require an intermediate system.

KCF0131E Your request failed because the configured system required to communicate with the target configured system system is not currently onlineExplanation: The definition for the targeted configured system indicates that the OMEGAMON configuration agent must communicate through an intermediate configured system; however, the intermediate system is not currently online.

KCF Messages


User Response: Ensure that the intermediate system is defined correctly and is running. Also ensure that the OMEGAMON configuration agent associated with the intermediate configured system is online within the CandleNet Portal Managed Systems folder.

KCF0132E Your request failed because the Configuration Manager did not receive all requested data from configuration agent agent quickly enough. Possible agent timeout.Explanation: A request for actual configuration information was made to OMEGAMON configuration agent agent; however, the agent did not return the requested information within the required time period.User Response: This problem can be caused by communication problems, or by poor performance by either the OMEGAMON configuration agent or the configured system. You can increase the amount of time allowed for the return of configuration data from the Configuration Manager Option.

KCF0133E Your request failed because the Configuration Manager could not create a new internal identifier for the objectExplanation: The Configuration Manager was unable to create the internal identifier for the new configuration object.User Response: Collect the CMS log files. Contact IBM Software Support.

KCF0134E Your request failed because the Configuration Manager was unable to create the new objectExplanation: The Configuration Manager was unable to create the new configuration object.User Response: Collect the CMS log files. Contact IBM Software Support.

KCF0135E The Configuration Manager was unable to open the configuration data baseExplanation: The Configuration database files do not exist or cannot be opened due to insufficient permissions.User Response: Collect the CMS log files, and contact IBM Software Support.

KCF0136E Because of an internal error, no objects were replicatedExplanation: An internal error occurred within the Configuration Manager, and your replication request failed.User Response: Collect the CMS log files. Contact IBM Software Support.

KCF0137E The configuration manager was unable to read from the data base log fileExplanation: The Configuration Manager was unable to read the database log file, which contains pending background actions information. The Configuration Manager will not be able to recover any background work during start up.User Response: Check that the RKCFDLOG file in CMS directory exists and has correct permission.

KCF0138E Your request failed because the Configuration Manager was unable to create an action setExplanation: The Configuration Manager was unable to build the internal resource required to perform the action.

Messages 281

KCF Messages

User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0139E Your request failed because the Configuration Manager was unable to create an action requestExplanation: The Configuration Manager was unable to build the internal resource required to perform the action.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0140E Your request failed because of an averted deadlock condition at the Candle Management ServerExplanation: A potential deadlock condition within the Configuration Manager was averted by cancelling your request.User Response: Retry the request. If the problem persists, collect the CMS log files, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0141E Your request failed because of storage shortage at the Candle Management ServerExplanation: A storage shortage condition was detected within the IBM Management Server. Your request was not processed.User Response: If possible, increase the amount of storage available to the CMS. Otherwise, collect the CMS log. Contact IBM Software Support.

KCF0142E Your request failed because of RW storage shortage at the Candle Management ServerExplanation: A storage shortage condition was detected within the Candle Management Server. Your request was not processed.User Response: If possible, increase the amount of storage available to the CMS. Otherwise, collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0143E The Configuration Manager encountered a duplicate key reading the configuration data baseExplanation: The database contains duplicate key, indicating inconsistency in the database.User Response: Collect the CMS log. Contact IBM Software Support.

KCF0144E The Discover New Resources request is not supported for this type of objectExplanation: The workstation has made a Discover new resources request to the Configuration Manager for an object other than a configured system.User Response: Collect the CMS and CandleNet Portal server log files. Restart the CandleNet Portal server. Contact IBM Software Support.

KCF0145W No new resources were discovered for configured system systemExplanation: A Discover new resources request was made for configured system system, but the Configuration Manager did not detect any actual resource that was not already defined.

KCF Messages


User Response: None.

KCF0148E The scheduled action was not performed due to a Configuration Manager restartExplanation: The Configuration Manager was shut down while scheduled action was being executed. Therefore the scheduled action failed with this error.User Response: Reschedule the action.

KCF0149E The scheduled action was not performed because the configured system for the target object was not locatedExplanation: The Configured System corresponding to the object of scheduled action was not found. This may happen if the configuration tree is now obsolete due to changes made to it while unlocked.User Response: Recycle the CMS, and reschedule the action.

KCF0150E The scheduled action was not performed because of a failure building the selection groupExplanation: The configured objects for which the scheduled action was to be performed could not be determined by the Configuration Manager.User Response: View the Scheduled action definition and ensure that the target of scheduled action still exists in the database. Reschedule the action at the object.

KCF0151E The scheduled action was disabled because of a prior execution failureExplanation: The scheduled action became disabled because of a failure during it's execution.User Response: Navigate to the Scheduled Action Status report for the scheduled action to determine what caused the problem. Correct the error, and re-enable the scheduled action.

KCF0152E You are not authorized to alter or delete global variablesExplanation: You attempted to delete or modify a global variable; however, based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the ADMIN.GLVAR security profile.

KCF0153E You are not authorized to access audit logExplanation: You attempted to access the audit log; however, based on the results of the RACROUTE REQUEST=AUTH call to the System Authorization Facility, you do not have the required access.User Response: Contact your local security administrator to provide you with access to this configuration object. You must have MODIFY access to the ADMIN.AUDIT security profile.

KCF0154E The scheduled action could not be run within the schedule windowExplanation: You had scheduled an action to run within a specific time interval, but the schedule window has now passed. This may happen if the Configuration Manager is unavailable during the schedule time window.

Messages 283

KCF Messages

User Response: Reschedule the action to run at a new time.

KCF0157E The Configuration Manager cannot open the data base log fileExplanation: The database log file could not be opened. Configuration Manager is shut down.User Response: This problem may occur if an out of space condition occurs for the database log file. If the CMS is running on z/OS, check for errors on the data set referred to by the RKCFDLOG DD statement in the CMS started task JCL. If the CMS is running on a distributed platform, ensure there is sufficient disk space for the database log file.

KCF0158E Your request failed because the Configuration Manager cannot write to the data base log fileExplanation: The configuration data base manager encountered an error writing to the data base log file; your request could not be processed, and the Configuration Manager is shut down.User Response: This problem may occur if an out-of-space condition occurs for the database log file. If the CMS is running on z/OS, check for errors on the data set referred to by the RKCFDLOG DD statement in the CMS started task JCL. If the CMS is running on a distributed platform, ensure there is sufficient disk space for the database log file.

KCF0160SE Your request failed because the base object could not be locatedExplanation: The operation you request could not be performed. The base object associated with the target object could not be located.User Response: Collect the CMS and CandleNet Portal server log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0161E An error was detected generating a product-defined objectExplanation: The Configuration Manager encountered error when Cluster Objects were being generated.User Response: Collect the CMS log, and contact IBM Software Support.

KCF0162E The scheduled action detected a validation errorExplanation: The Configuration Manager found a validation error while perform a scheduled validate action.User Response: Navigate to the Scheduled Action Status report for the scheduled action to determine what caused the problem.

KCF0163I Your validation request was scheduled the scheduled action name is actionExplanation: You requested that a validation operation be performed in the background. The Configuration Manager has created a scheduled action with the name action to perform this operation.User Response: You can track the progress of the scheduled action by viewing the 'Scheduled Action Summary' report for the target object.

KCF Messages


KCF0164I Your View Discrepancies request was scheduled the scheduled action name is actionExplanation: You requested that a View Discrepancies operation be performed in the background. The Configuration Manager has created a scheduled action with the name action to perform this operation.User Response: You can track the progress of the scheduled action by viewing the 'Scheduled Action Summary' report for the target object.

KCF0165I Your Update request was scheduled the scheduled action name is actionExplanation: You requested that an Update Actual from Defined or an Update Defined from Actual operation be performed in the background. The Configuration Manager has created a scheduled action with the name action to perform this operation.User Response: You can track the progress of the scheduled action by viewing the 'Scheduled Action Summary' report for the target object.

KCF0166I Your Delete request was scheduled the scheduled action name is actionExplanation: You requested that an Delete operation be performed in the background. The Configuration Manager has created a scheduled action with the name action to perform this operation.User Response: You can track the progress of the scheduled action by viewing the 'Scheduled Action Summary' report for the target object.

KCF0167E You cannot copy a prototype prototype that is directly descended from another prototype object sourceExplanation: You attempted to copy a prototype that is directly descended from another prototype into the defined view tree. This is not supported.User Response: You can only copy prototype objects into the defined view tree that are descended directly from Configured System Prototypes, Resource Group Prototypes, or Resource Prototypes.

KCF0168E The configuration manager cannot navigate to the object because the navigation path is emptyExplanation: You requested that the configuration product either select or open the settings for another object in the configuration. This could be the base object for the currently selected object, or it could be an object identified in the Validation report.User Response: The currently selected object may have been deleted or altered. Refresh the current tree using the Refresh pop-up menu option (for CandleNet Portal server, the Refresh Now option from the View pull-down menu), and retry the operation. If you are displaying the Validation report, close the report window and re-execute the Validate request.

KCF0206I The requested action was completed successfullyExplanation: The action that you requested was run successfully.User Response: None.

Messages 285

KCF Messages

KCF0210E The configuration manager cannot create this resource because it is dynamicExplanation: You requested that an actual resource be created from the a defined resource. However, the defined resource is dynamic, and an actual dynamic resource cannot be created by the Configuration Manager.User Response: None.

KCF0211E The requested configuration object was not foundExplanation: You entered a search request; however, there were no objects in the configuration which matched your search criteria.User Response: Reenter your search request, specifying a different search criteria.

KCF0212E Your request failed. A backup request is already in processExplanation: You requested that a backup copy of the configuration database be made; however, another backup request is currently being processed.User Response: Wait until the other backup request is complete, then reenter your request.

KCF0213E Your request failed. The configuration manager was unable to create a cursor for the database. Status= statusExplanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to open a cursor to read the contents of the database.User Response: Retry the request. If the problem persists, collect the CMS log file, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0214E Your request failed. The configuration manager was unable to write the data to the backup file. SAMRC= codeExplanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to write the contents of the database to the backup file.User Response: Ensure that there is sufficient disk space for the backup file.

KCF0215E Your request failed. The configuration manager was unable to read the database. Status= statusExplanation: You requested that a backup copy of the configuration database be made; however, the Configuration Manager was unable to read the contents of the database.User Response: Retry the request. If the problem persists, collect the CMS log file, restart the CMS and the CandleNet Portal server, and contact IBM Software Support.

KCF0216I The configuration data base was successfully backed up to fileExplanation: A backup copy of the configuration data base was successfully written to the file.User Response: None.

KCF Messages


KCF0217E You do not have the proper authorization to backup the configuration databaseExplanation: You made a request to backup the configuration database; however, your userid does not have the proper authority to perform this operation.User Response: Check with your security administrator. Your userid must have at least 'Update' access to the ADMIN.BACKUP security profile in order to backup the configuration database.

KCF0224E Name mask is too long or invalidExplanation: You entered a name mask on the Name page of the Find notebook that is either invalid, too long, or too complex.User Response: Correct the name mask, and reissue the request.

KCF0225E Database backup operation could not be completed because the configuration manager is being quiescedExplanation: You requested a backup operation of the configuration database; however, the backup operation could not be completed, because the Configuration Manager is quiescing.User Response: Restart the Configuration Manager on the CMS, and re-enter your request to backup the configuration database.

KCF0226E A fatal exception has occurred. A configuration manager thread has attempted to acquire too many locksExplanation: During the processing of your last request, a thread running in the Configuration Manager attempted to acquire more locks than is supported.User Response: Collect the CMS log files. Restart the CMS and the CandleNet Portal server. Contact IBM Software Support.

KCF0227E Cannot Create Resource in Database = Type=type, Resource=resource, Code=code Import StoppedExplanation: The Configuration Manager was unable to create a database object corresponding to the Object definition found in the import file. Import was stopped.User Response: Collect the CMS log and import file. Contact IBM Software Support.

KCF0229E Unknown Attribute Name=attribute = Value=value Import StoppedExplanation: Import file contains an attribute name that the configuration manager does not recognize. Import process was stopped.User Response: Collect the CMS log and import file. Contact IBM Software Support.

KCF0230E Unknown Data Type=type = Level=level Import StoppedExplanation: Import file contains an object definition which cannot be recognized by the Configuration Manager.User Response: Collect the CMS log and import file. Contact IBM Software Support.

Messages 287

KCF Messages

KCF0231E Data out of Sequence = Type=type, Level=level Import StoppedExplanation: The import file contains some tags that do not belong in the import file.User Response: Collect the CMS log and import file. Contact IBM Software Support.

KCF0232E Unknown object Tag tag Found Import StoppedExplanation: An XML tag in the import file was not recognized by the Configuration Manager, the import was stopped.User Response: Ensure that the CMS level is most current. Collect at CMS log, and the import file. Call IBM Software Support.

KCF0233E Your request failed. Object object is not based on a prototypeExplanation: You selected the Revert to Base Object operation for the specified object; however, the object is not based on a prototype.User Response: None; the Revert to Base Object operation does not apply to an object that is not based on a prototype.

KCF0234W No action performed. Object object has no overriding attributesExplanation: You selected the Revert to Base Object operation for the specified object; however, no action was required because the object did not contain any overriding properties.User Response: None.

KCF0238E The import file contains an invalid attribute value attribute for tag tag Import request not processedExplanation: You attempted to import a file into the configuration; however, there is an XML tag in the import file which contains an invalid value. The import file is not processed.User Response: Correct the import file, and reenter the Import request.

KCF0239E Import failed. Unable to import object into parent typeExplanation: You attempted to import a file into the configuration; however, the type of object specified within the import file is not valid for the target object. For example, an attempt was made to import a resource directly within a configured system group.User Response: Correct the import file, and reenter the Import request.

KCF0241E Invalid Import File XML has missing tagsExplanation: You attempted to import a file into the configuration; however, the XML file has an invalid structure (possibly missing end tags).Explanation: Correct the import file, and reenter the Import request.

KCF0242W Imported attribute attribute is not valid for object typeExplanation: You attempted to import a file into the configuration; however, the XML file included a tag that was inappropriate for the type of object being imported.User Response: Correct the import file, and reenter the Import request.

KCF Messages


KCF0243E Import failed. Type type cannot be imported at this level. Only import files containing configured system groups can be imported at this levelExplanation: The file being imported contains high level object definitions which cannot be children to the target object. Target object for import expects Configured System Groups as child objects.User Response: Examine the imported file to find the type of high level object being imported, and select appropriate target object for import.

KCF0251E The export MQSC cannot be performed because of a validation failure. Select validate option for object objectExplanation: Your request to export MQSC commands for the resource was not performed because the resource definition was invalid.User Response: Right click the resource and select 'Validate' option to view specific validation errors. Correct the errors and rerun the request to export MQSC commands.

KCF0252I Compare found no differencesExplanation: A request to compare two similar objects found no differences between them.User Response: None.

Messages 289

KMCRCA Messages

KMCRCA Messages

These messages take the form KMCRCAnnnx; they are written to the error log by the OMEGAMON configuration agent.

KMCRCA001W The environment variables have not been set from the registry.Explanation: This message is issued only when the OMEGAMON configuration agent is running on a Windows operating system. It indicates that the environmental variables could not be found in the registry and so will be set from the xxxENV file.System Action:Processing continues using the values from the xxxENV file.User Response:Check that the installation of the configuration agent was successful. If necessary, contact IBM Software Support.

KMCRCA002I Candle WebSphere MQ Configuration Agent Starting up. Entry = entry Object = object Build date/time = date timeExplanation: This message is issued only when the OMEGAMON configuration agent is running on the z/OS operating system at agent startup, if the Configuration tool value for Enable startup console messages was set to Y during installation. It may be used by Automation software to detect that the agent has started.System Action:Processing continues normally.User Response:None.

KMCRCA003E Connection Failed, Error=error, Queue Manager=managerNameExplanation: The OMEGAMON configuration agent was unable to establish a connection to the queue manager managerName due to error code error.System Action:Data from the queue manager will be unavailable until a connection is made.User Response:Review the WebSphere MQ cocumentation for connection error code. If necessary, contact IBM Software Support.

KMCRCA004I Successfully Connected to Queue Manager managerNameExplanation: The OMEGAMON configuration agent has successfully connected to the queue manager named managerName.User Response:None.

KMCRCA005E WebSphere MQ Open Failed with Error=openError, Queue Manager=managerName, Queue Name=queueName, Model Queue=modelQNameExplanation: The OMEGAMON configuration agent was unable to open the queue queueName on queue manager managerName due to error openError.System Action:Data from the Queue Manager will be unavailable until the queue can be opened.User Response:Review the WebSphere MQ documentation for queue open error code. If necessary, contact IBM Software Support.

KMCRCA Messages


KMCRCA006E Command Server Input Queue is not open for input on Queue Manager managerNameExplanation: The command input queue for the command server associated with queue manager managerName is not open.System Action:Data from the queue manager will be unavailable until the queue can be opened.User Response:Ensure that the command server is running. If necessary, contact IBM Software Support.

KMCRCA007W Auto create definition error: [LocalQueueManager] must precede all other definitionsExplanation: The order of control statements in the autocreate file (kmcauto.txt) is incorrect. A [LocalQueueManager] statement must be the first statement in the file.System Action:Processing of the autocreate file is terminated.User Response:Correct the order of the control statements in the kmcauto.txt file. If necessary, contact IBM Software Support.

KMCRCA008W Line ignored: lineExplanation: This message follows a previous error message regarding statements in the autocreate file (kmcauto.txt) and gives the line number within the file of the statement in error.User Response:Refer to previous messages for the precise cause of the error.

KMCRCA009W Auto create definition error: unrecognized inputExplanation: The content of a control statement in the autocreate file (kmcauto.txt) is unrecognised.System Action:Processing of the autocreate file is terminated.User Response:Correct the control statements in the kmcauto.txt file. If necessary, contact IBM Software Support.

KMCRCA010I WebSphere MQ message: message, Queue Manager: managerNameExplanation: An unexpected, or error, response message has been received from queue manager managerName.System Action:The data received is not processed; other processing continues normally.User Response:Review the WebSphere MQ documentation for the error code. If necessary, contact IBM Software Support.

KMCRCA011I Queue Manager shutdown detected for Queue Manager managerNameExplanation: The OMEGAMON configuration agent has detected that queue manager managerName is shutting down.System Action:Data from the queue manager will be unavailable until it is restarted.User Response:None.

Messages 291

KMCRCA Messages

KMCRCA012I Successfully created Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to create queue manager managerName was successful.User Response:None.

KMCRCA013I Successfully started Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to start queue manager managerName was successful.User Response:None.

KMCRCA014I Submitted endmqm command for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to stop queue manager managerName was submitted.System Action:The queue manager will shut down.User Response:None.

KMCRCA015I Successfully deleted Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to delete queue manager managerName was successful.User Response:None.

KMCRCA016I Successfully created default resources for Queue Manager managerNameExplanation: A request to the WebSphere MQ to create default resources for Queue Manager managerName was successful.User Response:None.

KMCRCA017I Successfully started command server for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to start the command server for Queue Manager managerName was successful.User Response:None.

KMCRCA018I Successfully started listener for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to start the listener for queue manager managerName was successful.User Response:None.

KMCRCA019I Successfully started trigger monitor for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to start the trigger monitor for queue manager managerName was successful.User Response:None.

KMCRCA020I Disconnecting from Queue Manager managerNameExplanation: The OMEGAMON configuration agent is closing down and has issued a disconnect from queue manager managerName.System Action:The queue manager disconnects from the configuration agent.User Response:None.

KMCRCA Messages


KMCRCA021E MQ API Error. Operation = operation CC = completion RC = reasonExplanation: An attempt to issue command operation to a queue manager through the standard interface has terminated with completion code completion and reason code reason.System Action:Data from the queue manager for this command is unavailable.User Response:Review the WebSphere MQ documentation for the completion and reason codes. If necessary, contact IBM Software Support.

KMCRCA022E Error accessing queue queueName Operation= operation CC = completion RC = reasonExplanation: An attempt to perform an action operation on queue queueName has terminated with completion code completion and reason code reason.System Action:Data from the queue manager for this command is unavailable.User Response:Review the WebSphere MQ documentation for the completion and reason codes. If necessary, contact IBM Software Support.

KMCRCA023E Error allocating new storage for resourceExplanation: The OMEGAMON configuration agent has encountered an error while attempting to allocate memory for a new resource resource.System Action:The configuration agent shuts down.User Response:Make more memory available to the OMEGAMON configuration agent, and restart it.

KMCRCA024I Monitoring ended because of event: eventExplanation: The OMEGAMON configuration agent has encountered an event, event, which is causing it to shut down. Examples of events include:

Alarm clockCPU time limit exceededCtrl-Break DetectedCtrl-C DetectedEMT InstructionEnd ProcessFile size limit exceededFloating Point ExceptionHangupInput data has been stored into the HFT monitor mode ring bufferInteractive stopInvalid InstructionMigrate ProcessMonitor AbortedMQ Manager QuiescingParameter not valid to subroutineProgram TerminatedProgramming exceptionQuitSecure attention key

Messages 293

KMCRCA Messages

Specification ExceptionSystem crash imminentVirtual time alarmWrite on a pipe when there is no receiving process

System Action:The configuration agent shuts down.User Response:Review the event that caused the OMEGAMON configuration agent to shut down, and take any action required to correct it. If necessary, contact IBM Software Support.

KMCRCA025E exception Exception ThrownExplanation: The OMEGAMON configuration agent has encountered an exception, exception, that is causing it to shut down. Examples of events include:

Bad Command from PCF headerBad EventOpenOption from PCFBad MQ API Return CodeBad MQOpenQueueBad PCFMessage No CorrelId definedBad PCFMessage No MsgId definedBad PCFMessage No MsgTag definedBad PCFMessage No Queuename definedBad ServerChannelMask creation failedEventQueueSet creation failedExternal Signal ReceivedMemory Allocation FailureMessageManQueue creation failedMQInterface creation failedMQOpenQueue creation failedPCFMessage OverflowPCFMessageIterator creation failedQueueMask creation failedServerRequestProcessor creation failedSystemCommandServer creation failed

System Action:The configuration agent shuts down.User Response:Review the exception that caused the OMEGAMON configuration agent to shut down, and take any action required to correct it. If necessary, contact IBM Software Support.

KMCRCA026I Successfully started channel initiator for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to start the channel initiator for queue manager managerName was successful.User Response:None.

KMCRCA Messages


KMCRCA027I Connected to remote Queue Manager remoteManagerName through Queue Manager managerNameExplanation: The OMEGAMON configuration agent has successfully connected to the remote queue manager named remoteManagerName through the queue manager named managerName.User Response:None.

KMCRCA028I Successfully stopped listener for Queue Manager managerNameExplanation: A request to the OMEGAMON configuration agent to stop the listener for queue manager managerName was successful.User Response:None.

KMCRCA029I An unresolved account has been detected in the list of authorization attributes for resource: resource resource type: type and it will be ignoredExplanation: While the OMEGAMON configuration agent was receiving authorization data from a queue manager, an unresolved account was reported for resource resource of type type.System Action:The account is ignored. Processing continues.User Response:Check the autorized accounts in the queue managers to determine where the unresolved account exists. If necessary, contact IBM Software Support.

KMCRCA030I name Queue Name for user specified model queue queueName is too long, Will use system model queue insteadExplanation: The queue name name used in the KMC_RQMODEL environmental variable, used to create the agent reply queue, is too long.System Action:The system model queue is used instead.User Response:Change the queue name in the environment variable KMC_RQMODEL to a valid name.

KMCRCA031I Failed to open agent reply queue with user specified model queue=queueName on Queue Manager managerName, Using system model queue to open agent reply queueExplanation: An attempt to open the agent reply queue using the model queue name specified in the KMC_RQMODEL environmental variable queueName on queue manager managerName has failed.System Action:The system model queue is used instead.User Response:Ensure that the model queue name given in the KMC_RQMODEL environmental variable is valid and that it exists on the queue manager referenced.

Messages 295

KCFCM Messages

KCFCM Messages

These messages take the form KCFCMnnnx; they are written to the error log by the Configuration Manager.

KCFCM001I Candle Configuration Manager startup completeExplanation: The Configuration Manager has completed initialization successfully.System Action: The Configuration Manager has initialized all of its internal tasks and is ready to begin accepting requests.User Response: None.

KCFCM002E Unable to open configuration databaseExplanation: The Configuration Manager was unable to open the RKCFAPLD database containing the configuration data.System Action: The Configuration Manager terminates.User Response: Search the CMS log, looking for other messages relating to this file, to determine the exact reason that the file could not be opened. Verify the presence of the file. If necessary, contact IBM Software Support.

KCFCM003E Unable to load DLL for Application applicationExplanation: The Configuration Manager was unable to load the application-specific library identified by application. The Configuration Manager cannot manage configuration data associated with this application without loading this library.System Action: If this is the only application-specific library associated with the configuration product, the Configuration Manager terminates.User Response: Search the CMS log, looking for other messages relating to this library, to determine the exact reason that the library could not be loaded. Verify the presence of the library. If necessary, contact IBM Software Support.

KCFCM004E Internal Error intError:(intType)- Function function - RC returnCodeExplanation: An internal error has occurred in the Configuration Manager. The internal error type is interror; the function that the error was detected in is function; the return code is returnCode.System Action: The currently active function ends prematurely.User Response: Contact IBM Software Support.

KCFCM005E Error from RCA. Function = function RC retCode(retcode) Reason reason (reason) Name = agentExplanation: An error was detected from a Configuration Agent. The function that detected the error is function. The return code and reason code are retcode and reason, respectively. The name of the Configuration Agent is agent.System Action: The currently active function ends prematurely.User Response: If the return code and reason code represent an application-specific return code (such as from WebSphere MQ), then look them up in the IBM-provided manual.

KCFCM Messages


KCFCM006E Unsupported managed system type mgsysType received from RCA agent - ignoredExplanation: The Configuration Agent agent has reported its configured system type as mgsysType - this type is ignored and unsupported.System Action: The Configuration Agent is ignored.User Response: Make sure that the Configuration Agent identified by agent is fully supported by the configuration applications you have installed in the CMS.

KCFCM008E database version version incompatible with configuration managerExplanation: The configuration database has been altered by a more recent version (version) of the Configuration Manager, which is not compatible with the version of the product you are now trying to run.System Action: The Configuration Manager can not continue initialization.User Response: You must either run the more recent version of the Configuration Manager, or you must restore the configuration data base files from a backup copy that was created prior to being touched by the more recent version.

KCFCM009I Configuration database successfully loadedExplanation: The configuration database has been successfully loaded into storage. The configuration product is ready for use.User Response: None.

KCFCM012I Unable to delete resource group prototype resource - it is in useExplanation: A user made an attempt was made to delete resource group prototype identified by resource; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM013I Unable to delete resource prototype resource - it is in useExplanation: A user made an attempt was made to delete resource prototype identified by resource; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM014I Unable to delete configured system prototype resource - it is in useExplanation: A user made an attempt was made to delete the configured system prototype identified by resource; however, it cannot be deleted because it is in use.System Action: The object is not deleted.User Response: Make sure that the prototype is not in using prior to attempting to delete it.

KCFCM015E RCA Request Retry Timeout for function functionExplanation: A request was sent to a Configuration Agent, but the agent did not respond with the requested data within the current agent timeout limit.System Action: The currently active function ends prematurely.

Messages 297

KCFCM Messages

User Response: Examine the CMS and agent logs to determine why the Configuration Agent did not respond.

KCFCM016E Cannot bring system system online; thru system thruSystem not foundExplanation: The Configuration Manager cannot bring configured system system online, because the through configured system, thruSystem, cannot be located.System Action: The currently active function ends prematurely.User Response: Correct the definition of the configured system to reference a valid through configured system.

KCFCM017E Cannot bring system system online; thru sys thruSystem not onlineExplanation: The Configuration Manager cannot bring configured system system online, because the through configured system, thruSystem, is not online.System Action: The currently active function ends prematurely.User Response: Ensure that the through configured system is active and available.

KCFCM018E Cannot bring system system online; thru sys thruSystem not direct attachExplanation: The Configuration Manager cannot bring configured system system online, because the through configured system, thruSystem, is not defined as directly attached.System Action: The currently active function ends prematurely.User Response: Change the definition of configured system system so that is either directly attached, or is attached 'through' a configured system which is directly attached.

KCFCM019E Cannot bring system system online; required RCA agent not availableExplanation: The Configuration Manager cannot bring configured system system online, because the Configuration Agent agent is not active.System Action: The currently active function ends prematurely.User Response: Start the Configuration Agent agent.

KCFCM020E Unable to connect with configured system systemExplanation: The Configuration Agent was unable to connect with the configured system identified by system.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to connect with the configured system.

KCFCM021I Successfully connected to configured system systemExplanation: The Configuration Agent has established a connection with the configured system system.User Response: None.

KCFCM022I Successfully started and connected to configured system systemExplanation: The Configuration Agent has started configured system system and established a connection with it.User Response: None.

KCFCM Messages


KCFCM023E Unable to start configured system systemExplanation: The Configuration Agent was unable to start the configured system identified by system.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to start the configured system.

KCFCM024I Successfully created and connected to configured system systemExplanation: The Configuration Agent has created and started configured system system and established a connection with it.User Response: None.

KCFCM025E Unable to create configured system systemExplanation: The Configuration Agent was unable to create the configured system identified by system.System Action: The currently active function ends prematurely.User Response: Examine the agent log to determine why the agent was unable to create the configured system.

KCFCM026I Successfully discovered configured system systemExplanation: As a result of a Discover request, the Configuration Manager discovered the configured system identified by system.System Action: A definition for the configured system is added to the configuration database.User Response: None.

KCFCM027I Discovered duplicate system systemExplanation: As a result of a Discover request, the Configuration Manager discovered the configured system identified by system; however, a definition for this configured system already exists in the configuration database.System Action: The discovered configured system definition is ignored.User Response: None.

KCFCM028E Maximum number of resourceType objects generated, cannot create new objectExplanation: The maximum number of objects of the type specified by resourceType has been created. The new object can not be created.System Action: The object definition is ignored.User Response: Contact IBM Software Support.

KCFCM029E Memory Allocation Error in Function:functionExplanation: There is not enough memory for the allocation made in function function.System Action: The currently active function ends prematurely. Under some circumstances, the Configuration Manager may shut down.User Response: Review the memory allocation parameters before calling IBM Software Support.

Messages 299

KCFCM Messages

KCFCM030W KEY1 operation Failed Function:function File=file Status=status Reason=reasonExplanation: The KEY1 database service (associated with the internal product-provided type configuration database) detected an error in the processing of one of the configuration files. operation identifies the attempted operation; function identifies the function which detected the error; file contains the name of the file; status and reason contain the status and reason.System Action: The currently active function ends prematurely. Under some circumstances, the Configuration Manager may shut down.User Response: Contact IBM Software Support.

KCFCM031E DataBase Bad Work Unit Status statusExplanation: In attempting to migrate a pre-Version 350 configuration database, the Configuration Manager detected a database work unit with bad status status.System Action: Initialization of the Configuration Manager ends abnormally.User Response: Contact IBM Software Support.

KCFCM032E Handle handle from selection group no longer found in configurationExplanation: A user requested an action against a set of configuration objects, however one of the members of the set, identified by handle, could not be located in the configuration.System Action: The currently active function ends prematurely.User Response: Re-execute the requested action, specifying only existing configuration objects.

KCFCM033I Candle Configuration Manager shutdown startedExplanation: The Configuration Manager has begun the process of shutting itself down. Message KCFCM034I should follow shortly indicating that the shutdown has completed.System Action: Shutdown of the Configuration Manager proceeds.User Response: None.

KCFCM034I Candle Configuration Manager shutdown completeExplanation: The Configuration Manager has completed shutdown processing.System Action: The Configuration Manager is no longer running.User Response: None.

KCFCM035I Configuration Agent agent is now onlineExplanation: The Configuration Agent identified by agent is now connected to the Configuration Manager.User Response: None.

KCFCM036I Configuration Agent agent is now offlineExplanation: The Configuration Agent identified by agent is no longer connected to the Configuration Manager.

KCFCM Messages


User Response: If the Configuration Agent was not taken down deliberately, scan the agent log to determine why it is no longer communicating with the CMS. If necessary, contact IBM Software Support.

KCFCM037E exception Exception caught in Unit unit Function functionExplanation: A program exception identified by exception was detected in the Configuration Manager, within unit unit and function function.System Action: Diagnostic information is written to the CMS log. The Configuration Manager is shutdown.User Response: Contact IBM Software Support.

KCFCM038I Configuration quiesce startedExplanation: The Configuration Manager has started to quiesce itself in preparation for a shutdown. The shutdown was either requested, or resulted from an unrecoverable error condition.System Action: The Configuration Manager quiesces all activity in preparation for a shutdown. Message KCFCM033I should soon appear, indicating that shutdown processing has begun.User Response: If you believe that the Configuration Manager is shutting down because of an error, search through the prior entries in the CMS log, looking for other messages indicating the nature of the error.

KCFCM040I Sucessfully loaded application library libname for application Address = addressExplanation: This message indicates that the Configuration Manager has successfully loaded the application-specific library identified by application.User Response: None.

KCFCM041I database error detected in function - configuration quiesce initiatedExplanation: The Configuration Manager has detected an unrecoverable database error.System Action: The Configuration Manager is shutdown.User Response: Contact IBM Software Support.

KCFCM042I Auto Import successful for file fileExplanation: At startup time, the Configuration Manager detected the presence of the configuration import file file, and has read and imported the data.System Action: The data from the import file was read and saved in the configuration data base.User Response: None.

KCFCM043E Error error locating import filesExplanation: At startup time, the Configuration Manager was unable to locate the configuration import files.System Action: Initialization of the Configuration Manager proceeds without the import data.

Messages 301

KCFCM Messages

User Response: If your CMS is running on z/OS, ensure that the RKANDATV DD statement is present in the started task JCL, and that it identifies a proper partitioned dataset. On distributed platforms, ensure that the RKCFCDI subdirectory is defined.

KCFCM044E Unable to open import file file - error code errorExplanation: At startup time, the Configuration Manager detected the presence of the configuration import file file; however, it encountered a problem attempting to read the data.System Action: The import file is ignored.User Response: Determine why the Configuration Manager was unable to open the import file. Restart the Configuration Manager in order to reinitiate the import process.

KCFCM045E Unable to open export file file - error code errorExplanation: When attempting to export data from the Configuration managers database, an error error was encountered while trying to open the export file file.System Action: The export function is terminated.User Response: Review the error against the error for the platform the process was executing on. If necessary, contact IBM Software Support.

KCFCM046E Unable to write export file file - error code errorExplanation: When attempting to export data from the Configuration managers database, an error error was encountered while trying to write to the export file file.System Action: The export function is terminated.User Response: Review the error against the error for the platform the process was executing on. If necessary, contact IBM Software Support.

KCFCM047I Export requested to file fileExplanation: The Export requested to file file has started.User Response: None.

KCFCM048I Export successful to file fileExplanation: The Export requested to file file has ended.User Response: None.

KCFCM049E Export failed to file file - error code errorExplanation: The Export requested to file file has failed to complete successfully due to error error.System Action: The export function is terminated.User Response: Review the error against the error for the platform the process was executing on. If necessary, contact IBM Software Support.

KCFCM050E Dynamic allocation of export file file failed. rc=error reason=reason info=infoExplanation: When attempting to export data from the Configuration Managers database, an error error, and reason reason was encountered while trying to dynamically allocate to the export file file.System Action: The export function is terminated.

KCFCM Messages


User Response: Review the error against the error for the platform the process was executing on. If necessary, contact IBM Software Support.

KCFCM051I count configured systems autodiscovered from agent agentExplanation: Auto-discovery processing was performed for the Configuration Agent identified by agent. count new configured systems were discovered.System Action: The automatically discovered configured systems were added to the configuration database.User Response: None.

KCFCM052E Exception Type = exceptionExplanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the type of exception. This is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact IBM Software Support.

KCFCM053E Exception Address = addressExplanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the memory address where the exception took place. This is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact IBM Software Support.

KCFCM054E Storage Access Address = addressExplanation: This message is produced after an exception condition has occurred within the Configuration Manager. This message indicates the address of the memory being accessed if a storage access violation is detected. This is one of several diagnostic messages that appear in the CMS log after an exception.User Response: Contact IBM Software Support.

KCFCM055E Configuration Agent did not provide requested data for configured system system - probable timeoutExplanation: A request was sent to a Configuration Agent for the configured system identified by system, but the agent did not respond with the requested data.System Action: The currently active function ends prematurely.User Response: This was likely caused by a timeout condition in the communication between the agent and the CMS. Examine the CMS and agent logs to determine why the Configuration Agent did not respond.

KCFCM056I Configuration Manager External security is disabledExplanation: At startup time, the Configuration Manager determined that the external security feature is disabled.System Action: No security validation checks will be performed by the Configuration Manager.User Response: None.

Messages 303

KCFCM Messages

KCFCM057I Configuration Manager External security is enabledExplanation: At startup time, the Configuration Manager determined that the external security feature is enabled, using the z/OS System Authorization Facility (SAF).System Action: Access to configuration objects by users of the configuration product will be subject to security checks.User Response: None.

KCFCM058E Persistent Data Store Failure in function function - Error Code errorExplanation: An error status was returned from the CMS Persistent Data Store facility (PDS). function identifies the function that detected the error. error indicates the error code that was returned from the PDS facility.System Action: Audit log records can not be read from or written to the Persistent Data Store.User Response: Investigate why the PDS is having problems by examining the log. If necessary, contact IBM Software Support.

KCFCM059E Unable to open Audit Log file fileExplanation: The Configuration Manager was unable to open the audit log file identified by file.System Action: Audit log records cannot be read from or written to the audit log file.User Response: Investigate why the Configuration Manager is having problems accessing the log file by examining the log. If necessary, contact IBM Software Support.

KCFCM060E Error writing to Audit Log file fileExplanation: The Configuration Manager was unable to write to the audit log file identified by file.System Action: Audit log records cannot be written to the audit log file.User Response: Investigate why the Configuration Manager is having problems accessing the log file by examining the log. If necessary, contact IBM Software Support.

KCFCM061E Write to Audit Log file resumed. Missed record count=countExplanation: A new audit log file has been created. count shows the number of Audit log records that have not been written during the allocation process.User Response: None.

KCFCM062I Candle Configuration Manager Starting up. Entry = entry Object = object Build date/time = date timeExplanation: This message is written when the Configuration Manager is started within the CMS. Initialization of the Configuration Manager proceeds.User Response: None. This message contains diagnostic information that may be of value to IBM Software Support.

KCFCM Messages


KCFCM063E Candle Configuration Manager Shutting down - no configuration applications definedExplanation: At startup time, the Configuration Manager detected that there were no valid configuration application libraries to load.System Action: The Configuration Manager shuts down.User Response: Examine the CMS log to determine why no configuration application libraries were available to the Configuration Manager. If necessary, contact IBM Software Support.

KCFCM064E Unable to open database log file RC = fileExplanation: The configuration application was unable to open the database log file RKCFDLOG.System Action: The Configuration Manager shuts down.User Response: Determine why the Configuration Manager was unable to open the RKCFDLOG file. If necessary, contact IBM Software Support.

KCFCM065E Failure writing to database log file RC = returnExplanation: The configuration application was unable to write to the database log file RKCFDLOG.System Action: The Configuration Manager shuts down.User Response: Determine why the Configuration Manager was unable to open the RKCFDLOG file. If necessary, contact IBM Software Support.

KCFCM066E Failure recovering configuration database RC = returnExplanation: At startup time, an error occurred while attempting to recover interrupted database work units.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM067I Database work unit recovery started for unitExplanation: At startup time, the Configuration Manager has found a database work unit in a semi-committed status.System Action: The Configuration Manager attempts to recover and commit the work unit. Message KCFCM068I will follow in the CMS log, when recovery for all work units has completed.User Response: None.

KCFCM068I Database work unit recovery completed for all work unitsExplanation: The Configuration Manager has completed recovery processing for all semi-committed work units.System Action: Initialization of the Configuration Manager proceeds.User Response: None.

KCFCM069E Database work unit recovery failed - return code = returnExplanation: The Configuration Manager was unable to perform recovery processing on the semi-committed work unit due to the error code identified by return.System Action: The Configuration Manager shuts down.

Messages 305

KCFCM Messages

User Response: Contact IBM Software Support.

KCFCM070I Database sucessfully migrated from pre-V350 systemExplanation: Version 350, and higher of the Configuration Manager is being run for the first time, and has successfully migrated the configuration data from pre-version 350 format.System Action: Initialization continues.User Response: None.

KCFCM071E Failure migrating database from pre-V350 system - return code = returnExplanation: An error has occurred migrating the data from a pre-version 350 configuration database.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM072E Unable to repair configuration database RC = returnExplanation: The KCF_REPAIR environmental variable was set to a value of YES, indicating that the Configuration Manager should repair the configuration database; however, an error was encountered, and the database could not be repaired.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM073I Configuration database successfully repairedExplanation: The KCF_REPAIR environmental variable was set to a value of YES, indicating that the Configuration Manager should repair the configuration database; the database was successfully repaired.System Action: Initialization continues.User Response: None.

KCFCM074E Duplicate Key detected in configuration databaseExplanation: The Configuration Manager has encountered a duplicate key in the configuration data base. Duplicate keys are not allowed.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support. If you have a recent backup of the configuration database, you might consider restoring from this backup.

KCFCM075E Unable to open backup file file return code = codeExplanation: You requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to open the backup file.System Action: The request to backup the configuration database is not completed.User Response: On z/OS, the backup file must refer to a predefined, sequential data set. Ensure that this data set exists. Otherwise, ensure that a valid file name is specified.

KCFCM Messages


KCFCM076E Unable to open backup secondary cursor. Status = statusExplanation: The user has requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to create a KEY1 cursor for reading the configuration data base.System Action: The request to backup the configuration database is not completed.User Response: Contact IBM Software Support.

KCFCM077E Browse for backup failed. Status = statusExplanation: The user has requested that a backup of the configuration database be taken. However, the Configuration Manager was unable to read the configuration data base.System Action: The request to backup the configuration database is not completed.User Response: Contact IBM Software Support.

KCFCM078I Backup successful to file fileSystem Action: The requested backup operation was completed successfully.User Response: None.

KCFCM079W Memory quiesce mode enteredExplanation: The amount of heap storage used by the Configuration Manager has exceeded the value of the KCF_HEAP_QUIESCE_VALUE environmental variable.System Action: The Configuration Manager attempts to release storage associated with inactive configuration objects. This could cause response time delays in servicing future requests, as those configuration objects will have to be loaded back in from the database.User Response: Ensure that the KCF_HEAP_QUIESCE_VALUE is set to an appropriate value. If this value is too small, it can cause response time problems.

KCFCM080I Memory quiesce mode exitedExplanation: The amount of heap storage used by the Configuration Manager is now less than the value of the KCF_HEAP_QUIESCE_VALUE environmental variable, indicating that the Configuration Manager is no longer in memory quiesce mode.System Action: Configuration storage management resumes normal mode.User Response: None.

KCFCM081E Unable to create cursor for alternate index. Code = errorExplanation: The Configuration Manager was unable to create a KEY1 cursor for accessing the RKCFAPLA file.System Action: The Configuration Manager reconstructs the contents of the RKCFAPLA file.User Response: Contact IBM Software Support.

Messages 307

KCFCM Messages

KCFCM082E Unable to create sequential cursor for data base. Code = errorExplanation: The Configuration Manager was unable to create an alternate KEY1 cursor for accessing the configuration data base.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM083E Unable to do sequential read from data base. Code = errorExplanation: The Configuration Manager was unable to read from the configuration database in an effort to create the RKCFAPLA file.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM084I Alternate index RKCFAPLA was successfully builtExplanation: The RKCFAPLA alternate index file was successfully built.User Response: None.

KCFCM085E Alternate index RKCFAPLA could not be rebuilt - status = statusExplanation: The Configuration Manager failed in its attempt to rebuild the RKCFAPLA file.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support.

KCFCM086I count records in alternate index RKCFAPLA were successfully deletedExplanation: In preparation for rebuilding the RKCFAPLA file, count records were deleted from the file. This is a normal part of rebuilding this file.User Response: None.

KCFCM087E Missing Key detected in configuration databaseExplanation: The Configuration Manager has encountered a missing record in the configuration data base.System Action: The Configuration Manager shuts down.User Response: Contact IBM Software Support. If you have a recent backup of the configuration database, you might consider restoring from this backup.

KCFCM088I Prototype usage data successfully rebuild for all objectsExplanation: The KCF_REBUILD_PROTO_REFS environmental variable was set to a value of YES, indicating that prototype usage information should be rebuilt.System Action: The Configuration Manager has successfully completed rebuilding prototype usage information.User Response: None.

KCFCM089E Configuration Name Service KEY1 error. Status = status Reason = reasonExplanation: A KEY1 error was encountered by the configuration name service. status and reason indicate the status and reason codes, respectively.System Action: The configuration name service is shutdown. The Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Ensure that the RKCFAPLN file is defined and available to the CMS. If necessary, contact IBM Software Support.

KCFCM Messages


KCFCM090E Configuration Name Service shutdown abnormally, rc=rcExplanation: The configuration name service was shutdown abnormally.System Action: The configuration name service is shutdown. The Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Scan the CMS log, looking for other messages indicating why the name service has shut down If necessary, contact IBM Software Support.

KCFCM091E Configuration Name Service KEY1 open failureSystem Action: The configuration name service was unable to open the RKCFAPLN file.System Action: The configuration name service is shutdown. The Configuration Manager proceeds without it, but with possibly degraded performance.User Response: Ensure that the RKCFAPLN file is defined and available to the CMS. If necessary, contact IBM Software Support.

KCFCM092I Database database KEY1 Function function. Status = status Reason = reasonExplanation: An informational event has occurred in the KEY1 database processor.System Action: Processing continues.User Response: None.

KCFCM093W No database pre-v350 Database found - no conversion will be attemptedExplanation: On startup, the Configuration manager was unable to locate any pre-version 350 database.System Action: Initialization continues.User Response: None.

KCFCM094E Unable to locate PDS Table table, ensure that Persistant Datastore has been installed/initialized.Explanation: The Configuration Manager is unable to locate the Persistent Datastore Table table. These tables are created at install time if the Persistent Datastore Option is configured.System Action: Persistent Datastore information will not be recorded.User Response: Check that the Persistent Datastore Option was requested at installation time.

KCFCM095E DB2 Error occurred in functionExplanation: An error has occurred in the DB2 Database Processor function function. The following messages will give more details.System Action: Depends on the content of the following messages.User Response: Review the log for following messages giving further details about the error.

KCFCM096E DB2 SqlState=state, SqlCode=errorExplanation: A DB2 database request terminated with SQLState SqlState and SQLCode SqlCode.System Action: The current action against the DB2 datbase is terminated.

Messages 309

KCFCM Messages

User Response: Review the DB2 Product Manuals for more information about the return codes that were issued. If necessary, contact IBM Software Support.

KCFCM097E DB2 CLI Return Code return at line line from Function 'function'Explanation: A DB2 SQL request has failed with return code return at line line in Function function.System Action: The current action against the DB2 datbase is terminated.User Response: Review the DB2 Product Manuals for more information about the return code that was issued. If necessary, contact IBM Software Support.

KCFCM098E DB2 errorExplanation: This message presents informational text which was retrieved from the SQL error system about an SQL Error that has occurred while processing a request.System Action: The current action against the DB2 datbase is terminated.User Response: Review the DB2 Product Manuals for more information about the return code that was issued. If necessary, contact IBM Software Support.

KCFCM099E DB2 Environment Error; Unable to open Database, TerminatingExplanation: Environmental variables have been set indicating that the DB2 database, as opposed to the KEY1, database is to be used. This message would be preceeded by a message indicating the cause of the database not being opened.System Action: Initialization of the Configuration Manager is terminated.User Response: Review the message log for further information about this error and take any corrective action necessary. If necessary, contact IBM Software Support.

Windows Event Log Messages


Windows Event Log Messages

OverviewWhen the OMEGAMON XE for WebSphere MQ configuration 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.)

ProcedureTo 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 loggedThe following messages (when the condition occurs) appear in the application event log.

Note: The Event ID number corresponds to the KMC message number.

Event ID Severity Symbolic NameMessage Number

00300 Error CONNECT_2_QMGR_FAILED KMCRCA003E

00400 Informational EVT_AGENT_CONNECT_SUCCESSFUL KMCRCA004I

00500 Error EVT_AGENT_OPEN_FAILED KMCRCA005E

00600 Error EVT_COMMAND_SERVER_DOWN KMCRCA006E

01100 Informational EVT_QMGR_SHUTDOWN KMCRCA011I

02000 Informational EVT_QMGR_DISCONNECT KMCRCA020I

02100 Error EVT_MQ_API_ERROR KMCRCA021E

02200 Error EVT_MQ_QUEUE_ERROR KMCRCA022E

02300 Error EVT_NEW_ALLOC_FAILED KMCRCA023E

02400 Informational EVT_EXTERNAL_SIGNAL KMCRCA024I

02500 Error EVT_EXCEPTION_THROWN KMCRCA025E

Problem Determination 311

Problem Determination

IntroductionThis section contains some problem determination tips associated with IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. This information is a quick reference designed to address the most common problems.

Appendix contentsProblem Determination Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312The Environment File Used by this Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

C

Problem Determination Tips



This table describes common problems and offers possible solutions. Your solution may be one or more of the options listed.

Symptom Solution

I cannot see the Configuration view. � Ensure that your CandleNet Portal user ID has the Navigator Configuration view as an Assigned View. See “Getting Started” on page 18.

� It is possible that this product is not properly installed. See “Getting Started” on page 18.

I cannot enable update mode. � Ensure that your CandleNet Portal user ID has modify WebSphere MQ Configuration permission. See “Getting Started” on page 18.

I am unable to create new objects or add information to settings lists.

� Ensure you are in Update mode. See “Entering Update Mode” on page 37.

� Ensure that you have appropriate WebSphere MQ permissions on the object.

� Ensure that the WebSphere MQ command server is running for the queue manager you are attempting to configure.

After running the Discover feature, there are no new queue managers visible in the defined view tree.

� Refresh the Defined View.� Ensure the configuration agent is online.

After running the Discover feature, new queue managers appear but there are no associated resources in the resource group.

The Discover feature only creates resource objects for active queue managers. See “Discovering Your Existing WebSphere MQ Configuration” on page 40. � Ensure the Discover Lite product option is disabled.� Refresh the Defined View.� Ensure that the queue manager and the command server

are both running. Use one of the following options:– Manually start the queue manager and manually start

the command server. Run the Discover feature again.– Open the queue manager settings list, expand the

Auto Start section, select the Auto start check box.Note: You must start the queue manager and the command server before running the Discover feature.

Hint: Use the Auto start option to automatically start the queue manager and the command server.

– Open the queue manager settings list, expand the Auto Start section, click Auto start.



The Update defined from actual operation does not update the defined view tree.

� Refresh the Defined View.� Ensure you have appropriate CandleNet Portal user

authority. � Ensure the configuration agent is online.� Ensure that the queue manager and the command server

are both running. Note: You must start the queue manager and the command server before you run the Update defined from actual operation.



The Update actual from defined operation does not update WebSphere MQ.

� Ensure that defined objects are valid.– Right-click the object you want to validate, select

Validate. The Discrepancy Display lists the corrections you need to make. Run the Update actual from defined operation again.

Note: You must start the queue manager and the command server before you run the Update actual from defined operation.



Updates or changes made to prototypes are not reflected in the “based on” sections of objects in the Defined View.

� Refresh the Defined View.

Unwanted persistent queues (named in the form KMC.IRA.V*) remain after the queue manager is recycled.

This behavior can be changed by setting an environment variable. See “The Environment File Used by this Agent” on page 314.

Symptom Solution

The Environment File Used by this Agent



About the environment fileIn general, each OMEGAMON Configuration Agent for WebSphere MQ on each host is assigned its own environment file as part of the installation and configuration process. This environment file is generally named KMCENV. In a z/OS environment, the configuration agent shares an environment file named KxxENV where xx is the two-character component code of the first IBM Tivoli OMEGAMON component installed and configured. For example, when the configuration agent is installed and configured in the Candle Management Server address space, it uses the KDSENV file that is a member of the &RHILEV..&SYS..RKANPAR library.

Normally, there is no need to edit the environment file. You may be instructed to do so by IBM Software Support in the event of a problem. One known case in which you may want to edit the environment file is described in this section.

Customizing reply queue defaults for this agentYou may want to edit the environment file if you experience the following problem: Unwanted persistent queues (named in the form KMC.IRA.V*) remain after the queue manager is recycled.

Reply queue defaults for this agent

By default, if you specify nothing, the OMEGAMON Configuration Agent for WebSphere MQ uses the following WebSphere MQ reply queues as models for reply queues it creates:

� On z/OS:

SYSTEM.COMMAND.REPLY.MODEL

� On non-z/OS

SYSTEM.MQSC.REPLY.QUEUE

By default, this configuration agent uses a prefix of the following form for reply queues it creates:

KMC.IRA.Vnnn.QUEUE

where nnn is a number. (This prefix can be customized using the Agent Queue Prefix field in the Manager section of the Queue Manager settings list.)

Using KMC_RQMODEL to change reply queue defaults for this agent

The KMC_RQMODEL environment variable specifies the name of the queue that the configuration agent uses as a model for reply queues it creates. You may need to specify this variable if your site changed, to persistent, the default persistence of the WebSphere MQ queue the agent normally uses as a model for reply queues (described above).

If the model queue used to create the reply queue is persistent, then the configuration agent's reply queues are created to be persistent and these queues (named in the form KMC.IRA.V*) will remain after the queue manager is recycled. To correct this problem,



create another model queue (say, TEMPMODELQ) with a default persistence of "Not Persistent" and in the KMCENV file specify the KMC_RQMODEL=TEMPMODELQ where TEMPMODELQ is the name of a model queue that has the default characteristics of the WebSphere MQ queue the agent normally uses as a model for reply queues.

Once you specify the model queue using the KMC_RQMODEL environment variable, then the default model queues (described in “Reply queue defaults for this agent” on page 314) are not used. If the queue you specify for KMC_RQMODEL cannot be found, then the following queue is used as a model:

system.default.model.queue



Support Information 317

Support Information

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:

� “Searching knowledge bases” on page 317

� “Obtaining fixes” on page 318

� “Receiving weekly support updates” on page 318

� “Contacting IBM Software Support” on page 319

Searching knowledge basesYou can search the available knowledge bases to determine whether your problem was already encountered and is already documented.

Searching the information center

IBM provides extensive documentation that can be installed on your local computer or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, and reference information.

Searching the Internet

If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem.

To search multiple Internet resources for your product, use the Web search topic in your information center. In the navigation frame, click Troubleshooting and support > Searching knowledge bases and select Web search. From this topic, you can search a variety of resources, including the following:

� IBM technotes

� IBM downloads

� IBM Redbooks®

� IBM developerWorks®

� Forums and newsgroups

� Google

D


Obtaining fixesA product fix might be available to resolve your problem. To determine what fixes are available for your IBM software product, follow these steps:

1. Go to the IBM Software Support Web site at (http://www.ibm.com/software/support).

2. Click Downloads and drivers in the Support topics section.

3. Select the Software category.

4. Select a product in the Sub-category list.

5. In the Find downloads and drivers by product section, select one software category from the Category list.

6. Select one product from the Sub-category list.

7. Type more search terms in the Search within results if you want to refine your search.

8. Click Search.

9. From the list of downloads returned by your search, click the name of a fix to read the description of the fix and to optionally download the fix.For more information about the types of fixes that are available, IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updatesTo receive weekly e-mail notifications about fixes and other software support news, follow these steps:

1. Go to the IBM Software Support Web site at http:/www.ibm.com/software/support.

2. Click My Support in the upper right corner of the page.

3. If you have already registered for My Support, sign in and skip to the next step. If you have not registered, click register now. Complete the registration form using your e-mail address as your IBM ID and click Submit.

4. Click Edit Profile.

5. In the Products list, select Software. A second list is displayed.

6. In the second list, select a product segment, for example, Application servers. A third list is displayed.

7. In the third list, select a product sub-segment, for example, Distributed Application & Web Servers. A list of applicable products is displayed.

8. Select the products for which you want to receive updates, for example, IBM HTTP Server and WebSphere Application Server.

9. Click Add products.

10. After selecting all products that are of interest to you, click Subscribe to email on the Edit profile tab.

11. Select Please send these documents by weekly email.

http://www.ibm.com/software/support

http://techsupport.services.ibm.com/guides/handbook.html

http://techsupport.services.ibm.com/guides/handbook.html


12. Update your e-mail address as needed.

13. In the Documents list, select Software.

14. Select the types of documents that you want to receive information about.

15. Click Update. If you experience problems with the My support feature, you can obtain help in one of the following ways:

Online: Send an e-mail message to [email protected], describing your problem.

By phone: Call 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software SupportIBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

� For IBM distributed software products (including, but not limited to, Tivoli, Lotus®, and Rational® products, as well as DB2® and WebSphere® products that run on Windows or UNIX operating systems), enroll in Passport Advantage® in one of the following ways:

– Online: Go to the Passport Advantage Web page (http://www.lotus.com/services/passport.nsf/WebDocs/ Passport_Advantage_Home) and click How to Enroll

– By phone: For the phone number to call in your country, go to the IBM Software Support Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

� For customers with Subscription and Support (S & S) contracts, go to the Software Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

� For customers with IBMLink™, CATIA, Linux™, S/390®, iSeries™, pSeries®, zSeries®, and other support agreements, go to the Support Line Web site at http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

� For IBM eServer™ software products (including, but not limited to, DB2 and WebSphere products that run in zSeries, pSeries, and iSeries environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to the contacts page of the IBM Software Support Handbook on the Web at

http://techsupport.services.ibm.com/guides/contacts.html

http://www.lotus.com/services/passport.nsf/WebDocs/ Passport_Advantage_Home

http://www.lotus.com/services/passport.nsf/WebDocs/ Passport_Advantage_Home

http://www.ibm.com/servers/eserver/techsupport.html


http://www.ibm.com/servers/eserver/techsupport.html


http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region for phone numbers of people who provide support for your location.

To contact IBM Software Support, follow these steps:

1. “Determining the business impact” on page 3202. “Describing problems and gathering information” on page 3203. “Submitting problems” on page 321

Determining the business impactWhen you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem that you are reporting. Use the following criteria:

Describing problems and gathering informationWhen explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

� What software versions were you running when the problem occurred?

� Do you have logs, traces, and messages that are related to the problem symptoms? IBM Software Support is likely to ask for this information.

� Can you re-create the problem? If so, what steps were performed to re-create the problem?

� Did you make any changes to the system? For example, did you make changes to the hardware, operating system, networking software, and so on.

� Are you currently using a workaround for the problem? If so, be prepared to explain the workaround when you report the problem.

� What software versions were you running when the problem occurred?

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.

Severity 2 The problem has a significant business impact. The program is usable, but it is severely limited.

Severity 3 The problem has some business impact. The program is usable, but less significant features (not critical to operations) are unavailable.

Severity 4 The problem has minimal business impact. The problem causes little impact on operations, or a reasonable circumvention to the problem was implemented.



Submitting problemsYou can submit your problem to IBM Software Support in one of two ways:

� Online: Click Submit and track problems on the IBM Software Support site at http://www.ibm.com/software/support/probsub.html. Type your information into the appropriate problem submission form.

� By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the Software Support Web site daily, so that other users who experience the same problem can benefit from the same resolution.




Notices 323

Notices

OverviewThis 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 LicensingIBM CorporationNorth Castle DriveArmonk, 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 CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 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

E


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 Corporation2Z4A/10111400 Burnet RoadAustin, 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

Notices 325

similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not display.

TrademarksIBM, the IBM logo, AIX, Candle, Candle Management Server, Candle Management Workstation, CandleNet, CandleNet Portal, DB2, developerWorks, eServer, IBMLink, IMS, Informix, iSeries, Lotus, OMEGAMON, OMEGAMON Monitoring Agent, 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.

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.

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.


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 327

Aaction scheduling 111–120

reports 112audit logging 139–142

archiving 140historical disk space requirements 141reports 142

automation 23

Bbooks

see publications 11

CCandle Management Server 21Candle Management Workstation 22CandleNet Portal 22CandleNet Portal Server 22changing

object parameters 80clusters

creating a prototype 130how to create a managed cluster 126how to modify a managed cluster 136local queues 134namelists 135placeholder objects 125receiver channel objects 133resource groups 132sender channels 134terminology 123

color 64, 103configuration database 24

backing up 143restoring 146

Configuration view 18Configuration_Background_Error 119configured system group 38copying objects 81

guidelines 81creating

configured system groups 38managed clusters 121

new queue managers 69prototypes from defined objects 48prototypes in the Prototype View 46queue managers automatically 70remote queue managers 162resource groups 76resources 79security attributes for queue managers 73

customer supportsee Software Support 319

Ddefined objects 64Defined View 25

reviewing after a Discover 42summary - creating using Discover 36validating objects in the 86

Discoverautomatically 40considerations 40Discover Lite product option 41overview 40your existing WebSphere MQ configuration 41

Discover new resources 94discrepancies

resolving 95viewing 95

disk space requirement worksheet 141documentation conventions 13drag and drop guidelines 49dynamic variables, product-provided 51

Eexport MQSC commands function 108export XML data function 104Extended export 105

Ffinding objects 65

Gglobal variables

adding 54

Index


adding to prototypes 56deleting 55modifying 55product-provided 51used with prototypes 45viewing 53

Global Variables workspaceoverview 53

guidelinescopying objects 81dragging and dropping 49

Hhistorical data 141

Iimport XML data function 104information centers, searching to find software

problem resolution 317

Kknowledge bases, searching to find software problem

resolution 317

Llocal queues

for managed cluster 134locating objects 65

Mmaintaining your configuration

resolving discrepancies 95Update actual from defined 100Update defined from actual 97View discrepancies 95

managed clustercreating 126modifying objects within 136

manualssee publications 11

MQSC commands format for export 108

Nnamelists

for managed cluster 135

OOMEGAMON DE feature package 22OMEGAMON Platform 21–23

online publicationsaccessing 11

ordering publications 11

Ppartial export 105performance 76, 140permanent dynamic queues 76policy editor, accessing 120Policy Management 23Prototype View 44prototypes

about 44creating 44creating a cluster prototype 122, 130creating from defined objects 48creating in the Prototype View 46disinheriting 62dragging to the Defined View 49global variables 45samples 46showing usage 61symbolic variables 45

publicationsaccessing online 11ordering 11

Qqueue managers

adding default resources 70automatically starting non-z/OS 70connecting 75creating in Defined View 69creating in Prototype View 47creating remote objects 162on nodes without a configuration agent 70on z/OS nodes 69setting security attributes 73setting up for remote configuration 156starting 71stopping 71submit MQ command 71

Rreceiver channel objects

for managed clusters 133remote configuration

overview 154possible WebSphere MQ configurations 158

Index 329

setting up queue managers 156Replicate 83resolving discrepancies 95resource groups

$Default_Group 42, 76$DynamicResources 76creating in the Defined View 76creating in the prototype configuration 47for managed cluster 132

resourcescreating in defined configuration 79creating in the Prototype View 47

Run_OnDemand_Config_Action 120

Ssecurity

of export/import operations on z/OS only 107setting security attributes for queue managers 73

sender channels for managed cluster 134settings lists

changing object parameters 80determining data sources 64setting security attributes for queue managers 73

Software Supportcontacting 319

symbolic variables 51adding to prototypes 58overriding 59prototyping 45

TTivoli software information center 11

UUpdate actual from defined

overview 100procedure 100

Update defined from actualguidelines 95, 97overview 97procedure 98

Update modeentering 37overview 37

Vvalidating defined objects 86variables

dynamic, product-provided 51

global, adding to prototypes 56global, adding, modifying, deleting 54global, product-provided 51global, used with prototypes 45symbolic 51symbolic, used with prototypes 45viewing resolved 60

viewing discrepanciesoverview 95

WWorkflow editor 23

XXML data format for import or export 104


IBM@

Part Number: SC31-6889-00

Printed in USA

SC31-6889-00

SC31-6889-00