tivoli manager for mqseries release notespublib.boulder.ibm.com/tividd/td/modmq/gi10-3059-06r/en......

Tivoli Manager for MQSeries Revised Date:February 14, 2003Release Notes Version 2.4.0 GI10-3059-06

Tivoli Manager for MQSeries Release Notes

Copyright Notice

© Copyright IBM Corporation 1997-2003. All rights reserved. May only be used pursuant to a Tivoli SystemsSoftware License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBMCustomer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, storedin a retrieval system, or translated into any computer language, in any form or by any means, electronic,mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBMCorporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of anymachine-readable documentation for your own use, provided that each such reproduction shall carry the IBMCorporation copyright notice. No other rights under copyright are granted without prior written permission ofIBM Corporation. The document is not intended for production and is furnished “as is” without warranty of anykind. All warranties on this document are hereby disclaimed, including the warranties of merchantabilityand fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, OS/390, MQSeries, MVS, OS/400, DB2, NetView, OS/2, andTivoli Enterprise Console are trademarks or registered trademarks of International Business MachinesCorporation or Tivoli Systems Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, 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.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that theywill be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products,programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or servicescan be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM,any functionally equivalent product, program, or service can be used instead of the referenced product, program,or service. The evaluation and verification of operation in conjunction with other products, except those expresslydesignated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patentsor pending patent applications covering subject matter in this document. The furnishing of this document doesnot give you any license to these patents. You can send license inquiries, in writing, to the IBM Director ofLicensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

Chapter 1. Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Accessing Softcopy Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Providing Feedback About Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Uninstalling Tivoli Manager for MQSeries Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Patches Incorporated in Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Known Product Defects, Limitations, and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Product Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Accessing the Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

iiiTivoli Manager for MQSeries Release Notes

iv Release Notes Version 2.4.0

Release Notes

These release notes include the following topics:

¶ “New Features” on page 2

¶ “System Requirements” on page 3

¶ “Installation Notes” on page 6

¶ “Patches Incorporated in Version 2.4.0” on page 8

¶ “Defects Fixed” on page 8

¶ “Known Product Defects, Limitations, and Workarounds” on page 8

¶ “Product Notes” on page 13

The following table lists the changes made to these release notes after the first version waspublished on August 10, 2001:

Revised on Content Changes

February 4, 2002 The list of characters that are not supported in command previsedfor queue managers has been revised to include the left and rightparentheses ( ). See the appropriate item in “Known ProductDefects, Limitations, and Workarounds” on page 8.

September 25, 2002 A limitation has been added relating to an installation failure forTivoli Business Systems Manager Instrumentation for MQSerieson any platform other than Windows. See the appropriate item in“Known Product Defects, Limitations, and Workarounds” onpage 8.

September 25, 2002 A limitation has been added relating to the failure of the CreateMonitoring Profile task if Tivoli Distributed Monitoring has beeninstalled after installing Tivoli Manager for MQSeries. See thecorresponding item in “Known Product Defects, Limitations, andWorkarounds” on page 8.

December 20, 2002 In the Tivoli Manager for MQSeries User’s Guide, the descriptionfor the command in Step 2 of the procedure for “AssigningAuthorization Roles” has been revised. See the corresponding itemon page 12.

February 14, 2003 In the Tivoli Manager for MQSeries User’s Guide, in the Creatingthe Event Adapter Configuration File section on page 96, theexample of a filter statement is incorrect. See the correspondingitem on page 12.

1

1Tivoli Manager for MQSeries Release Notes

1.R

eleaseN

otes

Additional InformationThe following sections describe how to access publications online, order publications,provide feedback about publications, and contact customer support.

Accessing Softcopy PublicationsThe publications for this product are available in PDF and HTML formats through the TivoliInformation Center. IBM posts publications for this and all other Tivoli products, as theybecome available and whenever they are updated, to the Tivoli Information Center Web site.The Tivoli Information Center is located at the following Web address:

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

Click the Tivoli Manager for MQSeries link to access the product library.

