tivoli manager for r/3 release notes

Tivoli® Manager for R/3Release Notes Version 2.2.0 Revison Date:October 3, 2002 GI10-3024-06

Tivoli Manager for R/3 Release Notes

Copyright Notice

© Copyright IBM Corporation1997, 2001. All rights reserved. May only be usedpursuant to a Tivoli Systems Software License Agreement, an IBM SoftwareLicense Agreement, or Addendum for Tivoli Products to IBM Customer or LicenseAgreement. No part of this publication may be reproduced, transmitted, transcribed,stored in a retrieval system, or translated into any computer language, in any formor by any means, electronic, mechanical, magnetic, optical, chemical, manual, orotherwise, without prior written permission of IBM Corporation. IBM Corporationgrants you limited permission to make hardcopy or other reproductions of anymachine-readable documentation for your own use, provided that each suchreproduction shall carry the IBM Corporation copyright notice. No other rightsunder copyright are granted without prior written permission of IBM Corporation.The document is not intended for production and is furnished “as is” withoutwarranty of any kind. All warranties on this document are hereby disclaimed,including the warranties of merchantability and fitness for a particularpurpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restrictedby GSA ADP Schedule Contract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Tivoli Enterprise, and TivoliEnterprise Console, are trademarks or registered trademarks of InternationalBusiness Machines Corporation or Tivoli Systems Inc. in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marks ofothers.

Notices

References in this publication to Tivoli Systems or IBM products, programs, orservices do not imply that they will be available in all countries in which TivoliSystems or IBM operates. Any reference to these products, programs, or services isnot intended to imply that only Tivoli Systems or IBM products, programs, orservices can be used. Subject to valid intellectual property or other legallyprotectable right of Tivoli Systems or IBM, any functionally equivalent product,program, or service can be used instead of the referenced product, program, orservice. The evaluation and verification of operation in conjunction with otherproducts, except those expressly designated by Tivoli Systems or IBM, are theresponsibility of the user. Tivoli Systems or IBM may have patents or pendingpatent applications covering subject matter in this document. The furnishing of thisdocument does not give you any license to these patents. You can send licenseinquiries, in writing, to the IBM Director of Licensing, IBM Corporation, NorthCastle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

Chapter 1. Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . 3

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Operating System Platform Support . . . . . . . . . . . . . . . . . . . . . . . . 5

Tivoli Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Support for R/3 Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Support for SAP Internet Transaction Server . . . . . . . . . . . . . . . . . 9

Support for SAPGUI Distribution . . . . . . . . . . . . . . . . . . . . . . . . . 9

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Upgrade Approach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Uninstalling Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Patches Incorporated in Version 2.2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Defects Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

Product Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

New Requirement for Filter Statements . . . . . . . . . . . . . . . . . . . . . . . . 20

R/3 Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Accessing Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

iiiTivoli Manager for R/3 Release Notes

Internationalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enabling Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Translation Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

iv

Release Notes

This Release Notes document provides important information aboutTivoli Manager for R/3 Version 2.2.0. These notes are the mostcurrent information for the product and take precedence over allother documentation.

Please review these notes thoroughly before installing or using thisproduct.

The following table lists changes made to these release notes afterthe first version was published on October 26, 2001.

1

1Tivoli Manager for R/3 Release Notes

1.R

eleaseN

otes

Revised on Content Changes

October 26, 2001 Several problems and workarounds have beenadded to “Known Product Defects, Limitations,and Workarounds” on page 14. These problems aresummarized as follows:

¶ Upgrading Tivoli Manager for R/3 fromVersion 2.1 fails if you have created R/3objects on a managed node other than on anendpoint’s current gateway.

¶ The CCMS Event Adapter does not report anyR/3 alerts, and it reports a return code of 338from function moduleBAPI_SYSTEM_MT_CREATEBYTEMPL.

¶ Authorization T_5618443201 cannot beassigned to authorization object S_LOG_COMbecause authorization T_5618443201 does notexist in R/3 releases prior to 4.6.

¶ Uninstalling Tivoli Manager for R/3 from anendpoints fails when the name of theendpoints’ gateway includes a space.

November 6, 2001 Several problems and workarounds related totranslation have been added to “TranslationDefects” on page 22.

October 3, 2002 Several problems and workarounds have beenadded to “Known Product Defects, Limitations,and Workarounds” on page 14.

These Release Notes include the following topics:

¶ “New Features” on page 4

¶ “System Requirements” on page 4

¶ “Installation Notes” on page 10

