Tivoli Header

Release Notes


Known Product Limitations and Workarounds for Version 3.1.0

This section describes limitations in Tivoli Manager for Domino, Version 3.1.0. The following table lists these limitations by category and describes workarounds, as applicable. The list might not be complete.

Table 4. Limitations and Workarounds

Description Workaround
Software Limitations
Important: Running the installation routine for the product does not complete the installation of the product. Obtain Patch 3.1-NOT-002 from Tivoli Customer Support and install it.
Note:
You must install this patch prior to using the product. Please refer to the readme file for that patch for important instructions.
When you are using Tivoli Framework, Version 3.7, a patch is required before you can install Tivoli Manager for Domino, Version 3.1.0. Obtain Patch 37-TMF-0010 from Tivoli Customer Support and install it.
When you are using Tivoli Distributed Monitoring, Version 3.6.2, a patch is required before you can install Tivoli Manager for Domino, Version 3.1.0. Obtain Patch 3.6.2-DMN-0001 from Tivoli Customer Support and install it.
Monitors fail to execute properly when you are using Tivoli Distributed Monitoring, Version 3.7. Obtain 3.1-NOT-002 for Tivoli Manager for Domino, Version 3.1.0, from Tivoli Customer Support and install it.
If the management console cannot communicate with the Tivoli server, the console stops functioning. When this occurs, the console displays one of the following exceptions: ExObjAdapter failure or connection to oserv lost. Stop and restart the management console to re-establish communication with the Tivoli server.
When you run the management console in a browser environment, the browser buttons do not correctly restart the applet. To restart the applet, close and restart all instances of the Web browser.
When you run the tmd_cr_db.sh and tmd_rm_db.sh scripts for DB2(R), the following error message is displayed: SQL1092N "xxxx" does not have the authority to perform the requested command. These scripts cannot be run because the DB2 user for which the script prompts does not match the DB2 user with access to run DB2 commands. You must log on to the machine as a valid DB2 user and extract the DbSetup.tar file so that you become owner of these files and have executable access. DB2 users also must be valid Tivoli users so they can run the tmd_cr_db.sh and tmd_rm_db.sh scripts.
To run Distributed Monitoring for Tivoli Manager for Domino on Tivoli Framework 3.7 in the OS/400 environment, you need Framework Patch 18. This patch fixes the w4fix_interp.pl script that was shipped with the 3.7-TMF-0007 patch. Without this patch, Distributed Monitoring for Tivoli Manager for Domino does not run on the OS/400 operating system. Obtain patch 3.7-TMF-0018, called Patch 18, from Tivoli Customer Support and install it.
If you are running the product on the OS/400 operating system with Tivoli Framework 3.7, the wtmdstartserver command fails in the Tivoli management region and displays the following error message:
wlseng fails for endpoint, unrecognized interp
Obtain patch 3.7-TMF-0018, called Patch 18, from Tivoli Customer Support and install it.
When you start the management console in a Web browser, a Java Plug-in security warning pop-up message is displayed. This message occurs because the digital certificate on the version of Java Help that is shipped with the applet has expired. You can ignore the warning and continue loading the applet by clicking Yes on the dialog box.
Only one instance of the management console runs for each instance of the Java Virtual Machine (JVM). Any attempt to load the management console while an instance of the management console is already active results in an error message. The Java Plug-in JVM is started when the applet is initially loaded in a browser window. The JVM remains active until all instances of the browser window are closed. The Lotus Notes client JVM is started when the first applet is loaded in the Notes client. The JVM remains active until all Notes client applications, including Notes Designer and the Administration client, are closed. Run only one instance of the management console at a time.
OS/400 has no Tivoli Enterprise Console standalone rules engine. It sends all Tivoli Manager for Domino events directly to the Tivoli Enterprise Console server. As on other operating systems, you can use the Start TEC Engine and Stop TEC Engine functions to control the sending of events to the Tivoli Enterprise Console server. None.
Tivoli Data Protection for Domino does not currently support OS/400. None.
Internationalization Limitations
DPSRoundTripMail probe does not automatically work in non-English versions of the product. Install a patch and change system settings for the Domino Performance Station that you want to probe, as described in these release notes in the "Correcting the Behavior of DPSRoundTripMail in Non-English Versions of the Product".
Some English text, resource names, resource types, window tabs, and monitor names that come from external sources are not fully translated. None.
Some windows or buttons are smaller than the text they contain. Resize the window to display the text.
For Korean and Simplified Chinese only: The management console uses the default fonts from Internet Explorer and Netscape. Customize the font selections by modifying the font properties for your browser.
Reports that obtain information from the endpoints display in English. Push the National Language Support pack to the endpoint. See "Installing Non-English Report Templates" for details.
On the help window for the management console, flyover icon labels such as previous, next, print, and page setup are displayed only in English. Also, if you select the Index or the Search tab, Find is displayed only in English. None.
Documentation Limitations
Updates were made in the individual monitor and task information that are not reflected in the Tivoli desktop or command line help. In some cases, updates were made to the command line syntax. See the Tivoli Manager for Domino Reference Guide for the most up-to-date information about commands, tasks, and monitors.
Sending Monitor or Probe Data to Reports: The Tivoli Manager for Domino User's Guide states that you can add the Data Rollup Interval monitor as a probe for performance stations from the Basics group. The only probes or monitors listed are from the performance station group and the Data Rollup Interval monitor is not displayed. Data rollup for performance stations and data rollup for Domino servers are different. A Data Rollup Interval monitor is distributed automatically when you create a new instance of a performance station object. There is no need to explicitly create and distribute a Data Rollup Interval monitor for a performance station. This monitor runs every 15 minutes, and the only way to modify this interval is from the Tivoli desktop or command line interface (using the wsetmon command). This monitor is unavailable in the management console. To submit data for reporting, you must configure a probe to log to file on the always Distributed Monitoring response level.
The Running a Task help topic states that the tools in the Tools > Diagnostics menu correspond to the Tivoli Manager for Domino tasks. This is true for the tasks in the Domino Server Tasks task library, but not for the Client Distribution Operations 3.1, Domino Performance Station Tasks, and TMD Configuration task libraries. None.
In Chapter 3, Installing Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide in Preparing for Installation, the Required Software reference in Table 3 must change to state only that Application Services, Version 1.2, is required for Tivoli Manager for Domino, Version 3.1.0. Previous versions of Application Services do not work with this product. If you are using an earlier version of Applications Services, you must upgrade to Version 1.2.
In Chapter 3, Installing Tivoli Manager for Domino, of the Tivoli Manager for Domino User's Guide in Preparing for Installation, change the reference in Table 4 from "AS/400" to "OS/400." None.
Currently only PDF file format is supported when you save a graph to a file in the management console. None.
The Refresh button no longer exists in the graph view of the management console. To refresh this view, you must close the view and click View again.


[ Top of Page | Previous Page | Next Page | Table of Contents ]