Ordering PublicationsYou 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

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

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback About PublicationsIf you have comments or suggestions about Tivoli products and documentation, complete thecustomer feedback survey at the following Web site:

http://www.tivoli.com/support/survey/

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact IBM Customer Support. Seethe Tivoli Customer Support Handbook at the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Customer Support, depending onthe severity of your problem, and the following information:

¶ Registration and eligibility

¶ Telephone numbers and e-mail addresses, depending on the country in which you arelocated

¶ What information you should gather before contacting support

New FeaturesTivoli Manager for MQSeries® Version 2.4.0 provides the following new features:

¶ Easier installation procedure.

¶ Tivoli Inventory software signature.

¶ Improved channel status monitoring.

Additional Information

2 Release Notes Version 2.4.0



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

http://www.tivoli.com/inside/store/lit_order.html

http://www.tivoli.com/support/survey/

http://www.tivoli.com/support/handbook/

¶ Ability to manage the dead-letter queue (DLQ), including tasks to start and stop theDLQ handler and a task to create and edit DLQ rules tables.

¶ Ability to clone a queue manager configuration that is saved in the Tivoli Inventorydatabase to one or more Tivoli endpoints.

¶ Ability to configure the event adapter for MQSeries to send events directly from theendpoints to the event server or, for distributed platforms, to send events from endpointsthrough the gateway to the event server.

Note: The term distributed platforms in this document includes the AIX®, HP-UX,Solaris, Windows NT™, and Windows™ 2000 platforms and does not include theOS/400® or OS/390® platforms.

¶ Improvements to the graphical user interface (GUI) that enable you to run tasks and toconfigure MQSeries resources more easily.

¶ A user-configurable Statistical Event Adapter to read MQSeries OS/390 SystemManagement Facilities (SMF) statistical and accounting records and forward formattedevents to the event server.

¶ Improved migration facility.

¶ Monitors that report the number of open input handles and open output handles for aqueue.

¶ Uninstall function, including the ability to uninstall only a management domain or theinstalled TAG files.

System RequirementsThis section describes the system requirements, including software and hardware, that TivoliManager for MQSeries supports for Tivoli servers, managed nodes, and Tivoli endpoints.

Software RequirementsThis section describes the Tivoli Manager for MQSeries software requirements. Tivoli doesnot maintain or distribute operating system patches from vendors. Contact your operatingsystem vendor for information about obtaining and installing operating system patches.

Operating System Platform SupportTivoli Manager for MQSeries supports the following platforms in 32-bit mode for Tivoliservers and managed nodes:

Support for Tivoli Servers and Managed Nodes

Platform Required Level

AIX AIX 4.3.x

HP-UX¶ HP-UX 10.20

¶ HP-UX 11.00

Sun Solaris¶ Sun Solaris 7

¶ Sun Solaris 8

Windows NT Windows NT 4.0 with Service Pack 6A

Tivoli Manager for MQSeries supports the following platforms in 32-bit mode for Tivoliendpoints:

New Features


1.R

eleaseN

otes

Support for Tivoli Endpoints

Platform Required Level

AIX AIX 4.3.x

HP-UX¶ HP-UX 10.20

¶ HP-UX 11.00 with the latest MQSeries 5.1 CSD

OS/390¶ OS/390 Version 1 Release 3 (for support of MQSeries

Version 1 Release 2) or OS/390 Version 2 Release 6through Version 2 Release 10

¶ z/OS V1R1.0 running in 31-bit mode

For information about other requirements for Tivoli Managerfor MQSeries for OS/390, see “Tivoli Manager for MQSeriesfor OS/390 Required Products” on page 5.

OS/400 OS/400 Version 4 Release 5 with AS/400® Corrective ServiceCUMPTF C1100450

Sun Solaris¶ Sun Solaris 7

¶ Sun Solaris 8

Windows 2000¶ Windows 2000 Server

¶ Windows 2000 Advanced Server

¶ Windows 2000 Data Center Server

¶ Windows 2000 Professional

Windows NT Windows NT 4.0 with Service Pack 6A

Tivoli Product SupportThis section describes required and optional Tivoli products that Tivoli Manager forMQSeries supports.