¶ “Defects Fixed” on page 13

¶ “Known Product Defects, Limitations, and Workarounds” onpage 14

¶ “Product Notes” on page 20

2

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

Accessing Publications OnlineYou can access many Tivoli publications online in the TivoliInformation Center, which is available on the Tivoli CustomerSupport Web site:

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

These publications are available in PDF or HTML format, or both.Translated documents are also available for some products.

Ordering PublicationsYou can order many Tivoli publications online at the following Website:

http://www.ibm.com/shop/publications/order

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, for a list of telephone numbers, see thefollowing Web site:

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

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey at the following Web site:

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

Additional Information


1.R

eleaseN

otes


http://www.ibm.com/shop/publications/order

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

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

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contactTivoli Customer Support. See the Tivoli Customer Support Handbookat the following Web site:

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

The handbook provides information about how to contact TivoliCustomer Support, depending on the severity of your problem, andthe following information:

¶ Registration and eligibility

¶ Telephone numbers and e-mail addresses, depending on thecountry you are in

¶ What information you should gather before contacting support

New FeaturesTivoli Manager for R/3 Version 2.2.0 provides the following newfeatures:

¶ A user-configurable event adapter to query the CCMSMonitoring Architecture for R/3 alerts and to report them asTivoli Enterprise Console events

¶ Support for Tivoli Business Systems Manager

¶ Additional R/3 release support

¶ Support for new releases of Tivoli Manager for DB2 and TivoliManager for Oracle

System RequirementsThis section describes the system requirements, including softwareand hardware, required by Tivoli Manager for R/3 Tivoli servers,managed nodes, and Tivoli endpoints.

Software RequirementsThis section describes the Tivoli Manager for R/3 softwarerequirements.

Additional Information

4

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

Operating System Platform SupportTivoli Manager for R/3 supports the following platforms in 32-bitmode:

Platform Required Level

AIX AIX 4.3.xNote: Tivoli’s support of AIX is limited toAIX on IBM systems. Tivoli does not supportAIX on other hardware.

HP-UX¶ HP-UX 10.20

¶ HP-UX 11.00

Sun Solaris¶ Sun Solaris 6

¶ Sun Solaris 7

¶ Sun Solaris 8

Windows 2000¶ Windows 2000 Server

¶ Windows 2000 Advanced Server

¶ Windows 2000 Professional

Windows NT Windows NT 4.0 with Service Pack 6A

Tivoli Manager for R/3 supports the following platform in 64-bitmode:

Platform Required Level

HP-UX HP-UX 11.00

Tivoli Product SupportThis section describes required and optional Tivoli products thatTivoli Manager for R/3 supports.

Required Tivoli ProductsTivoli Manager for R/3 requires the following Tivoli products:

¶ Tivoli Management Framework

System Requirements


1.R

eleaseN

otes

¶ Tivoli Enterprise Console, including the Tivoli EnterpriseConsole Adapter Configuration Facility

¶ Tivoli Distributed Monitoring, including the UniversalMonitoring collection

¶ Tivoli Application Proxy

The following table lists the supported releases, required patches,and additional patch information for each required product:

Product Release Required Patches Patch Notes

TivoliManagementFramework

3.6.5¶ 3.6.5–TMF–0002

¶ 3.6.5–TMF–0004

None


3.7B¶ 3.7–TMF–0010

¶ 3.7–TMF–0016

None


3.7.1¶ 3.7.1–TMF–0001

¶ 3.7.1–TMF–0002

¶ 3.7.1–TMF–0003

¶ 3.7.1–TMF–0007

Patch 3.7.1–TMF–0007 isrequired for Windowsplatforms only.

System Requirements

6


Tivoli EnterpriseConsole

3.6.2¶ 3.6.2–TEC–0002

¶ 3.6.2–TEC–0006

Apply patch3.6.2–TEC–0006 on theevent server, the eventconsole, and the managednodes where the TivoliEnterprise Console AdapterConfiguration Facility isinstalled. Patch3.6.2–TEC–0006 requirespatch 3.6.2–TEC–0002.

If you are using TivoliManager for R/3 in adouble-byte environment,the following patches arerequired to properly displayTivoli Enterprise Consoleevents:

¶ 3.6.2–TEC–0001

¶ 3.6.2–TEC–0004

Tivoli EnterpriseConsole

3.7¶ 3.7–TEC–0003

¶ 3.7–TEC–0004