Required Tivoli ProductsTivoli Manager for MQSeries requires the following Tivoli products:

¶ Tivoli Management Framework

¶ Tivoli Application Proxy

The following table lists the supported releases and the required patches for each requiredproduct:

Product Release Required Patches

Tivoli Management Framework 3.6.2¶ 3.6.2–TMF–0001

¶ 3.6.5–TMF–0006 (required for OS/400support)

Tivoli Management Framework 3.6.4 3.6.5–TMF–0006 (required for OS/400support)

Tivoli Management Framework 3.6.5 3.6.5–TMF–0006 (required for OS/400support)

Tivoli Management Framework 3.7B 3.7–TMF–0007 (required for OS/400 support)

System Requirements


Product Release Required Patches

Tivoli Management Framework 3.7.1 3.7–TMF–0007 (required for OS/400 support)

Tivoli Application Proxy 1.1¶ 1.1–APX–0005

¶ 1.0–APX–0001 (required for OS/400support)

¶ 1.1–APX–0007 (required for OS/400support on Tivoli Framework 3.7B or3.7.1)

Optional Tivoli ProductsTivoli Manager for MQSeries supports the following optional Tivoli products:

¶ Tivoli Business Systems Manager Version 1.1 or 1.5

¶ Tivoli Distributed Monitoring Version 3.6.2 or 3.7

¶ Tivoli Enterprise Console® Version 3.6.2 or 3.7, including the Tivoli Enterprise ConsoleAdapter Configuration Facility. Tivoli Enterprise Console Version 3.7 requires thefollowing patches:

v 3.7–TEC–0003

v 3.7–TEC–0004

In addition, for Tivoli Enterprise Console Version 3.7, contact Tivoli CustomerSupport to obtain the fix for APAR IY18247.

¶ Tivoli Inventory Version 3.6.2

¶ Tivoli Software Distribution Version 3.6.2

¶ Tivoli Software Installation Service Version 3.6.1 or 3.7

Tivoli Manager for MQSeries for OS/390 Required ProductsTivoli Manager for MQSeries for OS/390 Version 2.4.0 requires the following products:

¶ Tivoli Manager for MQSeries Version 2.4.0

¶ Tivoli NetView for OS/390 Version 1 Release 2 or later

¶ IBM TCP/IP

¶ Tivoli Business Systems Manager Task Server Version 1.5. The task server is installedwith Tivoli Business Systems Manager Event Enablement, which is provided on aseparate CD with the Tivoli Manager for MQSeries product.

Tivoli Business Systems Manager Task Server Version 1.5 runs on the followingplatforms:

v AIX

– AIX 4.1.5 with Motif 1.2 and the following PTFs:

¶ IX52339

¶ IX59547

¶ IX68453

– AIX 4.2.0 or later

System Requirements


1.R

eleaseN

otes

AIX 4.2.0 requires the following PTFs:

¶ IX61115

¶ IX68451

AIX 4.2.1 requires PTF IX68451

v AIX 4.3.1 or AIX 4.3.3

v Solaris 2.5.1, 2.6, 7, or 8 with patch 105210–x at this patch’s highest available level.Recommended patches are available from the following Sun Web site:

http://access1.sun.com

v Windows

– Windows NT 4.0 with Service Pack 4 or later

– Windows 2000 with Service Pack 1

For more information about Tivoli Manager for MQSeries for OS/390 requirements, refer tothe Tivoli Manager for MQSeries for OS/390 Program Directory.

Support for MQSeries ReleasesTivoli Manager for MQSeries supports the following MQSeries releases:

Platform Supported MQSeries Release

AIX, HP-UX, or Sun Solaris¶ MQSeries 5.1

Note: Apply the latest MQSeries 5.1 CSD on HP-UX 11.00.

¶ MQSeries 5.2

¶ Optionally, MQSeries Link for R/3 Version 1.2

Windows 2000 or Windows NT¶ MQSeries 5.1

¶ MQSeries 5.2

¶ MQSeries 5.2.1

¶ Optionally, MQSeries Link for R/3 Version 1.2

OS/390¶ MQSeries for MVS®/ESA 1.2

¶ MQSeries for OS/390 2.1

¶ MQSeries for OS/390 5.2

OS/400¶ MQSeries for AS/400 5.1

¶ MQSeries for AS/400 5.2

Hardware RequirementsIn addition to the space requirements for the management platform, a minimum of 16 MB offree disk space is required for all systems. On OS/400, an additional 2 to 3 MB of diskspace is required for the save files provided for the event adapter and the commands.

Installation NotesThis section summarizes the procedure, including prerequisite steps, for installing TivoliManager for MQSeries.

System Requirements


PrerequisitesSatisfy the following requirements before installing Tivoli Manager for MQSeries:

1. Ensure that you are running on a supported operating system and that you install allprerequisite software. See “Software Requirements” on page 3.

2. If you are running MQSeries resources on Tivoli endpoints, ensure that the endpoints areproperly configured and functional. Refer to the Tivoli Framework Planning andInstallation Guide.

3. Ensure that the Application Proxy is installed. For installation instructions, refer to″Chapter 2. Planning and Installing″ in the Tivoli Manager for MQSeries User’s Guide.

4. Configure the Tivoli management regions. For information, refer to ″Chapter 2. Planningand Installing″ in the Tivoli Manager for MQSeries User’s Guide.

5. Set the required system resources. For information, refer to ″Chapter 2. Planning andInstalling″ in the Tivoli Manager for MQSeries User’s Guide.

6. Configure the Tivoli Enterprise Console server (event server). For more information,refer to ″Chapter 2. Planning and Installing″ in the Tivoli Manager for MQSeries User’sGuide.

7. Optionally, if you manage MQSeries resources on an OS/390 system, refer to ″Chapter 8.Introducing Manager for MQSeries for OS/390″ in the Tivoli Manager for MQSeriesUser’s Guide.

8. Optionally, if you plan to manage MQSeries resources with Tivoli Business SystemsManager, ensure that the Tivoli Business Systems Manager task server is configured andthat the Tivoli Business Systems Manager workstations are installed.

SummaryTo install Tivoli Manager for MQSeries, you have one of the following options:

¶ If you do not have a previous version of Tivoli Manager for MQSeries installed, do anew installation of Tivoli Manager for MQSeries Version 2.4.0.

¶ If you have Tivoli Manager for MQSeries Versions 2.3 to 2.3.0.4 installed, upgrade toVersion 2.4.0. To do this, stop all MQSeries event adapters. Then, install Version 2.4.0on top of your existing installation to upgrade all management domain and queuemanager objects, monitoring profiles, and subscription lists to the Version 2.4.0 level. Toensure that the upgrade process works correctly, install Version 2.4.0 on the managednodes and gateways first, and then install Version 2.4.0 on the Tivoli server.

Note: Because Version 2.4.0 does not support OS/2, upgrading Version 2.3.1 to Version2.4.0 is not supported.

¶ If you have Version 2.2.1 installed, upgrade to Version 2.4.0. To do this, stop allMQSeries event adapters. Then, install Version 2.4.0 on top of your existing installation.To ensure that the upgrade process works correctly, install Version 2.4.0 on the managednodes and gateways first, and then install Version 2.4.0 on the Tivoli server. Afterinstallation, you must discover the queue manager objects again, delete the Version 2.2.1monitoring profiles, and then re-create the monitoring profiles for Version 2.4.0.

For complete details about how to install or upgrade to Tivoli Manager for MQSeriesVersion 2.4.0, refer to ″Chapter 2. Planning and Installing″ in the Tivoli Manager forMQSeries User’s Guide.

Installation Notes


1.R

eleaseN

otes

Uninstalling Tivoli Manager for MQSeries Version 2.4.0Tivoli Manager for MQSeries provides the mqsuninst command and theUninstall_Endpoints_ManagedNodes task to facilitate uninstalling Tivoli Manager forMQSeries Version 2.4.0. For complete details, refer to ″Chapter 2. Planning and Installing″in the Tivoli Manager for MQSeries User’s Guide.