¶ Contact Tivoli CustomerSupport to obtain thefixes for the followingAPARs:

v IY17813

v IY18247

APAR IY17813 has fix3.7–TEC–0024E.

Tivoli DistributedMonitoring

3.6.2¶ 3.6.2–DM–0001

¶ 3.6.2–DM–0011

¶ 3.6.2–DM–0023

¶ 3.6.2–DM–0024

None

Tivoli DistributedMonitoring

3.7 3.7–DM–0004 None

System Requirements


1.R

eleaseN

otes


TivoliApplicationProxy

1.1 1.1–APX–0005 None

Optional Tivoli ProductsTivoli Manager for R/3 supports the following optional Tivoliproducts:

¶ Tivoli Software Distribution 3.6.2

¶ Software Installation Service 3.6.1 or 3.7.

The following product patch is required for Software InstallationService 3.6.1:

3.6.1–SIS–0006

The following product patch is recommended for SoftwareInstallation Service 3.7:

3.7–SISDEPOT–0003

¶ Tivoli Business Systems Manager 1.5, including Tivoli BusinessSystems Manager Event Enablement 1.5.

The following patch is required for Tivoli Business SystemsManager Event Enablement 1.5:

1.5–BSM–0008

¶ Tivoli Manager for DB2 2.1.0 with the following productpatches:

v 2.0–DBT–0001 (for Tivoli Management Framework 3.7.1support)

v 2.1–DBT–0002 (for Windows 2000 support)

¶ Tivoli Manager for Oracle 2.0 with the following productpatches:

v 2.0–ORA–0001

v 2.0–ORA–0004

System Requirements

8

Support for R/3 ReleasesThis section lists the R/3 releases that Tivoli Manager for R/3supports. This support is limited to the extent that SAP supports itsR/3 releases. This means that Tivoli Manager for R/3 automaticallydrops support for an R/3 release when SAP drops support for thatrelease. The following list identifies supported R/3 releases andend-of-support dates, if applicable, based on SAP’s published releasestrategy.

¶ R/3 3.1I, until the end of August, 2003

¶ R/3 4.0B, until the end of August, 2003



¶ R/3 4.6C, until the end of March, 2005

¶ R/3 4.6D

Support for SAP Internet Transaction ServerTivoli Manager for R/3 supports the same SAP Internet TransactionServer (ITS server) general availability release levels that SAPsupports. The supported ITS server release levels apply to WindowsNT and Windows 2000 only. The following table describes the ITSserver release levels and the related R/3 Basis release that TivoliManager for R/3 supports:

ITS Server Release Related R/3 Basis Release

4.6DC4 4.6D

Support for SAPGUI DistributionTivoli Manager for R/3 provides SAPGUI distribution for thefollowing SAP-supported platforms:

¶ UNIX (AIX, HP-UX, Sun Solaris), up to R/3 release 4.0B

¶ Windows (Windows NT and Windows 2000)

¶ Windows 95/98

System Requirements


1.R

eleaseN

otes

Hardware RequirementsIn addition to space requirements for the management platform, aminimum of 60 MB of free disk space is required for all systems.An additional 10 MB of free disk space is required if you plan toinstall Tivoli Business Systems Manager Instrumentation for R/3Version 2.2.0.

Installation NotesThis section summarizes the procedure, including prerequisite steps,for installing Tivoli Manager for R/3.

PrerequisitesSatisfy the following requirements before installing:

1. Ensure that you are running on a supported operating system andthat you install all prerequisite software. See “SoftwareRequirements” on page 4.

2. Configure the Tivoli management regions. For information, referto ″Chapter 2. Planning for and Installing Tivoli Manager forR/3″ in the Tivoli Manager for R/3 User’s Guide.

3. If you are running R/3 application servers on Tivoli endpoints,ensure that the endpoints are properly configured and functional.Refer to the Tivoli Framework Planning and Installation Guide.

4. Ensure that the Application Proxy is installed. For installationinstructions, refer to ″Chapter 2. Planning for and InstallingTivoli Manager for R/3″ in the Tivoli Manager for R/3 User’sGuide.

5. Configure the event server. For more information, refer to″Chapter 2. Planning for and Installing Tivoli Manager for R/3″in the Tivoli Manager for R/3 User’s Guide.

6. Optionally, if you plan to manage R/3 resources with TivoliBusiness Systems Manager, ensure that the Tivoli BusinessSystems Manager is installed and operational.

System Requirements

10