Patches Incorporated in Version 2.4.0The following patches have been incorporated into this release of Tivoli Manager forMQSeries:

¶ 2.3–MQS–0001

¶ 2.3–MQS–0002

¶ 2.3–MQS–0003

¶ 2.3–MQS–0004

Defects FixedThe following defects have been corrected in this release of Tivoli Manager for MQSeries:

¶ APAR IY10779. Channel status monitors return up and down only. The monitors shouldreturn unknown also.

¶ APAR IY13890. Channel status monitor should return the same status that MQSeriesgives for the channel.

¶ APAR IY15461. Endpoints are not listed in the Execute Task dialog.

¶ APAR IY16275. The documentation does not describe how to manage MQSeries onmultiple OS/390 systems.

¶ APAR IY16966. The documentation does not state that the Qshell Utilities PRPQ optionis required for OS/400 support.

¶ APAR IY17193. The Create Management Domain task fails if an endpoint has the samename as a managed node.

¶ APAR IY17317. The Configure Event Server task fails when using Tivoli EnterpriseConsole Version 3.7

¶ APAR IY17552. The Configure Event Adapter task does not display the default portnumber for the event server when the event server is on a Windows host.

¶ APAR IY18727. TEC tasks do not execute if the managed node does not have the mqmgroup.

For information about fixed defects for Tivoli Manager for MQSeries for OS/390, refer tothe Tivoli Manager for MQSeries for OS/390 Program Directory.

Known Product Defects, Limitations, and WorkaroundsThis section describes known defects in this release of Tivoli Manager for MQSeries. Whereapplicable and known, suggested workarounds are identified. Note that this might not be acomplete list of defects.

¶ On Tivoli Enterprise Console Version 3.7, the Configure Event Server task does notcreate the MQSeries and MQSeries Statistics event groups.

Installation Notes


Workaround: Create the MQSeries and MQSeries Statistics event groups manuallyfrom the event console.

¶ Upgrading to Tivoli Manager for MQSeries Version 2.4.0 from a previous release fails ifyou install Version 2.4.0 on the Tivoli server at the same time as you install Version2.4.0 on the managed nodes and the gateways. The upgrade process must complete onthe managed nodes and the gateways before you can upgrade the Tivoli Manager forMQSeries installation on the Tivoli server.

If upgrading from a previous release failed because you installed Version 2.4.0 on theTivoli server at the same time as you installed Version 2.4.0 on the managed nodes andthe gateways, install Version 2.4.0 again on the Tivoli server. The Tivoli Manager forMQSeries installation on the managed nodes and the gateways has been upgraded.

¶ Using the Tivoli Manager for MQSeries Edit DLQ Rules Table task to edit a DLQ rulestable that has been created manually can have unpredictable results. If a rule containsunsupported syntax, the rule is ignored, and the DLQ rules table does not displaycorrectly in the Edit DLQ Rules Table dialog. In particular, the Tivoli Manager forMQSeries DLQ rules table editor does not support rules spanning multiple lines wherethe minus sign (–) is used within keywords and parameters, such as:APPLNAME(’ABC–D’)

Workaround: If a DLQ rules table that you have created manually does not displaycorrectly in the Edit DLQ Rules Table dialog, edit the DLQ rules table manually.

¶ Using pattern-matching characters to filter events on the event console does not work onOS/400.

Workaround: Filter events using the entire name of the event you want to filter out.

¶ On OS/400, monitors fail, returning the following error message:E.EXEC with exit code 7.

This problem occurs because Distributed Monitoring relies on the existence of the/dev/null directory when running monitors, and Distributed Monitoring does not createthe /dev/null directory on OS/400 as it does on other platforms. APAR IY19082 hasbeen opened against Distributed Monitoring to address this problem.

Workaround: Enter the QShell and create the /dev/null directory before runningTivoli Manager for MQSeries monitors.

¶ Entering multiple dollar signs ($) in a text field on a task dialog, such as theDescription text field, results in converting each pair of dollar signs ($$) to the numbers861. This problem occurs because $$ returns the value of the $ parameter in the bashshell.

Workaround: Do not use multiple dollar signs as input on a task dialog.

¶ Task input to MQSeries commands is limited to 255 characters. Running a task withparameters that exceed 255 characters produces the following message:Invalid Syntax. Command string must be between 1 and 255 characters long.

Workaround: Run the task multiple times, providing a subset of parameters each time.For example, if you are creating a channel, run the Create Channel task, providing asubset of parameters. Then run the Change Channel task, providing additionalparameters.

¶ Errors such as ″in spool error″ or ″general failure″ can be produced when distributing afile package for installation of MQSeries 5.1.

Known Product Defects, Limitations, and Workarounds


1.R

eleaseN

otes

Workaround: Refer to APAR IY05425 for wrpt parameter configuration.

¶ If you have a previous installation of the event adapter for MQSeries on OS/400, youmight observe events are not sent to the event server. Do the following:

Workaround: Follow these steps:

1. Stop the event adapter.

2. Remove the QTMEMQA library from the OS/400 endpoint.

3. Remove the symbolic links located in the/QIBM/UserData/Tivoli/lcf/bin/os400-v3r7/TME/TEC/adapters/bin directorypointing to any object in the QTMEMQA library, either by using the QSH interfaceor with the WRKLNK command.

4. Rerun any task against the OS/400 endpoint or against its queue manager to forceredistribution of the QTMEMQA library.

¶ For queue managers on OS/390, command prefixes that begin with or contain a percentsign (%), a dollar sign ($), or the left and right parentheses ( ) are not supported.