7. Optionally, if you want to extend Tivoli Manager for R/3database server status reporting, install Tivoli Manager for DB2or Tivoli Manager for Oracle, as appropriate.

Installation SummaryThe installation procedure you follow depends on whether you areinstalling Tivoli Manager for R/3 for the first time or whether youhave a previous version of Tivoli Manager for R/3 installed. Toinstall Tivoli Manager for R/3, you have one of the followingoptions:

¶ If you do not have a previous version of Tivoli Manager for R/3installed, do a new installation of Tivoli Manager for R/3Version 2.2.0.

¶ If you have Tivoli Manager for R/3 Version 1.5, Version 1.5.1,Version 2.0, or Version 2.1 installed, the method you choosedepends on whether you want to preserve configuration data orwhether you want to do a fresh installation.

Important Notice

If you plan to uninstall Tivoli Manager for R/3 Version 2.1, contact TivoliCustomer Support.

For complete details about how to install or upgrade to TivoliManager for R/3 Version 2.2.0, refer to ″Chapter 2. Planning for andInstalling Tivoli Manager for R/3″ in the Tivoli Manager for R/3User’s Guide.

Upgrade ApproachWhen upgrading Tivoli Manager for R/3 from version 2.1 to version2.2.0, you must also consider how to upgrade the required andoptional Tivoli products because each version of Tivoli Manager forR/3 has different requirements.

Assume that you have Tivoli Manager for R/3 Version 2.1 installedwith the following Tivoli products:

¶ Tivoli Management Framework 3.6.2

¶ Tivoli Distributed Monitoring 3.6.2

Installation Notes


1.R

eleaseN

otes

¶ Tivoli Enterprise Console 3.6.2

¶ Tivoli Global Enterprise Manager 2.2.1

The following upgrade approach ensures that Tivoli Manager for R/3remains operational throughout the upgrade process:

1. Upgrade Tivoli Management Framework to version 3.6.5.

2. Install the required Tivoli Management Framework and TivoliDistributed Monitoring patches as follows:

¶ Install Tivoli Management Framework patches3.6.5–TMF–0002 and 3.6.5–TMF–0004.

¶ Install Tivoli Distributed Monitoring patch 3.6.2–DM–0024and its prerequisites.

3. Upgrade Tivoli Manager for R/3 version 2.2.0 as follows:

¶ Install the Tivoli Manager for R/3 Version 2.2.0 R/3 ABAPtransport files.

¶ Install Tivoli Manager for R/3 Version 2.2.0 (Upgrade fromVersion 2.1) as a product patch.

For information about a limitation related to upgrading TivoliManager for R/3, see “Known Product Defects, Limitations,and Workarounds” on page 14.

Note: You can install the Version 2.2.0 transport files eitherbefore or after you install Tivoli Manager for R/3Version 2.2.0 (Upgrade from Version 2.1) productpatch.

4. Optionally, perform the following steps:

a. Upgrade Tivoli Management Framework to version 3.7 or3.7.1.

b. Upgrade Tivoli Distributed Monitoring to version 3.7 andapply patch 3.7–DM–0004.

c. Upgrade Tivoli Enterprise Console to version 3.7.

d. Create Tivoli Manager for R/3 objects for R/3 serversrunning on Windows 2000.

Installation Notes

12

e. Install Tivoli Business Systems Manager Instrumentation forR/3 Version 2.2.0.

Uninstalling Tivoli Manager for R/3Tivoli Manager for R/3 provides two scripts, R3Mgr_uninstall22.pland create_uninstall_task.sh, that facilitate uninstalling TivoliManager for R/3 Version 2.2.0. Refer to ″Chapter 2. Planning forand Installing Tivoli Manager for R/3″ in the Tivoli Manager for R/3User’s Guide for complete details.

Patches Incorporated in Version 2.2.0The following patches have been incorporated into this release ofTivoli Manager for R/3:

¶ 2.1.0–SAP–0002

¶ 2.1.0–SAP–0004

Defects FixedThe following defects have been corrected in this release of TivoliManager for R/3:

¶ APAR IY12258. Parsing failure events from wr3mib.

¶ APAR IY13049. Installing the ABAP programs into an R/3 4.6Clandscape fails. Upgrading SAP R/3 to 4.6 breaks the ABAPbecause a field has been removed.

¶ APAR IY13480. TECAD is still creating events with themannode slot causing a parse failure on reception in the eventserver (sap_tecad.baroc).