Workaround: Use a different character in the command prefix, such as a plus sign (+)or a pound sign (#).

¶ Starting the event adapter from an OS/400 command line, results in the followingexception:Application error. MCH3601 unmonitored by LIBTISat statement 0000000002, instruction X’0000’.

This problem does not occur when the event adapter is started using a task from theTivoli desktop.

Workaround: Before starting the event adapter from an OS/400 command line, youmust set the TISDIR environment variable using the following command:ADDENVVAR ENVVAR(TISDIR) VALUE(’/QIBM/USERDATA/TIVOLI/LCF’)

¶ There is a limit on the number of resources that can be discovered using a single TivoliBusiness Systems Manager heartbeat monitor. A single channel heartbeat monitor candiscover approximately 100 channels. A single queue heartbeat monitor can discoverapproximately 400 queues.

Workaround: Use multiple Tivoli Business Systems Manager heartbeat monitors andspecify filters for each monitor to limit the number of resources that can be discovered.

¶ Conflicts will occur if you install Tivoli Manager for R/3 and Tivoli Manager forMQSeries in the same Tivoli management region and try to run automatic discovery onOS/400 endpoints.

Workaround: Enter the following command to allow the run_task method to runsuccessfully on OS/400 endpoints in all gateways:wdepset -e @DependencyMgr:sap_run_task_dep -r \depset @DependencyMgr:sap_tool_dep

This command prevents the Tivoli Manager for R/3 automatic discovery function fromworking. Automatic discovery will continue to work on OS/400 endpoints that alreadyhave the necessary files. However, automatic discovery will fail when this command isrun on OS/400 endpoints on which automatic discovery has not been executed. Thecommand removes dependencies from the run_task method.

To put the dependencies back on the run_task method in all gateways, use the followingcommand:



wdepset -e @DependencyMgr:sap_run_task_dep -a \depset @DependencyMgr:sap_tool_dep

After either of the above commands are run, you must synchronize all the gateways withthe dependencies. Run the following command on each gateway you want tosynchronize:wgateway gateway_name dbcheck

where gateway_name is the name of the gateway you want to synchronize.

¶ Due to an unresolved problem on HP-UX machines, the Tivoli Manager for MQSeriesevent adapter cannot properly process certain event types, typically those associated withstopping a channel. When these event types are encountered, the event adapterterminates and must be restarted.

Workaround: None. Clear the system event queue before restarting the event adapter.

¶ Initial distribution of installation file packages to an endpoint fails, resulting in thecould not create process error.

Workaround: Run the Discover Queue Managers task on the appropriate endpoint (eventhough MQSeries is not installed on the endpoint). Then, distribute the installation filepackages.

¶ If $tmemqs_user is modified with the widmap command to contain user IDs that do nothave sufficient authority, tasks fail with write permission errors.

Workaround: Ensure that $tmemqs_user is mapped to user IDs with sufficientadministrator authority.

¶ The Create Management Domain dialog hangs when the same dialog is used to createmultiple domains.

Workaround: Use a new Create Management Domain dialog for each managementdomain you want to create. Also, stop and start the desktop after creating eachmanagement domain.

¶ When running the Create Management Domain task from the Manager for MQSeriesicon’s pop-up menu, the task output might not be correct if the task fails.

Workaround: Run the Create Management Domain task from the Utility Tasks library.

¶ When uninstalling Tivoli Manager for MQSeries, the mqsuninst command might issuean event method failed e=12 error.

Workaround: None. You can ignore this error message.

¶ You cannot distribute more than four monitors to a queue manager running under TivoliFramework 3.7.1.

Workaround: None. APAR IY21453 has been opened against Tivoli Framework toaddress this problem.

¶ The MQSeries monitoring collection is not installed in interconnected regions.

Workaround: Install Tivoli Manager for MQSeries in all regions before running thewupdate command to update shared resources.

¶ Pop-up menu tasks do not work in interconnection regions.

Workaround: Install Tivoli Manager for MQSeries in all regions before running thewupdate command to update shared resources.



1.R

eleaseN

otes

¶ On a Windows NT Tivoli management region, the Queue Manager Control Center dialoghangs when a large number (over 40) of queue manager configurations are saved in theTivoli Inventory database.

Workaround: Contact Tivoli Customer Support for the fix to APAR IY22213.

¶ When the display is exported from a UNIX machine to a Windows machine, or visaversa, the Delete Queue task fails from the Queue Manager Control Center dialog.

Workaround: For a temporary solution, run the Delete Queue task from the queuemanager icon’s pop-up menu or from the Queue Tasks library. For a permanent solution,contact Tivoli Customer Support for the fix to APAR IY22213.

¶ When using Tivoli Distributed Monitoring Version 3.7 on UNIX, Tivoli Manager forMQSeries monitors set to root fail with a policy validation failure.

Workaround: Set Tivoli Manager for MQSeries monitors to a user ID (other than root)that has mqm authority.

¶ The installation of Tivoli Business Systems Manager Instrumentation for MQSeries failson any platform other than Windows.

Workaround: Contact Tivoli Customer Support for the fix to APAR IY31394.

¶ When Tivoli Distributed Monitoring is installed after installing Tivoli Manager forMQSeries, the Create Monitoring Profile task fails.

Workaround: Run the Distributed Monitoring mcsl command on the Tivoli server. Thenrun the Create Monitoring Profile task again.

¶ A procedure in the Tivoli Manager for MQSeries User’s Guide contains an error: Step 2of the “Assigning Authorization Roles” procedure incorrectly states:

2. Enter the following command:mqs_interregion_roles.sh remote_region_name

Where remote_region_name is the name of the remote management region.

Workaround (This item resolves Doc APAR IY36444.): Use the following informationfor Step 2 of the “Assigning Authorization Roles” procedure:

2. Enter the following command:mqs_interregion_roles.sh remote_domain_name

Where remote_domain_name is the name of the remote WebSphere MQ managementdomain without the MQS_ prefix.

¶ In the Tivoli Manager for MQSeries User’s Guide, the Creating the Event AdapterConfiguration File section on page 96 shows an incorrect example for the followingfilter statement:

The following filter statement passes all events for the queue manager named QSB014:FilterMode=INFilter:Class=*;QMgrName=QSB014

Workaround (This item resolves Doc APAR IY39488.): You must enclose the queuemanager name in single quotes. The correct filter statement should read as follows:

The following filter statement passes all events for the queue manager named QSB014:FilterMode=INFilter:Class=*;QMgrName=’QSB014’



Product NotesThis section contains important information that you should consider when using TivoliManager for MQSeries.

Accessing the Product DocumentationThe following .pdf and the .htm documentation files are available on the Tivoli Manager forMQSeries CD in the /doc directory and are installed with the product in the$BINDIR/../generic_unix/TME/MQS/doc/ directory:

Document Files

Tivoli Manager for MQSeries User’s Guide¶ m24u.pdf

¶ m24utfrm.htm (frames version)

¶ m24u.htm (non-frames version)

View or print the .pdf files using the Adobe Acrobat Reader. View the .htm files using yourdefault Web browser.

Notes:

1. If you do not have Adobe Acrobat Reader, you can obtain it free by clicking theGet Acrobat Reader icon and following the steps that are provided at the AdobeWeb site:

http://www.adobe.com

2. The Tivoli Manager for MQSeries User’s Guide and the Tivoli Manager forMQSeries Release Notes are also available in .htm and .pdf format at the followinglocation on the Tivoli support Web site:

http://www.tivoli.com/support/documents/

You need a user ID and a password to access this Web site. To obtain an ID for useon the support Web site, go to the following Web site:

http://www.tivoli.com/support/getting/

InternationalizationThis section provides information about using Tivoli Manager for MQSeries Version 2.4.0with language support.

Enabling Language SupportTivoli Manager for MQSeries Version 2.4.0 is enabled for the following languages:

¶ Brazilian Portuguese

¶ Chinese (Simplified)

¶ Chinese (Traditional)

¶ French

¶ German

¶ Italian

¶ Japanese

¶ Korean

Product Notes


1.R

eleaseN

otes

http://www.adobe.com

http://www.tivoli.com/support/documents/

http://www.tivoli.com/support/getting/

¶ Spanish

To enable these languages, you must install the appropriate language support pack from theTivoli Manager for MQSeries Language Support CD-ROM. For example, install thefollowing pack for German language support:Tivoli Manager for MQSeries, Version 2.4.0 (de)

You can install multiple language support packs for a single product. Please note, however,to get full language enablement, you must install the Framework language support pack inaddition to the language support pack for Tivoli Manager for MQSeries.

For instructions on installing products and for information about setting up a non-Englishenvironment, refer to the Tivoli Enterprise Installation Guide Version 3.7.

Translation DefectsEvery effort is made to translate the documentation clearly and accurately, but terminologychanges between versions of a product may cause inconsistencies in the documentation.

Occasionally, you might notice that the text in a procedure does not agree with theaccompanying screen capture. If this happens, always follow the instruction in the text.

The following list describes known translation defects in this release of Tivoli Manager forMQSeries. Where applicable and known, suggested workarounds are identified. Note thatthis might not be a complete list of defects.

¶ When running tasks on Tivoli Framework Version 3.7 endpoints, messages are displayedin English only.

Workaround: For translated messages, replace the wbindmsg command in each$BINDIR/../lcf_bundle/$interp/TME/MQS/utils directory with the wbindmsgcommand that is in the $BINDIR/bin directory.

¶ For Japanese only: In task output, the words Task Endpoint are corrupt. This problemdoes not prevent understanding of the task output.

Workaround: Run the task from the task library.

¶ When creating or editing a DLQ rules table, a description entered in the Descriptiontext field on the Create/Edit DLQ Rulesets dialog in a language other than Englishmight not display correctly.

Workaround: Enter a description in English only in the Description text field on theCreate/Edit DLQ Rulesets dialog.

¶ In task output, some characters in MQSeries message AMQ8195 are corrupt. Thisproblem has been observed intermittently in Italian and should not prevent understandingof the task output.

Workaround: None.

Product Notes


Part Number: 5698MQS

Printed in U.S.A.

GI10-3059-06

(1P)

P/N:

5698MQS

tivoli manager for mqseries release notespublib.boulder.ibm.com/tividd/td/modmq/gi10-3059-06r/en......

Documents