¶ APAR IY13838. The CANCELLEDJOBMONITOR does notpopulate slots in the Tivoli Enterprise Console event.

¶ APAR IY14480. Whole number overflow on multiplication.

¶ APAR IY14485. Transport fails.

¶ APAR IY15143. SAP IDOC adapter does not obey the timeoutsettings.

Installation Notes


1.R

eleaseN

otes

¶ APAR IY20506. The Tivoli Manager for R/3 User’s Guide doesnot describe how to distribute a common set of event filteringcriteria to multiple endpoints.

¶ APAR IY23066. Tivoli Manager for R/3 Version 2.1 core dumps.

Known Product Defects, Limitations, andWorkarounds

This section describes known defects in this release of TivoliManager for R/3. Where applicable and known, suggestedworkarounds are identified. Note that this might not be a completelist of defects.

¶ The event adapter daemons do not start automatically on UNIXreboot.

Workaround: Start the r3mibIID, r3slogIID, r3idocIID, orr3moniIID daemons manually, or add the event adapter daemonsto your system startup.

¶ When installing a Tivoli Manager for R/3 product patch, such asthe Upgrade from Version 2.1 patch or patch 2.2.0–SAP–0001,you might experience an incomplete patch installation on yourendpoints if you have a configuration in which your R/3 objectsreside on a managed node other than on the endpoint’s currentgateway. In this situation, the updated Version 2.2.0 files will notbe installed on some endpoints and event adapters will not beupgraded.

Workaround: Run either the 210SAP0006LCF.init or the220SAP0001LCF.init script from the$BINDIR/../generic_unix/TME/SAP directory on the managednode where the R/3 objects reside.

¶ The CCMS Event Adapter does not report any R/3 alerts. TheCCMS Event Adapter log file shows a return code of 338 fromfunction module BAPI_SYSTEM_MT_CREATEBYTEMPL.This problem occurs when using R/3 clients other than 000.

Workaround: This problem is due to an incompletelyconfigured R/3 client. The R/3 basis administrator must maintainthe time zone table TTZZ in the target client to make an entry

Defects Fixed

14

for UTC. Because table TTZZ is client dependent, the R/3 basisadministrator must make a UTC entry for every R/3 client thatthe CCMS Event Adapter logs on to.

¶ When configuring R/3 authorizations for the Tivoli R/3 user ID,authorization T_5618443201 could not be assigned toauthorization object S_LOG_COM. This problem occurs withR/3 releases prior to release 4.6.

Workaround: Authorization T_5618443201 does not exist priorto R/3 release 4.6. Use authorization S_LOGCOM_ALL forauthorization object S_LOG_COM.

¶ Uninstalling Tivoli Manager for R/3 from endpoints fails whenthe name of the endpoints’ gateway includes a space. Thefollowing message is displayed for each endpoint on which theuninstall failed:resource $BINDIR/../lcf_bundle/bin/w32-ix86/TME/SAP/2.2C/wbindmsg.exe not found

Workaround: After uninstalling Tivoli Manager for R/3 fromthe Tivoli server, run the following command from the Tivoliserver:wgateway "gatewayName" dbcheck

Then run the Uninstall Tivoli Manager for R/3 Version 2.2.0 taskon the appropriate endpoints.

¶ Sending CCMS Event Adapter events to a version 3.7 eventconsole causes extraneous events on the version 3.7 event server.These events consist of nonsense characters and are visible onlywhen using the wtdumprl command.

Workaround: None. An APAR has been opened against TivoliEnterprise Console to address this problem. The APAR numberis not available yet.

¶ Programs using RFC calls fail to open an RFC connection orcause the automatic discovery function to report incorrect systeminformation.

Workaround: This problem can occur when SAP debuggingvariables (CPIC_TRACE=3 and RFC_DEBUG=99) are set in the

Known Product Defects, Limitations, and Workarounds


1.R

eleaseN

otes

environment. Remove the the CPIC_TRACE and RFC_DEBUGvariables from the environment and retry the command or task.

¶ Tivoli Manager for R/3 database status reporting fails to reportDB2 status correctly. Tivoli Manager for DB2 status eventscontain an extra single quote ( ' ) causing Tivoli EnterpriseConsole to report parsing errors.

Workaround: None. APAR IY23821 has been opened againstTivoli Distributed Monitoring to address this problem.

¶ If $root_user is modified with the widmap command to containuser IDs that do not have sufficient authority, monitors fail withwrite permission errors. By default, $root_user is mapped to rootfor UNIX and Administrator for Windows.

Workaround: Ensure that $root_user is mapped to user IDs thathave write permission to the tmp directory where DistributedMonitoring writes log files.

¶ OS Collect CPU percentage values total to more than 100percent.

Workaround: None. This situation occurs only in R/3 4.5systems. In R/3 4.5, SAP introduced the IO Wait % parameter.The IO Wait percentage was included in the idle CPU time,making the idle CPU time higher than it actually was. SAPremoved the IO Wait % parameter in subsequent R/3 releases.

¶ Tivoli Manager for R/3 does not support routing events to asingle remote event server from both managed nodes and Tivoliendpoints in interconnected Tivoli management regions.

Workaround: None. Refer to the Tivoli Manager for R/3 User’sGuide for information about supported configurations formultiple regions.

¶ When using the automatic discovery function, the R/3 systempolicy region might not contain all R/3 application servers in theR/3 system.

Workaround: The automatic discovery function might beexperiencing resource contention problems for an R3Systemobject. Run automatic discovery again to discover the missingR/3 application servers.


16

¶ Unable to deploy the message server status monitor because themessage server is running on a machine without an R/3application server.

Workaround: Use the desktop to create a virtual R3AppServerobject pointing to the managed node or endpoint that is runningthe message server. On the Create R/3 Application Server dialog,enter any two digits to represent the instance ID. Deploy themessage server status monitor to this virtual R3AppServerobject. After creating the virtual R3AppServer object, be sure toremove it from the appropriate App Server List profile manager.

¶ On Windows NT, when running the wr3exist executable, theentry point _lc_collate_cp could not be found.

Workaround: The named entry point is provided in themsvcrt.dll file in the \winnt\system32 directory. The entrypoint cannot be found because the version of the msvcrt.dllfile is older than the version required by Tivoli Manager for R/3.

To correct this problem, replace the\winnt\system32\msvcrt.dll file with a later version. Toassist you, Tivoli Manager for R/3 ships a later version ofMicrosoft’s msvcrt.dll file in the %BINDIR%\..\..\lib\w32-ix86 directory. This version provides the needed entry point andallows wr3exist to run.

¶ When deleting multiple R/3 objects from an R/3 system policyregion, not all objects are deleted or objects appear as blackboxes.

Workaround: This problem occurs because the delete processdoes not correctly lock resources. Based on activity in the R/3system, another process might refresh the R/3 system objects listwhile the delete process is still running.

The long-term solution to this problem is to apply a TivoliFramework patch. The patch number was not available forinclusion in this Release Notes document prior to publication.

You might be able to workaround this problem. If your onlysymptom is that not all R/3 objects have been deleted, delete theobjects again. If your symptom includes R/3 objects appearing asblack boxes, contact Tivoli Customer Support.



1.R

eleaseN

otes

¶ When using Tivoli Enterprise Console event forwarding,duplicate FATAL and CRITICAL events are sent to the eventserver to which you are forwarding events. The duplicate eventsoccur because Tivoli Manager for R/3 is using a rule in thesap_tecad.rls file to forward all of its Tivoli EnterpriseConsole events, and Tivoli Enterprise Console is also using arule in the tecad_nv390fwd.rls file to forward all FATAL andCRITICAL events. Both rules are in effect, causing duplicateevents to be forwarded.

Workaround: None.

¶ Tivoli Enterprise Console events for the saposcol monitor haveinconsistent values in the hostname event slot. The monitor isdistributed to an R3AppServer object. If the R3AppServer objectis based on a managed node, the hostname event slot containsthe R/3 application server triplet name. If the R3AppServer isbased on a Tivoli endpoint, the hostname event slot contains theTCP/IP host name.

Workaround: None. APAR IY11845 has been opened againstTivoli Distributed Monitoring to address this problem.

¶ When running the Display OS/390 Information task or whenrunning monitors from the OS/390 monitoring source on an R/34.5B system, errors are reported indicating that the databaselogical destination could not be established.

Workaround: Apply the ABAP fix that is described in SAPOSS note 164660.

¶ When running Tivoli Manager for R/3 and Tivoli Manager forMQSeries in an AS/400 environment, Tivoli Manager forMQSeries tasks that are run on an AS/400 Tivoli endpoint fail.

Even though Tivoli Manager for R/3 does not support theAS/400 operating system, you might have installed both TivoliManager for R/3 and Tivoli Manager for MQSeries in yourenvironment. Tivoli Manager for R/3 uses the dependency setfeature of gateways to install files that Tivoli Manager for R/3requires on Tivoli endpoints. The method by which this is doneforces the dependency files to be installed on an endpoint, evenan AS/400 endpoint, whenever any task is run against that


18

endpoint. However, one of the files in the Tivoli Manager forR/3 dependency set is incompatible with AS/400 file namingconventions. This file naming incompatibility causes installationof the dependency set files from the gateways to the AS/400endpoints to fail, resulting in Tivoli Manager for MQSeries tasksfailing on AS/400 endpoints.

Workaround: Remove the Tivoli Manager for R/3 dependencyset from gateways that manage AS/400 endpoints. To do this,run the following sequence of commands on the appropriategateways. The first command removes the Tivoli Manager forR/3 dependency set from the gateway. The second commandensures that the gateway is not still running the Tivoli Managerfor R/3 dependency set.wdepset -e @DependencyMgr:sap_run_task_dep \-r depset @DependencyMgr:sap_tool_dep

wgateway gateway_name dbcheck

Note: Removing the Tivoli Manager for R/3 dependency setfrom a gateway will result in the inability to run theTivoli Manager for R/3 automatic discovery function onthe endpoints managed by that gateway.

¶ The alternate process described on Page 69 under the headingFiltering Events in the Tivoli Manager for R/3 User’s GuideVersion 2.2 does not work.

Workaround: None. This problem has been fixed in the newestrelease of this product, IBM Tivoli Monitoring for Applications,Version 5.1.0: mySAP.com.

¶ The event server is forwarding events to itself.

Workaround: When running the Configure Event Server job,ensure that the event server name specified in the Host Name ofthe Event Server field is a different event server than the onesending the events.

¶ The Start Event Adapter task cannot be run as a monitoraction.

Workaround: None. This task requires an argument. Argumentscan only be passed to Distributed Monitoring tasks if they are



|||

|||

|

||||

||

||

1.R

eleaseN

otes

TLL based. The Tivoli Manager for R/3 tasks are not TLL basedso they cannot be used in this context.

Product NotesThis section contains important information that you should considerwhen using Tivoli Manager for R/3.

New Requirement for Filter StatementsTivoli Manager for R/3 configuration files require special formattingfor Filter statements to work. If you are adding or updating Filterstatements, you must include a hexadecimal 03 characterimmediately preceding the event class name as shown in thefollowing example:Filter:Class=<0X03>SAP_SYSLOG_MSG

This requirement for Filter statements applies to the IDOC EventAdapter, the Syslog Event Adapter, and the CCMS Event Adapter,but it does not apply to the Alert Event Adapter. Although thischange was made for double-byte language support, the hexadecimal03 character must be included in Filter statements for all languages.

R/3 TransportsThe Tivoli Manager for R/3 User’s Guide provides instructions forinstalling ABAP programs into an R/3 landscape using an R/3transport. The transport files used in Tivoli Manager for R/3 Version2.2.0 are as follows:

Transport Data File Cofiles File

Base TV1R000269 TV1K000269

OS/390 Extension (Thistransport must beinstalled after the basetransport.)

TV1R000204 TV1K000204

Accessing Product DocumentationThe following .pdf and the .htm documentation files are available onthe Tivoli Manager for R/3 CD in the /DOC directory.


20

||

Document Files

Tivoli Manager for R/3 User’s Guide¶ sa22mst.pdf

¶ sa22msttfrm.htm (framesversion)

¶ sa22mst.htm (non-framesversion)

View or print the .pdf files using the Adobe Acrobat Reader. Viewthe .htm files using your default Web browser.

Notes:

1. If you do not have Adobe Acrobat Reader, you can obtain itfree by clicking the Get Acrobat Reader icon andfollowing the steps that are provided at the Adobe Web site:

http://www.adobe.com

2. The Tivoli Manager for R/3 User’s Guide and the TivoliManager for R/3 Release Notes are also available in .htmand .pdf format at the following location on the Tivolisupport Web site:


InternationalizationThis section provides information about using Tivoli Manager forR/3 Version 2.2.0 with language support.

Enabling Language SupportTivoli Manager for R/3 Version 2.2.0 is translated into the followinglanguages:

Note: Language support is included on a separate CD, which willbe available shortly after the general release of TivoliManager for R/3 Version 2.2.0.

¶ Brazilian Portuguese

¶ Chinese (Simplified)

¶ Chinese (Traditional)

Product Notes


1.R

eleaseN

otes

http://www.adobe.com


¶ French

¶ German

¶ Italian

¶ Japanese

¶ Korean

¶ Spanish

To enable these languages, install the appropriate language supportpack from the Tivoli Manager for R/3 Language Support CD-ROMfrom the Tivoli desktop. For example, install the following pack forGerman language support:Tivoli Manager for R/3, Version 2.2.0 (de)

You can install multiple language support packs for a single product.Please note, however, to get full language enablement, you mustinstall the Framework language support pack in addition to thelanguage support pack for Tivoli Manager for R/3.

Tivoli Manager for R/3 language support also requires installation ofthe following product patch on all systems on which Tivoli Managerfor R/3 is installed:

2.2.0–SAP–0001

For instructions on installing products and for information aboutsetting up a non-English environment, refer to the Tivoli EnterpriseInstallation Guide Version 3.7.

To uninstall a Tivoli Manager for R/3 language support pack, use theR3Mgr_uninstall22.pl and the create_uninstall_task.sh scripts.Refer to ″Chapter 2. Planning for and Installing Tivoli Manager forR/3″ in the Tivoli Manager for R/3 User’s Guide for completedetails.

Translation DefectsEvery effort is made to translate the documentation clearly andaccurately, but terminology changes between versions of a productmay cause inconsistencies in the documentation.

Product Notes

22

Occasionally, you might notice that the text in a procedure does notagree with the accompanying screen capture. If this happens, alwaysfollow the instruction in the text.

The following list describes known translation defects in this releaseof Tivoli Manager for R/3. Where applicable and known, suggestedworkaround are identified. Note that this might not be a completelist of defects.

¶ When installing a French or Japanese Tivoli Manager for R/3language support pack on a Windows platform, the beforeinstallation script fails. The installation task output displays errormessages from the tar and mv commands. APAR IY16151 hasbeen opened against Tivoli Management Framework to addressthis problem.

Workaround: Manually perform the tasks in the beforeinstallation script. To do this, follow these steps:

1. On the Tivoli server, go to the $BINDIR/../../msg_catdirectory and check for the fr_FR or ja_JP subdirectory, orboth. If either the fr_FR or the ja_JP subdirectory does notexist, you do not need to perform any additional steps. Ifeither the fr_FR or the ja_JP subdirectory exists, proceed tothe next step.

2. Stop the Tivoli Object Dispatcher (oserv) process from theServices applet in the Windows Control Panel.

3. Do one of both of the following as appropriate:

v Copy $BINDIR/../../msg_cat/fr/* into$BINDIR/../../msg_cat/fr_FR, overwriting the existingfiles.

v Copy $BINDIR/../../msg_cat/ja/* into$BINDIR/../../msg_cat/ja_JP, overwriting the existingfiles.

4. Do one or both of the following as appropriate:

v Rename $BINDIR/../../msg_cat/fr_FR to$BINDIR/../../msg_cat/fr.

Product Notes


1.R

eleaseN

otes

v Rename $BINDIR/../../msg_cat/ja_JP to$BINDIR/../../msg_cat/ja.

v Restart the oserv process.

¶ Messages are displayed in English in non-English environmentsin the following situations:

v Uninstalling Tivoli Manager for R/3 from endpoints.

v Running the Start Event Adapter task on an R/3 applicationserver that is down.

v Running the Configure Windows 95/98 Client Install job.

v Running any task that executes an R/3 script, such as thetasks that start and stop R/3 system or server objects. Ingeneral, R/3 scripts are not translated. For more information,refer to the R/3 documentation.

Workaround: None.

¶ RFC error messages are returned in the default system language(the language set when the RFC was configured).

Workaround: None.

¶ Because Tivoli Manager for R/3 uses other Tivoli products andtheir language support packages, you might see translationdefects that are related to those products and not to TivoliManager for R/3. In particular, note the following:

v When using the BIG5 locate on AIX 4.3.3, the Tivoli desktopexhibits a strong flicker when the mouse pointer is movedover object for which status bar messages are associated.

v Some dialog controls for prerequisite products can displayEnglish labels in non-English environments. This problem islimited to Windows platforms.

Workaround: Refer to the documentation for the appropriateprerequisite products to find solutions to these problems.

Product Notes

24

Part Number: CTON71E

Printed in U.S.A.

GI10-3024-06

(1P)

P/N:

CTON71E

tivoli manager for r/3 release notes

Documents