IBM Tivoli Enterprise Console. Release Notes. Version 3.9 SC

Transcription

1 IBM Tioli Enterprise Console Release Notes Version 3.9 SC

2 Note Before using this information and the product it supports, read the information in Notices on page 41. First Edition (August 2003) This edition applies to ersion 3 release 9 of IBM Tioli Enterprise Console (product number 5698-TEC) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents IBM Tioli Enterprise Console ersion 3.9 release notes Contents About this release New in this release Tioli Enterprise Console product images Product fix history Backward compatibility Product compatibility Product notes Software requirements Required Tioli Management Framework patches 4 Required Windows operating system serice packs 5 Required AIX patches for JRE support... 5 Required HP-UX patches for JRE support.. 6 Required Solaris patches for JRE support.. 6 Known limitations, problems, and workarounds.. 6 Limitations Known problems and workarounds Installation Eent consoles Rules Adapters Scripts Documentation notes Documentation changes Documentation updates Internationalization notes Enabling language support Eent adapter and eent serer compatibility.. 24 Custom applications built with Tioli Eent Integration Facility Eent adapters Non-English data in adapter format files.. 27 Non-English data in filters in adapter configuration files Troubleshooting tips Installing a language pack on a non-tioli eent console Software limitations, problems, and workarounds for internationalization issues Appendix A. Upgrading from ersion Eent adapters no longer shipped Tioli Enterprise Data Warehouse enablement Eent database configuration using the installation wizard Graphical rule builder Rule enhancements Prefixes used in prolog file names Upgrading rule bases to ersion Deprecated BAROC features Changes to the first_instance and all_instances predicates Differences in predicate behaior from past releases 31 Appendix B. Defects corrected in ersion Appendix C. Jaadoc HTML documentation for the EentList class. 37 com.tioli.zce.engine Class EentList Constructor Summary Method Summary Constructor Detail EentList EentList Method Detail seteentat eentat size remoelast length tostring Notices Trademarks Copyright IBM Corp iii

4 i IBM Tioli Enterprise Console: Release Notes

5 IBM Tioli Enterprise Console ersion 3.9 release notes Contents About this release The IBM Tioli Enterprise Console Release Notes proides important information about the IBM Tioli Enterprise Console product. These Release Notes are the most current information for the Tioli Enterprise Console product and take precedence oer all other documentation. Reiew these Release Notes thoroughly before installing or using this product. Note: The IBM Tioli Enterprise Console Release Notes might be updated from time to time. You can find the most current ersion of these Release Notes at the following Web site: These release notes include the following topics: New in this release Tioli Enterprise Console product images Product fix history Backward compatibility Product compatibility Product notes Software requirements Known limitations, problems, and workarounds Documentation notes Internationalization notes This section includes information about what is new, what has been fixed, and compatibility issues for this release. New in this release This section describes what is new in this release. HP-UX and Windows NT operating systems are no longer supported, and any reference to these operating systems in the documentation is not alid. Although the Windows NT operating system is not supported, as a conenience, the Windows NT eent log adapter is aailable as part of the Adapter Configuration Facility in release 3.9; and you can distribute the Windows NT eent log adapter to Windows NT endpoints. Web ersion of the eent console, which you can use to manage eents from a Web browser. Start_Maintenance task, which you can use to inform the eent serer about computers that are in maintenance mode. Simplified packaging of the Tioli Eent Integration Facility. The Tioli Eent Integration Facility is no longer an installable component of the Tioli Enterprise Console product. This facility is a toolkit that is aailable on the product images but does not need to be installed. Howeer, the Jaadoc HTML documentation Copyright IBM Corp

6 for the EentList class has been inadertently omitted from the Tioli Eent Integration Facility. See Appendix C, Jaadoc HTML documentation for the EentList class, on page 37 for this information. Tioli Enterprise Console gateway can now receie eents from non-tme adapters. Enhancements to state correlation including: Correlation of eents from TME adapters with eents from non-tme adapters at the Tioli Enterprise Console gateway Support for customizable actions New state correlation rules For more information, refer to Part 2 of the IBM Tioli Enterprise Console Rule Deeloper s Guide. New Default rule base, which includes preconfigured rule sets that proide support for processing common application and infrastructure eents. The rules in the Default rule set proide functions that include the following: Causal analysis of network infrastructure and e-business application eents based on serice impact and dependency relationships Scheduling of maintenance windows and discarding of eents from systems currently undergoing maintenance Integration with external trouble ticket systems Heartbeat monitoring and detection of missed heartbeat pulses For more information, refer to the IBM Tioli Enterprise Console Rule Set Reference. Enhancements to unified system and network management including: Rules that correlate system-related and network-related eents, which are based on predefined associations and help in performing root cause analysis. Rules that understand and automatically process network eents. Predefined eent console and eent groups for IBM Tioli NetView eents, which you can use to manage these eents immediately. Optimized eent management for key e-business applications including: Predefined eent consoles and eent groups for IBM WebSphere MQ, IBM DB2, and IBM WebSphere Application Serer eents. Rules based on predefined associations among the WebSphere MQ, the DB2, and the IBM WebSphere Application Serer applications that help you identify the root cause of a problem. Predefined eent groups for all eents in open and acknowledged state and maintenance eents that are not closed. A default eent console that is assigned to the root administrator and to which all predefined eent groups are assigned. Improed installation wizard that helps you complete the following tasks: Configure an eent database. The ersion 3.8 eent database installation wizard has been integrated into the installation wizard. Install the product components. Installation of the Windows non-tioli Jaa ersion of the eent console has been integrated into the installation wizard. Uninstall and upgrade the product components as appropriate. Enhanced Tioli Data Warehouse Enablement Pack that extracts aailability data from the eent database for outage reporting by IBM Tioli Serice Leel 2 IBM Tioli Enterprise Console: Release Notes

7 Adisor. For more information, refer to the IBM Tioli Enterprise Console Warehouse Enablement Pack: Implementation Guide. Tioli Enterprise Console product images The following list describes the Tioli Enterprise Console product images: IBM Tioli Enterprise Console Version 3.9 New Installations IBM Tioli Enterprise Console Version 3.9 Non-TME Installations IBM Tioli Enterprise Console Version 3.9 Upgrade IBM Tioli Enterprise Console Version 3.9 Installation Wizard IBM Tioli Enterprise Console Version 3.9 Language Pack IBM Tioli Enterprise Console Version 3.9 Tioli Data Warehouse Integration Product fix history For information about the defects that hae been corrected in this release, see Appendix B, Defects corrected in ersion 3.9, on page 33. Backward compatibility The following list describes the compatibility issues for the Tioli Enterprise Console product. The following compatibility issues exist when using mixed ersions of Tioli Enterprise Console components: Eent serers, user interface (UI) serers, eent consoles, and the Adapter Configuration Facility must be at the same ersion. For example, a ersion 3.9 eent console works with a ersion 3.9 UI serer, and a ersion 3.9 UI serer works with a ersion 3.9 eent serer. Using mixed ersions of components is not supported, and unexpected results can occur. Ensure that the Tioli Enterprise Console components are of the same ersion. Adapters can generally send eents to any currently supported ersion of the eent serer, and the eent serer can successfully receie the eent information. Howeer, compatibility issues exist for sending eents from adapters in non-english enironments. If you are combining different ersions of adapters and eent serers in a non-english enironment, see Eent adapters on page 25 for additional information. To forward eents from ersion 3.9 rules to a ersion of the eent serer prior to ersion 3.9, you must update the root.baroc file in the prior ersion to include the fqhostname eent attribute in the EVENT class, which contains the fully qualified host name of the machine. Otherwise, these eents will fail with a PARSING_FAILED error. Add the following entry to the attribute list: fqhostname STRING; Alternatiely, for ersion 3.7.1, you can apply Fix Pack 5 (3.7.1 TEC FP05) to obtain the update for the fqhostname eent attribute. For ersion 3.8, you can apply Fix Pack 1 (3.8.0 TEC FP01) to obtain the update for the fqhostname eent attribute. Because changes hae been made to the Default rule base in ersion 3.9, the ersion 3.9 rule base does not work with prior ersions of the Tioli Enterprise Console product. To use the new Default rule base and the preconfigured rule sets, you must install ersion 3.9 of the Tioli Enterprise Console product. Because of dependencies on changes made to the rules in ersion 3.9 of the Tioli Enterprise Console product, the rules shipped with ersion 1.2 of the warehouse enablement pack do not work with prior ersions of the Tioli IBM Tioli Enterprise Console ersion 3.9 release notes 3

8 Enterprise Console product. To use the preconfigured rules that ersion 1.2 of the warehouse enablement pack proides, you must install ersion 3.9 of the Tioli Enterprise Console product. Product compatibility The following list describes compatibility issues when using other products with the Tioli Enterprise Console product. When using both the Tioli Enterprise Console product and the Tioli Risk Manager product, you must install the IBM WebSphere Application Serer product that is proided with the Tioli Enterprise Console product on a different computer than the Tioli Risk Manager Information Facility to aoid port contention problems. The ersion of Tioli Aailability Intermediate Manager (ersion 3.7) that is shipped with ersion 3.9 of the Tioli Enterprise Console product is the same ersion that was shipped with ersion and ersion 3.8 of the Tioli Enterprise Console product. Product notes If you are upgrading from ersion to ersion 3.9 of the Tioli Enterprise Console product, see Appendix A, Upgrading from ersion 3.6.2, on page 29. Software requirements This section describes the patches that the Tioli Enterprise Console product requires and supplements the software requirements described in the IBM Tioli Enterprise Console Installation Guide. Required Tioli Management Framework patches The following Tioli Management Framework patches are required for ersion 3.9 of the Tioli Enterprise Console product. 4 IBM Tioli Enterprise Console: Release Notes

9 Table 1. Required Tioli Management Framework patches Tioli Management Framework ersion Operating system Required patches AIX, HP-UX, Solaris Operating Enironment, and Windows TMF TMF 0099 Linux 3.7 TMF 0016 Patches TMF 0097 and TMF 0099 are included in Tioli Management Framework Version Fix Pack 4. You can obtain the required patches for Tioli Management Framework Version from the following Web site: ftp://ftp.software.ibm.com/software/tioli_support/ patches/patches_ TMF TMF 0090 You can obtain these patches from the following Web site: 4.1 AIX, HP-UX, Solaris, Windows, Linux ftp://ftp.software.ibm.com/software/tioli_support/ patches/patches_ TMF 0010E To obtain this patch, contact IBM Software Support. 4.1 TMF 0013 To obtain this patch, use ftp://ftp.software.ibm.com/software/tioli_support/ patches/patches_4.1/4.1-tmf TMF 0014 To obtain this patch, use ftp://ftp.software.ibm.com/software/tioli_support/ patches/patches_4.1/4.1-tmf TMF 0015 To obtain this patch, use ftp://ftp.software.ibm.com/software/tioli_support/ patches/patches_4.1/4.1-tmf-0015 Required Windows operating system serice packs For Windows 2000, download the following serice pack from the Microsoft Download Center: Q259728_W2K_SP1_x86_en.exe Required AIX patches for JRE support The following AIX patches are required to support Jaa Runtime Enironment (JRE) Version Table 2. Required AIX patches for JRE support AIX AIX AIX AIX IBM Tioli Enterprise Console ersion 3.9 release notes 5

10 Required HP-UX patches for JRE support The following HP-UX patches are required to support JRE Version Table 3. Required HP-UX patches for JRE support HP-UX (PA-RISC) HP-UX 11i (PA-RISC) PHCO_26060 PHCO_26089 PHCO_26111 PHCO_26960 PHCO_27375 PHCO_27731 PHKL_18543 PHKL_23409 PHKL_26136 PHKL_27282 PHKL_28180 PHKL_28202 PHNE_23003 PHNE_27886 PHNE_28102 PHNE_24937 PHSS_26559 PHSS_26637 PHSS_26945 PHSS_26972 PHSS_26974 PHSS_26976 PHSS_27869 PHSS_28366 PHSS_28469 PHCO_26061 PHCO_27632 PHCO_27740 PHCO_27958 PHKL_24751 PHKL_25233 PHKL_25993 PHKL_25994 PHKL_27091 PHKL_27094 PHKL_27096 PHKL_27316 PHKL_27317 PHKL_27686 PHKL_28122 PHKL_28267 PHKL_28089 PHKL_28103 PHSS_26971 PHSS_26973 PHSS_26975 PHSS_26977 PHSS_28370 PHSS_28470 Required Solaris patches for JRE support Obtain the required Solaris patches for JRE support from the following Web site: Known limitations, problems, and workarounds Limitations This section describes known software limitations and problems in ersion 3.9. Workarounds are proided when applicable. For software limitations, problems, and workarounds related to internationalization, see Internationalization notes on page 24. When using the installation wizard, users must specify a temporary directory to which the installation wizard can copy files for use. This temporary directory 6 IBM Tioli Enterprise Console: Release Notes

11 must not contain a subdirectory named tec39 or important files in that subdirectory might be mistakenly deleted. During installation, the installation wizard creates the tec39 subdirectory under the user-specified directory. The installation wizard then copies seeral installation files to that directory and restarts from that temporary location. When the installation wizard finishes, it remoes this tec39 subdirectory and deletes all of the files contained in it regardless of whether it placed those files in this directory or not. When using the Web ersion of the eent console, Web browser controls, such as Refresh, which are aailable are not supported. Using Web browser controls when running the Web ersion of the eent console can cause unpredictable results. The supported configuration for a Web browser that is running the Web ersion of the eent console is to allow cookies. Because preference settings are stored in cookies, allowing cookies enables preferences to persist across login sessions. Disabling cookies during a login session of the Web ersion of the eent console is not supported. The IBM WebSphere Application Serer product proides URL rewriting as an alternate method of storing session information in a Web browser. Howeer, URL rewriting does not persist the session information across login sessions. Using URL rewriting is not supported for the Web ersion of the eent console. Control characters in the message of an eent cause the eent to fail with a PARSING_FAILED error. When using the Jaa ersion of the eent console, effect eents might not be displayed in the Effect Eents area of the Related Eents tab for an eent group. This situation can happen when an eent group definition does not match the rules definitions. For example, if an eent group is configured to display only open and acknowledged eents and your rules close some effect eents, the eent group filters out the closed effect eents. If you want the eent group to include the effect eents, modify the eent group definition. Popup blocking software might interfere with the Web ersion of the eent console. For example, some of the operations of the Web ersion of the eent console start new browser sessions, and popup blocking software might preent these new sessions from starting. When using the Web ersion of the eent console, either ensure that popup blocking software is not running, or consult the documentation for the popup blocking software to configure the software properly. Known problems and workarounds This section describes known defects in this release of the Tioli Enterprise Console product. Where applicable and known, suggested workarounds are identified. Note that this might not be a complete list of defects. Installation This section describes problems with installation of the base product and configuration of the eent database. Tioli Enterprise Console installation and upgrade: The following problems and workarounds relate to installing or upgrading the base Tioli Enterprise Console product: Problem: Importing the IBM Tioli Monitoring BAROC and rule set files (either manually or by using the IBM Tioli Monitoring dmae_tec_inst.sh script) into the Tioli Enterprise Console rule base fails if the target rule base contains any of the following BAROC files: IBM Tioli Enterprise Console ersion 3.9 release notes 7

12 DB2Agents.baroc DB2CpuUtilization.baroc DB2DatabaseStatus.baroc DB2_Eent.baroc DB2HostThroughput.baroc DB2InstanceStatus.baroc itmwas_dm_eents.baroc WebSphere_MQ_Channel.baroc WebSphere_MQ_Queue.baroc WebSphere_MQ_QueueManager.baroc This problem can occur because the Tioli Enterprise Console product ships a subset of the BAROC files for the IBM Tioli Monitoring, the IBM Tioli Monitoring for Business Integration: WebSphere MQ, the IBM Tioli Monitoring for Databases: DB2, and the IBM Tioli Monitoring for Web Infrastructure: WebSphere Application Serer products as part of the Default rule base. Workaround: Before integrating IBM Tioli Monitoring with the Tioli Enterprise Console product, you must modify your target rule base. To do this, use the before and after installation scripts that the Tioli Enterprise Console product proides. Alternatiely, you can manually perform the steps that the before and after installation scripts perform. Using the before and after installation scripts To use the before and after installation scripts to enable IBM Tioli Monitoring to integrate with the Tioli Enterprise Console product, follow these steps: 1. Copy the pre-installation script, before_install.sh, and the post-installation script, after_install.sh, from the $BINDIR/TME/TEC/contrib directory to the directory in which the target rule base resides. 2. Run the pre-installation script from the directory in which the target rule base resides. Enter the following command:./before_install.sh target_rule_base ITM Where target_rule_base is the name of the rule base to which you will be importing the IBM Tioli Monitoring BAROC files. 3. Run the IBM Tioli Monitoring dmae_tec_inst.sh script or manually import the IBM Tioli Monitoring BAROC and rule set files. For more information, refer to the IBM Tioli Monitoring User s Guide. 4. Run the post-installation script from the directory in which the target rule base resides. Enter the following command:./after_install.sh target_rule_base ITM Manual steps: 8 IBM Tioli Enterprise Console: Release Notes To manually enable IBM Tioli Monitoring to integrate with the Tioli Enterprise Console product, follow these steps: 1. Create a temporary subdirectory in the directory in which the target rule base resides. 2. If the ebusiness rule set was imported in the EentSerer target of the target rule base, delete this rule base from the EentSerer target. 3. If the ebusiness rule set has been imported into the target rule set:

13 a. Copy the ebusiness.rls file from the TEC_RULES directory of the target rule base to the temporary subdirectory that you created in step 1 on page 8. b. Delete the ebusiness rule set from the target rule base. 4. Copy the following BAROC files from the TEC_CLASSES directory of the target rule base to the temporary directory: DB2DatabaseStatus.baroc DB2CpuUtilization.baroc DB2HostThroughput.baroc DB2Agents.baroc DB2_Eent.baroc DB2InstanceStatus.baroc itmwas_dm_eents.baroc WebSphere_MQ_Queue.baroc WebSphere_MQ_QueueManager.baroc WebSphere_MQ_Channel.baroc 5. Delete the following BAROC files from the target rule base in the following order: a. DB2InstanceStatus.baroc b. DB2DatabaseStatus.baroc c. DB2CpuUtilization.baroc d. DB2HostThroughput.baroc e. DB2Agents.baroc f. DB2_Eent.baroc g. itmwas_dm_eents.baroc h. WebSphere_MQ_Queue.baroc i. WebSphere_MQ_QueueManager.baroc j. WebSphere_MQ_Channel.baroc 6. Run the IBM Tioli Monitoring dmae_tec_inst.sh script or manually import the IBM Tioli Monitoring BAROC and rule set files. For more information, refer to the IBM Tioli Monitoring User s Guide. 7. From the temporary directory, import the following BAROC files into the target rule base in the following order: a. WebSphere_MQ_Channel.baroc b. WebSphere_MQ_QueueManager.baroc c. WebSphere_MQ_Queue.baroc d. itmwas_dm_eents.baroc e. DB2_Eent.baroc f. DB2Agents.baroc g. DB2HostThroughput.baroc h. DB2CpuUtilization.baroc i. DB2DatabaseStatus.baroc j. DB2InstanceStatus.baroc 8. If the ebusiness.rls file exists in the temporary directory, import the ebusiness.rls file into the target rule base and import the ebusiness rule set into the EentSerer target of the target rule base. 9. Compile and load the target rule base. IBM Tioli Enterprise Console ersion 3.9 release notes 9

14 10. Delete the temporary directory and its contents. 11. Stop and restart the eent serer. Problem: When integrating the IBM Tioli Monitoring for Databases: DB2 product with the Tioli Enterprise Console product using the ECC_Configure_TEC_Classes task, a new rule base is created. When copying from an existing rule base to create the new rule base, the integration fails if the rule base to be copied contains any of the following BAROC files: DB2_Eent.baroc DB2Agents.baroc DB2HostThroughput.baroc DB2CpuUtilization.baroc DB2DatabaseStatus.baroc DB2InstanceStatus.baroc This problem can occur because the Tioli Enterprise Console product ships a subset of the BAROC files for the IBM Tioli Monitoring for Databases: DB2 product as part of the Default rule base. Workaround: Before integrating the IBM Tioli Monitoring for Databases: DB2 product with the Tioli Enterprise Console product, you must modify the rule base to be copied. To do this, use the before and after installation scripts that the Tioli Enterprise Console product proides. Alternatiely, you can manually perform the steps that the before and after installation scripts perform. Using the before and after installation scripts To use the before and after installation scripts to enable the IBM Tioli Monitoring for Databases: DB2 product to integrate with the Tioli Enterprise Console product, follow these steps: 1. If the rule base to be copied is the Default rule base, create an interim copy of the Default rule base. This is required because the Default rule base cannot be modified. Follow these steps: a. Enter the following command to create a new rule base: wrb crtrb path directory Default_copy Where directory is the directory in which you want to create the rule base files. b. Enter the following command to copy the Default rule base files into the Default_copy rule base: wrb cprb force Default Default_Copy 2. Copy the pre-installation script, before_install.sh, and the post-installation script, after_install.sh, from the $BINDIR/TME/TEC/contrib directory to the directory that contains the rule base you want to copy. 3. Run the pre-installation script from the directory that contains the rule base you want to copy. Enter the following command:./before_install.sh copy_rule_base DB2 Where copy_rule_base is the name of the rule base you want to copy. 4. Run the ECC_Configure_TEC_Classes task to import the IBM Tioli Monitoring for Databases: DB2 BAROC and rule set files. For more information, refer to the IBM Tioli Monitoring for Databases: DB2 User s Guide. 10 IBM Tioli Enterprise Console: Release Notes

15 5. Run the post-installation script from the directory that contains the rule base that was copied. Enter the following command:./after_install.sh target_rule_base DB2 Where target_rule_base is the name of the target rule base. Manual steps: To manually enable the IBM Tioli Monitoring for Databases: DB2 product to integrate with the Tioli Enterprise Console product, follow these steps: 1. If the rule base to be copied is the Default rule base, create an interim copy of the Default rule base. This is required because the Default rule base cannot be updated. Follow these steps: a. Enter the following command to create a new rule base: wrb crtrb path directory Default_copy Where directory is the directory in which you want to create the rule base files. b. Enter the following command to copy the Default rule base files in to the Default_copy rule base: wrb cprb force Default Default_Copy 2. Create a temporary subdirectory in the directory that contains the rule base you want to copy. 3. If the ebusiness rule set was imported in the EentSerer target of the target rule base, delete the ebusiness rule base from the EentSerer target. 4. If the ebusiness rule set has been imported into the rule set to be copied: a. Copy the ebusiness.rls file from the TEC_RULES directory of the rule base to be copied to the temporary subdirectory that you created in step 2. b. Delete the ebusiness rule set from the rule base to be copied. 5. Delete the following BAROC files from the rule base to be copied in the following order: a. DB2InstanceStatus.baroc b. DB2DatabaseStatus.baroc c. DB2CpuUtilization.baroc d. DB2HostThroughput.baroc e. DB2Agents.baroc f. DB2_Eent.baroc 6. Run the ECC_Configure_TEC_Classes task to import the IBM Tioli Monitoring for Databases: DB2 BAROC and rule set files. For more information, refer to the IBM Tioli Monitoring for Databases: DB2 User s Guide. 7. If the ebusiness.rls file exists in the temporary directory, import the ebusiness.rls file into the target rule base and import the ebusiness rule set into the EentSerer target of the target rule base. 8. Compile and load the target rule base. 9. Delete the temporary directory and its contents. 10. Stop and restart the eent serer. Problem: In ersion 3.9 of the Tioli Enterprise Console product, only one console can be assigned to an operator. If you are upgrading from ersion IBM Tioli Enterprise Console ersion 3.9 release notes 11

16 of the Tioli Enterprise Console product and hae multiple consoles assigned to a single operator, manual interention is required. Workaround: After the upgrade process has completed, update your console definitions to assign only one console to one operator. Problem: When you use Tioli Risk Manager 4.1 with Tioli Enterprise Console 3.9, setting the single_port_bdt option with the set_port_range option might cause the Tioli Risk Manager 4.1 installation to fail. Workaround: Set the single_port_bdt option without the set_port_range option. Problem: When installing the Tioli Enterprise Console product from a managed node in a Tioli enironment that consists of multiple locales, the output of the installation process might be corrupted. Workaround: In a Tioli enironment with multiple locales, install the Tioli Enterprise Console product from the Tioli serer. Problem: After upgrading the Tioli Enterprise Console product on RedHat Linux, there is high CPU usage due to the Jaa Runtime Enironment (JRE). Workaround: Set the enironment ariable using the following command: odadmin eniron set LD_ASSUME_KERNEL=2.2.5 Problem: The Tioli Enterprise Console installation wizard does not start on AIX 5.1 systems running with the GB18030 code page. This problem is because the GB18030 code page causes poor system performance. Workaround: Install the Tioli Enterprise Console product using a different code page than GB Problem: For SuSE and SuSE Linux Enterprise Serer (SLES) distributions of Linux, if the compress utility is not installed, you might experience problems, such as the rule base not being loaded or the eent serer not starting due to a missing rule base. The Tioli Enterprise Console product requires the compress utility, and more recent ersions of Linux distributions from SuSE do not include the compress utility. Workaround: Obtain the compress utility from an older leel of Linux distributions from SuSE. Problem: To install the Tioli Enterprise Console product on RedHat Linux, the Linux system must hae the compress command installed and aailable. Workaround: Check your RedHat Linux documentation for the compress package to install and access the compress command. Problem: Uninstalling a Tioli Enterprise Console component fails using the wuninst command if the host where the component was uninstalled contains both a managed node and an endpoint with the same name. Workaround: Use the following steps to uninstall a component: 1. Rename the label of the endpoint with the following command: wep old_endpoint_label set_label new_endpoint_label 2. Run the wuninst command to remoe the component. For more information about the wep command, refer to the Tioli Management Framework Reference Manual. For more information about using the wuninst command with Tioli Enterprise Console components, refer to the IBM Tioli Enterprise Console Installation Guide. Problem: Installation of the eent serer fails without the correct permissions to the temporary directory on the Tioli serer. Workaround: To install the eent serer, the file permissions for the temporary directory on the Tioli serer must hae both read and write access by all. For the UNIX operating system, the tmp subdirectory must hae permissions of 12 IBM Tioli Enterprise Console: Release Notes

17 777. For Windows, the Eeryone account needs at least read and write permissions for the $DBDIR\tmp directory, and all other users and groups need full control of the $DBDIR\tmp directory. Problem: When mounting the Tioli Enterprise Console, Version 3.9, CD installation images on HP-UX using the mount command or SAM, all file names end with the ;1 character string. HP-UX does not support the Rock Ridge format with the mount command. In some cases, the pfs_unmount command might be required to unmount the CD-ROM directory. Workaround: If you hae already mounted a Tioli Enterprise Console, Version 3.9, installation image CD using the mount command or using SAM, the CD-ROM must be unmounted with the unmount command before beginning. 1. Ensure that both the pfs_mountd and the pfsd processes are running. If they are not, start both processes using following commands: pfs_mountd & pfsd & 2. Mount the CD-ROM using the following command: /usr/sbin/pfs_mount /de/dsk/cd_deice mounting_point 3. Confirm that file names do not end with the ;1 character string. 4. After completing the installation, you can unmount the CD-ROM using the unmount command. If you are using HP-UX 11 or HP-UX 11i, you can download HP-UX patches to enable Rock Ridge format support using the standard mount command. For additional information, contact Hewlett-Packard customer support. Eent database installation and upgrade: The following problems and workarounds relate to installing or upgrading the eent database: Problem: Migration from ersion or ersion of the Tioli Enterprise Console product to ersion 3.9 does not drop the existing Tioli Enterprise Console table space due to potential conflicts with customer application tables and triggers. For Informix, Microsoft SQL Serer, and Sybase databases, the migration process does not drop the Tioli Enterprise Console database system area. Workaround: See the workaround for the appropriate database type. For a DB2 database: 1. Open a DB2 command line prompt. 2. At the prompt, enter the following sequence of commands: db2 connect to tecdb user user_id using password db2 drop tablespace tablespace_name Where tecdb is the name of the Tioli Enterprise Console database, user_id and password are the user ID and password of a user that has sufficient system priileges to drop a table space, and tablespace_name is the name of the Tioli Enterprise Console data table space. The table space name has the form userid_data. The DB2 database automatically remoes the data files and directories that were used by the table space. For an Informix database: To drop a deice that is no longer in use by a database, follow these steps: 1. Log in to the Informix serer or client machine as the Tioli Enterprise Console RIM user. IBM Tioli Enterprise Console ersion 3.9 release notes 13

18 2. Enter the following command to list the existing dbspaces and their associated physical files allocations: onstat -d 3. Enter the following command to remoe a dbspace: onspaces d dbspace_name y 4. When all the dbspace names hae been remoed, delete the physical files for each deice remoed. Refer to step 2 to know which physical file was allocated to each deice. For a Microsoft SQL Serer database: You do not need to delete any deices. The serer deletes any deices and their physical files when a database is dropped. For an Oracle database: 1. Start SQL*Plus. The user should log on to the Tioli Enterprise Console database as a user with SYSDBA priilege, such as SYS or SYSTEM. For example: sqlplus "sys/password@sid as sysdba" Where password is the password for the user and SID is the SID for the database. 2. Determine which data files are being used by the Tioli Enterprise Console ersion 3.7 data table space. To do this, enter the following command: SELECT file_name FROM dba_data_files WHERE tablespace_name = tablespace_name Where tablespace_name is the name of the Tioli Enterprise Console data table space. The table space name has the form userid_data. 3. Drop the Tioli Enterprise Console data table space with the following command: drop tablespace tablespace_name 4. Exit SQL*Plus. 5. If the table space was successfully dropped, delete the files that were listed in step 2. Note: The table space must be successfully dropped before deleting the data files. For a Sybase database: To drop a deice that is no longer in use by a database, follow these steps: 1. Log in to isql as sa. 2. Use the sp_helpdeice command to see the names of all logical deices and the physical files they reside on. Make a note of the logical file names and their physical file names. This information is unaailable after the serer is stopped and restarted in step Use the sp_dropdeice command followed by the logical deice name to remoe the appropriate deices. For example: sp_dropdeice mydeice Ensure that these deices are no longer in use by any database before remoing them. 4. Stop and restart the Sybase serer. 14 IBM Tioli Enterprise Console: Release Notes

19 5. Delete the physical files for each deice remoed. Refer to step 2 on page 14 to determine which physical file was allocated to each deice. Problem: When using the wtdbspace command with a Sybase database, you might encounter a RIM error. RIM trace output might display an error message similar to the following example: Sybase Serer Error: Msgno 953 Leel 11 State 1Page 39680, passed to curunreseredpgs built-in function, is an inalid page number in database ID 10. The highest page number in this database is This problem is caused by not remoing deices associated with databases that hae been dropped. Sybase reuses database IDs. After a database has been dropped and a new one has been created, the Sybase system tables still contain references to deices and their associated database IDs. The Sybase system tables also contain the information about the deice pages that exist for a database and the pages in use by the unremoed deices are outside that range, thereby causing the error. Workaround: Remoe unused deices using the sp_dropdeice deicename Sybase command, stop and restart the Sybase database serer, and delete the physical files associated with each dropped deice. For more information about the sp_dropdeice command, refer to the Sybase documentation. Problem: The wdbmaint.sh script with the stats option does not run when upgrading an Oracle eent database from ersion or to update database statistics. The database is still correctly upgraded. Workaround: To update the database statistics, manually run the wdbmaint.sh script with the stats option after the database upgrade has successfully completed. Problem: When using the installation wizard to configure the eent database on the UNIX operating system, the password fields cannot be oerwritten by highlighting the text field and then typing a new password. Workaround: When using the installation wizard to configure the eent database on the UNIX operating system, delete the entire password field using the backspace key or delete key before modifying the field. Problem: The wtdbclear.pl command loops when the number of eents retrieed is greater than the buffer size. The wtdbclear.pl command retriees all eents that match the SQL where clause instead of retrieing the output in buffer-sized pieces. If the number of eents retrieed is greater than the buffer size (default=1000), the wtdbclear.pl command goes into an endless loop. Workaround: Use the wtdbclear command or change the buffer size to aoid this problem. Adapter Configuration Facility upgrade: The following problem and workaround relates to upgrading the Adapter Configuration Facility. Problem: When you upgrade the Adapter Configuration Facility, adapter configuration profiles do not get upgraded and you cannot work with older ersions of the adapter configuration profiles. Some problems resulting from this situation are as follows: If you are upgrading from ersion of the Tioli Enterprise Console product, the existing profiles do not distribute successfully. This problem is caused by the fact that new binary files are distributed, but the old file setup is still being used. For example, on Solaris systems, the adapter fails to restart because it IBM Tioli Enterprise Console ersion 3.9 release notes 15

20 cannot find the FMT file; that is, the adapter is looking in the new location (etc/c/tecad_logfile.fmt), but the file is still in the old location (etc/tecad_logfile.fmt). To use the new function, you must explicitly add it to the adapter configuration profile. For example, if you are upgrading from ersion of the Tioli Enterprise Console product, the profile does not contain default entries for filters or prefilters; you must add them in the Adapter Configuration Facility. Also, the FQDomain and TransportList keywords are not specified by default in an older profile as they are in a new profile. Workaround: To upgrade the Adapter Configuration Facility, follow these steps: 1. Note your changes to the older adapter configuration profile so that you can add them to a new profile later. 2. Distribute a blank adapter configuration profile to remoe the old adapter. 3. Upgrade the Tioli Enterprise Console product as usual, including the Adapter Configuration Facility. 4. Create a new profile entry for each new adapter and add the changes that you noted earlier to the new profile. 5. Distribute the new adapter configuration profile to each applicable endpoint. Eent consoles The following problems and workarounds relate to eent consoles: Problem: When using the Task Assistant search facility in the Web ersion of the eent console, the search results might contain a topic that is listed as >. Selecting this topic produces the following message: No Help Aailable. Workaround: None. You can ignore this help topic. Problem: Running a non-tioli eent console on a machine with multiple network interface cards (NICs) can cause problems and preent the eent console from starting. The problems occur because of the bind order of NICs. Workaround: Change the bind order of the NICs. Problem: The following message receied when logging into the Web ersion of the eent console does not indicate the cause of the login failure. Authentication failed. A login failure can occur for any one of the following reasons: Incorrect user ID or password Insufficient Tioli authorization roles Operator is not assigned to the eent console Workaround: An administrator can determine the exact cause of the login failure through IBM WebSphere Application Serer logging. Problem: Creating an eent group filter with the causing eent receied attribute does not filter effect eents correctly. Workaround: To create an eent group filter to filter effect eents, create an eent group filter with an SQL constraint. To do this, follow these steps from the Configuration iew of the Jaa ersion of the eent console: 1. Right-click on the appropriate eent group and select Create Filter from the context menu. 2. In the Add Eent Group Filter window, enter a name and description for the new filter, and then click Add SQL. 16 IBM Tioli Enterprise Console: Release Notes

21 3. In the Add SQL window, do one of the following to create the filter: To filter in effect eents, enter the following SQL expression: cause_date_receptn <> 0 To filter eents other than effect eents, enter the following SQL expression: cause_date_receptn = 0 Problem: When using the Web ersion of the eent console in Netscape 6.2.x, selecting items in drop-down lists with the mouse does not work within the task wizard. Workaround: You can access the selections in a drop-down list using the keyboard in Netscape 6.2.x, or you can use Microsoft Internet Explorer to run the Web ersion of the eent console. Problem: A large number of eent group filters (typically 100 or greater depending on the size of the indiidual filters) defined within a single eent group in ersion of the Tioli Enterprise Console product might not migrate to ersion 3.9. This problem is due to a limitation in the size of the eent group filter in ersion 3.9 of the Tioli Enterprise Console product. Workaround: Rework the eent group filters prior to migrating to ersion 3.9. Problem: When displaying a help panel for the first time in the Web ersion of the eent console, the left arrow on the toolbar of the Task Assistant is actie, indicating that you can go back to the preiously isited help topic. Because a preious help topic does not yet exist, the following message is displayed: No Help Aailable. Workaround: None. Problem: After upgrading to ersion 3.9 of the Tioli Enterprise Console product on Tioli Management Framework, ersion 3.7.1, the time receied for eents displayed in a Tioli eent console might show as one hour late. This occurs because the time zone enironment ariable (TZ) in the Tioli Management Framework oser process is not synchronized with the TZ ariable in the operating system. The time receied on the eent console is displayed in Greenwich Mean Time (GMT), regardless of the selected time zone. This occurs only when daylight saings time is in effect and only on Tioli eent consoles running on Tioli Management Framework, ersion This does not occur on non-tioli eent consoles. Workaround: Check your time zone setting using the wtimezone command. If the time displayed is incorrect, manually set the TZ enironment ariable for the Tioli Management Framework oser process. For more information about the wtimezone command, refer to the Tioli Management Framework Reference Manual. Problem: If the ersion 3.9 upgrade is applied in a Tioli region that was preiously interconnected to another Tioli region that already has ersion or later of the Tioli Enterprise Console product installed, and the TaskLibrary resource type has been exchanged, then creating or assigning operators to eent consoles in the other Tioli region might fail with a message similar to the following example: com.tioli.framework.runtime.exinobjref, minor code = 28, completion status = No. Workaround: From the Tioli region where ersion or later of the Tioli Enterprise Console product was not upgraded, exchange resources with the Tioli region where the Tioli Enterprise Console product was upgraded, using the following command: wupdate r TaskLibrary region IBM Tioli Enterprise Console ersion 3.9 release notes 17

22 Where region is the Tioli region in which the Tioli Enterprise Console product was upgraded. Problem: Operators using Netscape as their default browser on Windows 2000 might see the following error message after clicking the Information button in the eent iewer in the Jaa ersion of the eent console: Unable to open "C:\/.tioli/tec_temp0.html". The following location is shown in the browser window: file:///c:/.tioli/tec_temp0.html A side effect occurs after the message box is displayed on top of the browser window. The focus can be changed from the browser to the actie window, but the error message must be closed before returning to the eent console or the eent console windows become blank. This is a limitation of Windows and certain ersions of Netscape. This problem has been seen occasionally in Netscape, ersion 4.74 and earlier. Workaround: Change the default browser to Internet Explorer or upgrade Netscape to a newer ersion. Problem: When a Jaa GUI process is launched in an X Window enironment, you might see error messages regarding font conersion, such as the following: ********************** Aertissement : Cannot conert string "-jdk-lucida-medium-r-normal--* p-*-iso " to type FontStruct ********************** Workaround: You can ignore this message because it does not indicate any problems in the system. Not eery X Window serer has eery font aailable. The message indicates that the mismatch of a font has occurred. When a font that is not installed in that particular X Window enironment is requested, the X Window system maps the missing font to one of the fonts that exists in the enironment. Problem: When starting the Jaa ersion of the eent console, the following Jaa exception might occur: GlobalPreferencesBean::loadPreferences( ) caught: jaa.io.inalidclassexception: jaax.swing.plaf.basic.basiclookandfeel; Local class not compatible: stream classdesc serialversionuid= local class serialversionuid= This exception occurs after a ersion 3.9 eent console is installed on a machine that preiously had a ersion or later eent console installed on it. It might also occur with a first-time, ersion 3.9 installation of the Tioli Enterprise Console product. Workaround: You can ignore this exception because it is harmless. This exception does not occur the second time the Jaa ersion of eent console is started. Problem: When using the Jaa ersion of the eent console with the NetView component, selecting more than 100 NetView eents (eent classes beginning with TEC_ITS_) to simultaneously acknowledge or close the eents while continuing normal operations might cause a deadlock situation. A timer is enabled for all eents other than NetView eents to regulate processing. 18 IBM Tioli Enterprise Console: Release Notes

23 Workaround: Select 100 or fewer eent to simultaneously acknowledge or close the eents while continuing normal operations. A counter is displayed in the upper right-hand corner of the eent iewer. The counter displays the total number of eents in the Working Queue and the number of eents currently selected. Problem: Renaming the NON_TME directory on AIX after installation might cause the following error when starting the Jaa ersion of the eent console: Unable to find xhpi, path used /home/non_tme_console/tec_console/jre/bin/libxhpi.a Could not create the Jaa irtual machine. Workaround: Run the slibclean command as the root user to clean the AIX caching library information. Then run the tec_console command. Problem: On Windows 2000, the login panel might not be displayed on top of existing windows. This problem occurs when you switch windows after running the tec_console command. Workaround: Minimize or moe any windows selected after running the tec_console command. On Windows 2000, do not use the Show Desktop button, which hides all actie windows including the login panel. Rules The following problems and workarounds relate to rules: Problem: Prolog action names that contain one or more spaces cause a compilation error when tracing is turned on. Workaround: Do not use spaces in prolog action names. Problem: The Tioli Enterprise Console ersion 3.9 product added e-business rule sets. To take adantage of these rule sets, eents must include fqhostname slot, which contains the fully qualified host name of the machine. Workaround: Ensure that the IBM Tioli Monitoring Fix Pack 5 is applied. If you are using the IBM Tioli Monitoring for Business Integration: WebSphere MQ, the IBM Tioli Monitoring for Databases: DB2, or the IBM Tioli Monitoring for Web Infrastructure: WebSphere Application Serer products, ensure that you hae installed the latest ersion of these products, which includes support for the fqhostname eent slot. Problem: The all_instances() predicate might return the same eent multiple times if you use the ersion of the predicate which does not include a time window and a current eent. Workaround: Do not use this ersion of the predicate: all_instances(eent:_eent of_class class where attribute_conditions) Always use this ersion of the predicate: all_instances(eent:_eent of_class class where attribute_conditions, _referenceeent -time_before -time_after) Problem: When compiling a prolog rule file that contains more than 70 rules or more than 4000 lines of code, using the wrb -comprules command with the -trace option does not produce an ERR file when the system finds a syntax error during the processing of that prolog rule file. Workaround: You can either disable the -trace option for the prolog rule file, or put the rules in multiple prolog rule files. Adapters The following problems and workarounds relate to adapters: Problem: Eents from a TME Windows eent log adapter might be lost during high eent traffic or when sending eents from a cache file. IBM Tioli Enterprise Console ersion 3.9 release notes 19

24 Workaround: Add the BufferFlushRate and MaxPacketSize keywords to the adapter configuration file so that the adapter bundles the eents that are sent to the gateway. The following example illustrates how you might set the BufferFlushRate and MaxPacketSize keywords. BufferFlushRate=1200 MaxPacketSize=4000 Problem: When you are using Tioli Enterprise Console 3.9 logfile adapters, watching log files that are in UTF-8 format and setting the NO_UTF8_CONVERSION=YES option might corrupt the eent information. Workaround: Ensure that the log files are created in local code page and set the NO_UTF8_CONVERSION=NO option. Problem: The UNIX logfile adapter and the Windows eent log adapter do not start if the path of any of the files specified in the LogSources keyword does not exist. Workaround: Proide alid path names for all LogSources files. Problem: When installing the HP OpenView adapter, you might see a soft error, and the adapter might not register correctly with HP OpenView. Workaround: To make the HP OpenView adapter functional, manually unregister and reregister the HP OpenView adapter with HP OpenView by running the following sequence of commands: odelobj /etc/opt/ov/share/tecad_hpo.lrf ostop ostart oaddobj /etc/opt/ov/share/tecad_hpo.lrf ostart tecad_hpo Problem: The $TIVOLIHOME/tec directory is used by the Tioli Enterprise Console gateway function and is created when the Adapter Configuration Facility is installed on the managed node machine. If this directory is remoed, Tioli Enterprise Console gateway does not function correctly. Workaround: Ensure that $TIVOLIHOME/tec directory exists before distributing the Tioli Enterprise Console gateway profile. If $TIVOLIHOME/tec directory does not exist, create it manually. By default, $TIVOLIHOME is set to the following depending on the operating system: For UNIX: /etc/tioli For Windows: %WINDIR%\system32\driers\etc\Tioli Problem: Two logfile adapters with the same ID are started. Workaround: If you try to configure two adapters with the same ID, the adapter is started twice. Therefore, if you are using IDs with logfile adapters, ensure that each ID is unique. Problem: Unpredictable results can occur when a syslog or log file that is being monitored includes a message that exceeds 3900 bytes. Workaround: Limit the total size of the eent data to 3900 bytes. Problem: The OS/2 adapter does not automatically start after distributing it using the Adapter Configuration Facility. Workaround: Restart the OS/2 machine to start the adapter. Problem: The format file for the UNIX logfile adapter does not match Solaris Operating Enironment, Version 8, syslogd eents file. The format for the Solaris log file changed from Solaris Operating Enironment, Version 7, to Version 8. Some adapter format files no longer match entries in the system log. Workaround: Either update the format file as described or set the log message format to Solaris 7 compatibility mode. To set the log file compatibility mode, add the following entry to the /kernel/de/log.conf file: 20 IBM Tioli Enterprise Console: Release Notes

25 msgid=0 Restart the syslogd daemon for the changes to take effect. Problem: Modifying configuration file options stored in adapter configuration profiles on endpoints with the wsetaeen command fails. A message similar to the following example is displayed: FRWTE:0021 Wed Aug 14 17:14: (21): operation `_set_acpenironment not implemented Workaround: Add or modify configuration file options using the Adapter Configuration Facility, and then distribute the profiles to endpoints. Problem: Eent strings generated by Windows XP are different from those generated by Windows This causes the Windows eent log adapter on Windows XP endpoints to only generate eents of class NT_Base for all of the Windows XP eents that satisfy the filtering criteria of the adapter. For example, an NT_Performance_Alert class eent from a Windows 2000 endpoint is an NT_Base class eent on a Windows XP endpoint. Workaround: To enable the Windows eent log adapter to match Windows XP eents with Tioli Enterprise Console eent classes, modify the tecad_win.fmt file (also known as a format file) to match the specific eents you want to send to the eent serer. For more information on how to generate a new class definition statement (CDS) file after you modify a format file, refer to the IBM Tioli Enterprise Console Adapters Guide. Documentation notes Scripts The following problem and workaround relates to a script: Problem: When using the wtdbclear.pl script to clear the eent database, the script fails to complete if the system tmp subdirectory does not hae sufficient space, and you might see errors. Because the wtdbclear.pl script uses the system tmp subdirectory to store table and data information, this problem can occur when clearing an eent database that has a large amount of data. Workaround: If you are deleting a large amount of data from the eent database, increase the size of the system tmp subdirectory, or delete the data incrementally in smaller amounts. This section describes changes made to the organization of the documentation in ersion 3.9 of the Tioli Enterprise Console product, and it describes information that was identified after the documentation was finished. Documentation changes The section describes organizational changes to the documentation for ersion 3.9, and it describes important terminology information. The following table describes the books that hae been renamed in ersion 3.9 of the Tioli Enterprise Console product: Preious book name New book name IBM Tioli Enterprise Console Reference Manual IBM Tioli Enterprise Console Command and Task Reference IBM Tioli Enterprise Console Rule Builder s Guide IBM Tioli Enterprise Console Rule Deeloper s Guide IBM Tioli Enterprise Console ersion 3.9 release notes 21

26 Preious book name Tioli Eent Integration Facility User s Guide New book name Tioli Eent Integration Facility Reference The IBM Tioli Enterprise Console Rule Set Reference is a new book in this release. It proides reference information about the Tioli Enterprise Console rule sets. Rule deelopers should read this book to understand the functionality that the Tioli Enterprise Console rule sets automatically proide. The IBM Tioli Enterprise Console Installation Guide has been completely updated and reised. It now includes chapters on using the installation wizard and on troubleshooting as well as an appendix describing a sample, step-by-step installation of all Tioli Enterprise Console components in a simple working deployment. The IBM Tioli Enterprise Console User s Guide has been completely updated and reised. It now includes a chapter specifically for operators. The online HTML reference for the Tioli Enterprise Console product is no longer aailable on the eent serer host at $BINDIR/../generic_unix/TME/TEC/BOOKS/HTML/reference.html. The IBM Tioli Enterprise Console Command and Task Reference, which is aailable in both PDF and HTML formats, contains this information. The following table describes information that has moed to a new location: Information Preious location New location Writing rules to correlate eents at the adapter or the Tioli Enterprise Console gateway (state correlation) Installing, upgrading, and uninstalling adapters Tioli Enterprise Console gateway Eent flow Adapter Configuration Facility Logfile format editor postzmsg, TECAgent, and wpostzmsg commands Tioli Eent Integration Facility Reference IBM Tioli Enterprise Console Installation Guide IBM Tioli Enterprise Console Adapters Guide IBM Tioli Enterprise Console Command and Task Reference IBM Tioli Enterprise Console User s Guide IBM Tioli Enterprise Console User s Guide Tioli Eent Integration Facility Reference Part 2 of the IBM Tioli Enterprise Console Rule Deeloper s Guide IBM Tioli Enterprise Console Adapters Guide IBM Tioli Enterprise Console User s Guide IBM Tioli Enterprise Console User s Guide IBM Tioli Enterprise Console Adapters Guide IBM Tioli Enterprise Console Adapters Guide IBM Tioli Enterprise Console Command and Task Reference In the documentation, the terms TME and non-tme are used primarily in reference to adapters. A TME adapter is an adapter than runs on either a managed node or an endpoint. A non-tme adapter is an adapter that does not use the Tioli Management Framework (managed node or endpoint) to send eents to the eent serer. In the adapter configuration file, you set the type of transport mechanism that an adapter uses to send eents to the eent serer. A TME adapter uses either the endpoint transport (transport type set to LCF) or the managed node transport (transport type set to TME) to send eents. A non-tme adapter uses the socket transport (transport type set to SOCKET) to send eents. The term Tioli (as opposed to non-tioli) is used primarily in reference to the Tioli enironment, which was formerly known as the Tioli Management Enironment (TME). Tioli enironment is defined as the Tioli 22 IBM Tioli Enterprise Console: Release Notes

27 applications, based upon the Tioli Management Framework, that are installed at a specific customer location. In some cases, you might find that these terms are used synonymously: Tioli and TME Non-Tioli and non-tme Documentation updates The following information about the Start_Maintenance task is aailable in the online help of the Jaa ersion of the eent console in English only. This information is proided here to support national languages. The Start_Maintenance task informs the eent serer that a host has been put in maintenance mode. Select the eent serer to inform, type the name of the host to put in maintenance mode, and specify the duration for the maintenance mode. To configure the task: 1. Select Start_Maintenance from the TEC Tasks list in the Task Execution dialog box. The configuration options for the task are displayed in the right pane. 2. In the right pane, type or select alues for the following fields: Eent Serer s Name The eent serer to inform. This is a required field. hostname The fully qualified name of the host to put in maintenance mode. This is a required field. The default for this field is an asterisk. If you do not change this default, all hosts are put in maintenance mode. Maintenance Owner Information Optional information, such as an address or phone number, that you can enter regarding the person who is oerseeing the maintenance for the host. Maintenance Duration The number of minutes during which the host is in maintenance mode. This is a required field. The default is 60 minutes. Time to Start Maintenance The time at which the host is put in maintenance mode. If you leae this field blank, the host is put in maintenance mode immediately. Specify the time in this format: yyyy mm dd hh mm ss For example, indicates that the host is put in maintenance mode on 12 June 2003 at 23:30:00, or 11:30 p.m. Assumptions and Prerequisites: This task assumes that the wpostemsg command is aailable on the host where the task executes. The wpostemsg command is always aailable on the eent serer host and endpoints that hae an eent adapter installed. Authorization Required: super, senior, admin, user IBM Tioli Enterprise Console ersion 3.9 release notes 23

28 Command-Line (CLI): Internationalization notes You can run this task from the command line. You can also put a host in maintenance mode by running the wstartmaint.sh shell script, which resides on the eent serer. Do not use the wpostemsg command to send a TEC_Maintenance eent. For information about tasks, enironment ariables aailable to tasks, and how to configure and run tasks from the command line, refer to the IBM Tioli Enterprise Console Command and Task Reference. The information in this section supersedes the information in the Tioli Enterprise Console library. This section outlines Tioli Enterprise Console support for international languages. Enabling language support The Tioli Enterprise Console product is translated into the following languages: German Spanish French Italian Japanese Korean Portuguese (Brazilian) Chinese (Simplified) Chinese (Traditional) To enable these languages and use the fully-translated eent console task windows, install the appropriate language support pack from the IBM Tioli Enterprise Console Language Support CD. You must install the appropriate IBM Tioli Enterprise Console, Version 3.9 language support pack. You can install multiple language support packs for a single product. For installation instructions, refer to the IBM Tioli Enterprise Console Installation Guide. Eent adapter and eent serer compatibility Different ersions of eent adapters can send their eent data to eent serers with different character encoding. Additionally, different ersions of eent serers expect eent data in different character encoding. If you are combining ersions of eent adapters and eent serers in a non-english enironment, especially a multi-byte character set (MBCS) enironment, it is important that you understand the compatibility among the arious ersions of eent adapters and eent serers. Note: You should keep all components of the Tioli Enterprise Console product at the most recent ersion. The term UTF-8 patch is used to refer to the patches shown in the following table: 24 IBM Tioli Enterprise Console: Release Notes

29 Table 4. UTF-8 patches Version of eent serer or adapter Patch number TEC-0010 and 3.6-TEC TEC-0005, TEC-0008, and TEC-0010 indiidually applied, or TEC-0013 applied (contains 0005, 0008, 0010) TEC-0001 and TEC-0004 Custom applications built with Tioli Eent Integration Facility For adapters and other applications built with Tioli Eent Integration Facility, the NO_UTF8_CONVERSION keyword specifies the encoding for the eents, configuration file, and any other data input. The Pre37Serer and Pre37SererEncoding keywords specify the encoding of the output from Tioli Eent Integration Facility. For example, when the NO_UTF8_CONVERSION keyword is set to YES and the Pre37Serer keyword is set to YES, Tioli Eent Integration Facility expects eent data and its configuration file to use UTF-8 encoding, but it transmits the eent to the eent serer using DBCS encoding. Eent adapters Some changes to the eent processing for international enironments that might require changes to some adapters, their configuration files, or filters. The following table describes the compatibility between different ersions of adapters and eent serers. Table 5. Settings for internationalization support for non-tme adapters Eent serer ersion Eent data stream encoding Comments Adapter ersion 3.8 or or 3.9 UTF-8 data is sent. Pre37Serer must be set to NO, which is the default alue. NO_UTF8_CONVERSION=NO 3.7 UTF-8 data is sent. 3.6, 3.6.1, and with the UTF-8 patches 3.6, 3.6.1, and without the UTF-8 patches Pre37Serer must be set to NO, which is the default alue. UTF-8 data is sent. Pre37Serer must be set to YES and Pre37SererEncoding must be set to UTF-8. Local encoded data is sent. 3 Pre37Serer must be set to YES and Pre37SererEncoding must be set to the Tioli encoding at the eent serer. See thetioli Management Framework User s Guide for additional information about Tioli text encoding support. Data can be passed to tasks and programs in UTF-8 or local encoding. See the IBM Tioli Enterprise Console Rule Deeloper s Guide for additional information. Data can be passed to tasks and programs in UTF-8 or local encoding. See the IBM Tioli Enterprise Console Rule Deeloper s Guide for additional information. Data is passed to tasks and programs in UTF-8 encoding. Data is passed to tasks and programs in local encoding. IBM Tioli Enterprise Console ersion 3.9 release notes 25

30 Table 5. Settings for internationalization support for non-tme adapters (continued) Eent serer ersion Eent data stream encoding Comments Adapter ersion 3.7 and and later UTF-8 data is sent. 3.6, 3.6.1, and with UTF-8 patches 3.6, 3.6.1, and without UTF-8 patches 3.6, 3.6.1, and with UTF-8 patches 3.6, 3.6.1, and without UTF-8 patches Pre37Serer must be set to NO, which is the default alue. UTF-8 data is sent. Pre37Serer must be set to YES and Pre37SererEncoding must be set to UTF-8. Local encoded data is sent. Pre37Serer must be set to YES and Pre37SererEncoding must be set to the Tioli encoding at the eent serer. See the Tioli Management Framework User s Guide for additional information about Tioli text encoding support. 3.7 and later Not supported. None. 3.6, 3.6.1, and with UTF-8 patches 3.6, 3.6.1, and without UTF-8 patches UTF-8 data is sent. Not supported. Data can be passed to tasks and programs in UTF-8 or local encoding. Data is passed to tasks and programs in UTF-8 encoding. Data is passed to tasks and programs in local encoding. Data is passed to tasks and programs in UTF-8 encoding. None. 3.7 and later Local encoded data is sent. 3 Data can be passed to tasks and programs in UTF-8 or local encoding. 3.6, 3.6.1, and with UTF-8 patches Not supported. None. 3.6, 3.6.1, and without UTF-8 patches Local encoded data is sent. 3 Data is passed to tasks and programs in local encoding. Notes: 1. An internal inconsistency in the 3.7 and adapters required users to unconditionally set NO_UTF8_CONVERSION to YES. This workaround allowed eents to correctly reach the eent serer but caused encoding mismatches between eent data and eent filters set in the adapter configuration files. As a result, filtering eents (using the Filter keyword in the configuration files) based on attributes containing DBCS or UTF-8 characters would not work. The problem is fixed for the 3.9 eent adapters. Set NO_UTF8_CONVERSION to YES only if the adapter input (eents), format file (for logfile adapters), and configuration file are already encoded in UTF-8 format. If the adapter input, format file (for logfile adapters), and configuration file are encoded in DBCS, set NO_UTF8_CONVERSION to NO. 2. Non-TME logfile-type adapters shipped with Tioli Enterprise Console, ersion 3.7.1, must hae the NO_UTF8_CONVERSION configuration file option set to YES because the eent data has already been conerted to UTF-8 before being passed to Tioli Eent Integration Facility for forwarding to the eent serer. If this option is not set to YES, the non-english eent data will be unusable because it will hae been conerted to UTF-8 encoding twice, once by the adapter and again by Tioli Eent Integration Facility. 3. Local encoding of adapters and eent serer must be the same. For example, SJIS encoded data sent from an adapter is not supported by an eent serer set to EUJCP encoding. 26 IBM Tioli Enterprise Console: Release Notes

31 Non-English data in adapter format files For logfile-type adapters, you can use non-english characters in a format string in a format file. The non-english characters must be entered in local or UTF-8 encoding. This is different than preious ersions. The following table summarizes the encoding of characters in format files for arious ersions. Note: The contents of a format file should not contain different strings encoded in both local and UTF-8 encoding. Using mixed encoding in the same file might cause many problems, including mismatches on eent filtering, unreadable eent contents on eent serer, and others. Table 6. Non-English data in adapter format files Version with UTF-8 patches Version 3.7 Version Version 3.8 or 3.9 UTF-8 encoding Local encoding with patches (see the Tioli Support Web site for patch information) Local encoding Local encoding 1 or UTF-8 1 Eent data, the configuration file, and the format file must all use the same encoding. If the encoding is DBCS, the NO_UTF8_CONVERSION keyword must be set to NO (the default setting). If the encoding is UTF-8, the NO_UTF8_CONVERSION keyword must be set to YES, because all the data is already in UTF-8 format. Non-English data in filters in adapter configuration files For logfile-type adapters, you can use non-english characters in an attribute filter specification defined by the Filter keyword in an adapter configuration file. The non-english characters must be entered in local encoding. This is different than preious ersions. The following table summarizes the encoding of characters in configuration files for arious ersions: Table 7. Non-English data in adapter configuration files Version with UTF-8 patches Version 3.7 Version Version 3.8 or 3.9 Not supported Local encoding with patches (see the Tioli Support Web site for patch information) Local encoding Local encoding 1 or UTF-8 1 Eent data, the configuration file, and the format file must all use the same encoding. If the encoding is DBCS, the NO_UTF8_CONVERSION keyword must be set to NO (the default setting). If the encoding is UTF-8, the NO_UTF8_CONVERSION keyword must be set to YES, because all data is already in the UTF-8 format. Troubleshooting tips The TISDIR enironment ariable is set by Tioli software products and points to the code set directory. The code set directory contains the conersion tables to conert local encoded data to UTF-8 encoded data. If eent data is unusable, check the TISDIR ariable and ensure that it is pointing to the correct code set directory. Also ensure that the code set directory has the appropriate conersion table for the locale. For example, the file named 932 must be in the code set directory for a Windows enironment in Japan. Check locale enironment ariables for correct settings. Installing a language pack on a non-tioli eent console A separate language pack is proided for installing on a non-tioli eent console. This language pack can be installed using the procedure proided on the IBM Tioli Enterprise Console 3.9 Language Support CD. The procedure is in the README file in the Setup directory. IBM Tioli Enterprise Console ersion 3.9 release notes 27

32 Software limitations, problems, and workarounds for internationalization issues This section describes known problems in this release that are related to internationalization issues. When using Netscape 6.2.x, the attributes table of Sample Eent Information is not completely translated into the national language. In the attributes table shown, the top part of the HTML page is translated into the national language, but the bottom part of the HTML page is not translated into the national language. This problem is because of limitations of Netscape 6.2.x when dealing with DBCS characters (Japanese, Korean and Chinese). Microsoft Internet Explorer displays the characters correctly. When the Tioli Enterprise Console installation wizard is running on the AIX operating system under the Chinese (Traditional) code page, characters in bold fonts might be difficult to read. This is a limitation of the Jaa Runtime Enironment. The logfile adapters produce unexpected results when using the German code page IBM-850 on AIX. Do not use code page IBM-850. When using national language support (NLS) keyboard mapping, the user ID and password for the eent console is limited to alphanumeric characters. Do not use non-alphanumeric characters for the user ID or password. When using the installation wizard to configure the eent database, the text in some help windows does not wrap properly at line end when DBCS and SBCS characters are mixed on the window. For example, when there is an English keyword, the immediately trailing DBCS text starts on the next line. When using the installation wizard to configure the MS SQL Serer eent database, the first row of the Unit drop-down list is intentionally blank. When using the installation wizard to configure the DB2 eent database, the default for the Select the Database Locale field is USA, regardless of the locale set for the local machine. When using the installation wizard to configure the MS SQL Serer or Oracle eent database, on the file group specification panel, the alue Unlimited in the Maximum Size field is intentionally in English. For the Jaa ersion of the eent console, if you hae configured the tec_help.pl file to display extended ASCII (hex 128 to 255) or DBCS characters on Eent Information Web pages, you must conert these files into UTF8 format. You must do this for the tec_help.pl file and any supporting HTML files that contain these extended characters. If you do not conert the tec_help.pl file and the HTML files into UTF8 format, displaying eent information fails with the following error: ECO2032E: Failed to receie eent information from Use the Tioli Management Framework wicon utility to conert your files to the UTF8 format. For example, use a command similar to the following example: wicon -f ISO t UTF8 < tec_helporig.pl > tec_helputf8.pl In addition, you must print out this entry as part of your HTML header: <META HTTP-EQUIV="Content Type" CONTENT="text/html; charset=utf 8"> Doing this ensure that Web browsers use UTF8 encoding to display the Eent Information page. 28 IBM Tioli Enterprise Console: Release Notes

33 Appendix A. Upgrading from ersion This section contains information about changes to the Tioli Enterprise Console product as of ersion 3.8 that you should be aware of if you are upgrading from ersion to ersion 3.9 of the Tioli Enterprise Console product. Eent adapters no longer shipped The following eent adapters are no longer shipped: The SPECTRUM adapter for the Cabletron SPECTRUM Enterprise Manager The Sun Solstice/SunNet Manager adapter Tioli Enterprise Data Warehouse enablement The Tioli Enterprise Console product is enabled for the Tioli Enterprise Data Warehouse with a warehouse enablement pack. You can expect enhancements to the Tioli Enterprise Console warehouse enablement pack oer time. Check with IBM Software Support or the IBM Passport Adantage program for subsequent enhancements to this component. Eent database configuration using the installation wizard Graphical rule builder Rule enhancements The following items pertain to configuring the eent database using the installation wizard: Do not generate scripts to the $BINDIR/TME/TEC/sql directory. If you mistakenly attempt to generate them to that directory, a message similar to the following is issued: The directory that you specified for the generated scripts directory is the same as $BINDIR/TME/TEC/sql. Specify another directory. Specify a different directory and generate the script again. The graphical rule builder included with the Tioli Enterprise Console product proides an easy way to create ery simple rules. If you need to use the full power of the rule language, manual coding of rules with a text editor is the recommended approach for deeloping rules in ersion 3.9. Similarly, use the wrb command when performing rule base-related tasks. Deeloping rules and managing rule bases is ery different in ersions later than If you hae deeloped rules and managed rule bases in preious ersions of the Tioli Enterprise Console product, familiarize yourself with the information contained in the IBM Tioli Enterprise Console Rule Deeloper s Guide. Copyright IBM Corp

34 Prefixes used in prolog file names The Tioli Enterprise Console product preiously required the use of the tec_r prefix in Prolog files that were used with the TECpcomp command or predicates that operated with Prolog files, such as the compile or consult predicates. For ersion 3.9, files no longer need the prefix. If existing files contain the prefix, the prefix is automatically remoed when you compile the file. For additional information about prefixes for Prolog files, refer to the IBM Tioli Enterprise Console Rule Deeloper s Guide. Upgrading rule bases to ersion 3.9 For rule bases created for ersions 3.6.x, the WIC and the root.baroc files are automatically upgraded when you upgrade to ersion 3.9. To use the upgraded rule bases, you must recompile and reload them. Rule bases that were created in a 3.7.x or later ersion of the Tioli Enterprise Console product do not need to be upgraded. Deprecated BAROC features The following items are deprecated in ersion 3.9 and will not be supported in future releases. When the Tioli Enterprise Console ersion 3.9 product rule compiler encounters any of the deprecated items, a warning message is issued. These are the deprecated items: Multiple Class Inheritance Eent classes can no longer inherit from more than one superclass. Single class inheritance is not deprecated. Using an eent class name as an attribute type Base data types no longer include eent class names. Valid base data types are now enumerated types: INT32, INTEGER, REAL, and STRING. Changes to the first_instance and all_instances predicates The first_instance and the all_instances rule language predicates now alidate that each attribute referenced in an attribute filter has been defined in one of the classes listed in the class filter. That is, to filter on an attribute, the attribute must be defined in the class that causes the rule to run instead of in a parent class. For example, if the attribute disk is not defined in the eent class Logfile_Baroc, the following use of the first_instance predicate is not alid: first_instance(eent: _dup_eent of_class Logfile_Base where [ disk: equals c: ]) Attribute filters in rules are checked to ensure that the type complexity (SINGLE or LIST_OF) of the attribute in the filter is the same as the filter alue. For example, the following rule results in a compilation error if the attribute msg is defined as a SINGLE complexity, while the alue is a LIST_OF complexity. rule: single_eq_list: ( eent: _eent of_class _class where [ msg: equals [ one, two, three ] ] 30 IBM Tioli Enterprise Console: Release Notes

35 ). action: ( drop_receied_eent ) Differences in predicate behaior from past releases In ersion 3.6.x of the Tioli Enterprise Console product, the all_instances and the first_instance rule language predicates return different results from the eent cache when a free class ariable is used in the eent filter. The returned result depends on whether or not a time window was specified. If no time window is gien, then only eents of leaf-node classes are returned. If a time window is specified, then all eents in the cache are returned, including superclass eents. In ersion 3.7 and later, this behaior changed so that the result does not include superclass eents, regardless of whether or not a time window is specified. Howeer, this is inconsistent with the way eent filters handle free class ariables. This has been corrected in ersion and later of the Tioli Enterprise Console product. Regardless of whether a time window is specified, when the all_instances or the first_instance rule language predicates are called with a free class ariable in the eent filter, all eents in the eent cache are returned. The following sample code returns all eents in the eent cache. all_instances(eent: _dup_eent of_class _dup_class where [ status: outside [ CLOSED ] ], _eent The behaior has also changed in these two predicates in the case where the eent cache is searched for a superclass. In the following rule, ersion of the Tioli Enterprise Console product returns child class eents of NT_Base and eents of class NT_Base (a superclass). all_instances(eent: _dup_eent of_class NT_Base where [ status: outside [ CLOSED ] ], _eent Howeer, if the time window _eent is not specified, then only eents of leaf-node classes are returned. This has been changed to return only eents of leaf-node classes specified in the eent filter, regardless of whether a time window has been specified. Appendix A. Upgrading from ersion

36 32 IBM Tioli Enterprise Console: Release Notes

37 Appendix B. Defects corrected in ersion 3.9 The following defects hae been corrected for this release of the Tioli Enterprise Console product. The defect or APAR number precedes the description of the defect : The adapter uninstall scripts can remoe the incorrect entry in the /etc/rc.xxx file : Running the tecad_logfile.cfg file from any directory other than the $TECADHOME/bin directory fails with a syntax error similar to the following example: /data/tec371/nontme/bin/tecad_logfile.cfg[1678]:./wlocpatch: not found Usage: gencds format_file : The tec_console enironment ariables do not match the rule base enironment ariables : The tec_reception process hangs during an eent storm : The Windows TME adapter does not send complete eent message information : Upgrading a rule base using the wrbupgrade command from a bash shell fails : The TME adapter does not update the rc.xxx scripts when it is redistributed : Unable to distribute an adapter to an endpoint running Red Hat Linux 8.0. IY13071: The AS/400 adapter can miss messages when another application remoes messages from the queue. IY20113: When an alternate eent serer is specified in an adapter configuration file with the SererLocation keyword and the primary serer is down, the first eent sent using the wpostemsg command is put into the cache instead of being sent to the alternate eent serer. IY20446: The Change Seerity task does not produce any output, and it causes the application to hang. IY21007: The wmigcon command does not migrate ersion eent consoles to ersion eent consoles correctly when the Administrator and console names are different. IY22158: The adapter lock file created for a process number is not deleted when the tecadini.sh stop is called. IY21196: AIX adapters do not automatically start with startup commands in the rc.nfs file. IY22689: The AS/400 adapter stops running when you create a message and then try to send the message to the queue. IY32758: The create_clearing_eent predicate does not restrict the eent correctly. IY23584: The eent class and source buttons are missing from the EVENT_QUERY task in the eent console. IY28856: The wsetemsg process requires seeral minutes to complete with a large number of eents in the eent database. IY29094: The wrb crtrb command fails as root Tioli administrator if the user is not the system root user. Copyright IBM Corp

38 IY30177: The graphical rule builder fails to run on HP-UX 11 with the following message: FRWSL0024E A failure was detected by the oser daemon... IY30915: After distributing an adapter with the S flag set and restarting the system, the adapter does not start with the S option. IY31847: The log file adapter sends all eents when the last updated time changes. IY31930: When forwards eents from one eent serer to another, the date_reception field within the serer_path object does not contain a alid date. IY33041: The stored procedures do not run correctly on a DB2 database when running the wtdbclear command. IY33187: Logfile adapters generate errors when the length of the eent is greater than 4096 errors. IY33312: Stopping the eent serer (from the desktop or with the wstopesr command) hangs when single port BDT has been enabled. IY33602: The wtdbclear.pl script enters an infinite loop when the number of eents to delete is greater than or equal to the buffer size or when the following attributes are specified without s, c, r: e t 0 Or: l f t 0 IY34129: Eents are not sent to the eent serer with the tec_gateway process running in connection-oriented mode when the TMF 0073 and the TMF 0075 Tioli Management Framework patches are installed. IY34289: The tec_rule process stops with a SIGSEGV iolation when the eent serer, configured to forward eents, is initializing. IY34293: The TEC_CONSOLE -E eent_group_name command works only when the name of the eent group does not contain spaces. IY34386: The eent console fails to start the NetView management console on W32-IX86 platforms. IY34564: The init.tecad_logfile script failes to start multi-region adapters. IY34596: The tecad_nt.exe process generates a Dr. Watson error if the FMT file contains a statement that does not begin with the following characters: %s*. IY34913: The init.tecad_logfile script does not process the S option on Digital Equipment Corporation Tier 2 systems. IY34968: Adapters reading from a file specified with the LogSources option cannot forward eents with more than 300 characters in each line. IY35033: The list of aailable hosts in the Task Execution window incorrectly displays host names instead of endpoint names. IY35099: The eent console task completion icon disappears or is not always displayed in the eent iewer. IY35278: The logfile adapter does not start if the FMT file contains the s* characters in a match statement. IY35286: After installing TEC-0031E, you cannot create a CDS file from a FMT file with a printf statement containing %s. IY35647: After applying the TEC FP02 fix pack, performance is impacted on the Windows adapter. IY35763: The eent console distributed with the TEC FP03 fix pack does not start due to a Jaa class error. 34 IBM Tioli Enterprise Console: Release Notes

39 IY36144: The format specifier, %LENGTHs, does not parse correctly after upgrading from ersion 3.6.x. IY36319: The TEC_ADMIN enironment ariable does not display the name of the administrator when running the TroubleTicket.sh script. IY36572: The tec_gateway process has a memory leak. IY36663: The wconsole command creates a warning when the specified password is incorrect. IY36686: The SererLocation parameter in the tec_gateway.conf file is ignored when the local eent serer stops and the parameter contains a blank character after the specified eent serer. IY37000: The Eent Integration Facility discards eents when null attribute alues are included in the Sample.Adapter.jaa file. IY37027: The Eent Integration Facility does not correctly parse strings enclosed in double quotes in the SampleAdapter.jaa file. IY37051: For interconnected Tioli regions, adapters do not send eents to the eent serer when only one eent serer is installed in one of the interconnected Tioli regions. IY37190: The Windows adapter uses 100% CPU when processing large log files. IY37400: Eents are cached at the Tioli Enterprise Console gateway when sending eents from an endpoint to the eent serer using the endpoint wpostemsg command. IY37549: The init.tecad_snmp script does not support HP-UX 11. IY37675: The tec_dispatch process terminates with a signal 211 error when receiing eents from the IBM Tioli Risk Manager product if the locale is not set to C. IY37768: The tec_gateway process stops sending eents to the eent serer after processing the contents of a full tec_gateway.cache file. IY37863: The HP-UX adapter uses 100% CPU and does not process eents after upgrading from ersion to TEC FP03. IY38116: When reception logging is disabled, the eent serer fails to process eents. IY38205: The eent console operator definitions are periodically lost. IY38379: When running the cr_tec_db.sh script against Oracle 9i V2, an ORA error is generated. IY38723: The DISPLAY enironment ariable is not properly set for the TroubleTicket.sh script. IY38796: Running the postemsg command on Windows 2000 to another machine, which is on a slow connection, fails. IY38929: When parameters that are not alid are supplied to either the wlsemsg or the wsetemsg commands, the program prints an error message about the error but does not close the RIM_database_endor_agent process, and the process runs indefinitely. IY39825: The listing in the Current Hosts pane of the Task Execution window lists host names instead of endpoint names. IY39401: The logfile adapter does not function correctly when matching the format %LENGTHS with the WIDTHSTRMEANING=YES option set. IY39819: The tec_ui_serer process memory usage increases oer time een if the total number of actie eent consoles does not go beyond a certain number. IY39936: Attribute list always prints when iewing eent information from the eent console. Appendix B. Defects corrected in ersion

40 IY40173: Memory for the tec_gateway process grows without bounds. IY40180: Add tracing to the tec_gateway process to capture out of port errors. IY40453: Eents with an equal sign (=) in an attribute alue are not put in the rules cache when the eent serer restarts. IY40557: Extended eent attributes are not aailable to the TroubleTicket.sh script een though they are listed in the SLOTS enironment ariable. IY40576: The Target Hosts pane on the Task Execution window does not list all endpoints in the Tioli region. IY40864: Changes to eent console properties are not reflected in the eent iewer. IY40903: The wmigcon process generates a Jaa exception when upgrading from ersion to ersion 3.8. IY41202: The Aailable Operators panel does not list unassigned operators. IY41207: The eent serer fails to obtain a port to receie eents from non-tme adapters. IY42199: The tec_ui_serer install with update methods fails on managed nodes. IY42462: The Linux logfile adapter slows down the syslog startup when the system is restarted. IY42602: The win_gencds process generates a Dr. Watson error when the format string is too long. IY42774: The TME logfile adapter has a memory leak. IY42831: After some time (or after receiing seeral thousand eents), eents fail at the eent serer with a PARSING_FAILED error. IY42976: The tec_rule process shows a memory leak when forwarding eents. IY42977: The eent serer hangs when receiing eents. IY43147: The Ctrl-E key combination in an eent stream causes the eent serer to stop. IY43294: The HP OpenView adapter ignores the PREFIX operator in the tecad_hpo.cds entry. IY43312: The tec_gateway process requires more RPC threads. IY43346: Using $VARBIND in the tecad_hpo.cds or the tecad_snmp.cds files causes the adapter to stop. IY44093: Eents comprised of a blank line are always mapped to a class in the FMT file without any ariables defined. IY44231: Internal eents, such as generate_eent(), do not force clean the eent cache file when the cache file is full. Also, the internal eent is dropped when the cache is full. IY44860: String slots in eents forwarded to the Tioli Business Systems Manager, which initially get sent as unquoted strings, eentually start getting sent as single-quoted strings after seeral days of operation (> 100,000 eents triggering exec_program() predicate). Tioli Business Systems Manager currently does not handle single-quoted strings. This change in behaior causes Tioli Business Systems Manager to fail eents which were preiously handled. IY45389:After installing TEC-0045E, the debug mode for the logfile adapter does not match eents the same way the adapter matches them when running in the standard operating mode (without the -d flag). 36 IBM Tioli Enterprise Console: Release Notes

41 Appendix C. Jaadoc HTML documentation for the EentList class com.tioli.zce.engine Class EentList This appendix contains the Jaadoc HTML documentation for the EentList class. jaa.lang.object +--com.tioli.zce.engine.eentlist public final class EentList extends jaa.lang.object The EentList class stores an array of Eents and keeps track of the last index used in this array. This implementation uses the ArrayList class which efficiently increases the capacity of the list on demand. For cases where large numbers of elements are remoed from EentList, we proide a mechanism to call ArrayList.trimToSize method Author: fer (Metin Feridun) Constructor Summary (EentList)((Eent) eent) Create EentList with one gien eent in it (EentList)(int size) Create EentList of specific size Method Summary (Eent) (eentat)(int position) Get Eent at gien position in list int (length)() Get maximum size of list. oid (remoelast)() Remoe last element in the list oid (seteentat)((eent) eent, int position) Set Eent at gien position in list int (size)() Get current size of list (index of last element set) jaa.lang.string (tostring)() Return contents of the EentList as a String. Copyright IBM Corp

42 Methods inherited from class jaa.lang.object, clone, equals, finalize, getclass, hashcode, notify, notifyall, wait, wait, wait Constructor Detail EentList public EentList(int size) Create EentList of specific size Parameters: size - Size of list to be created EentList public EentList((Eent) eent) Create EentList with one gien eent in it Parameters: eent - Single eent contained in this list Method Detail seteentat public oid seteentat((eent) eent, int position) Set Eent at gien position in list Parameters: eent - Eent to be stored in list position - Position this Eent will be stored in list eentat public (Eent) eentat(int position) Get Eent at gien position in list Parameters: position - Position in list we want to get Eent from Returns: Eent at gien position 38 IBM Tioli Enterprise Console: Release Notes

43 size public int size() Get current size of list (index of last element set) Returns: Size of list remoelast public oid remoelast() Remoe last element in the list length public int length() Get maximum size of list. For ArrayList implementation, the alue returned by this method is is the same as the number of elements in the list. Returns: Maximum size of list tostring public jaa.lang.string tostring() Return contents of the EentList as a String. Oerrides: tostring in class jaa.lang.object Returns: String representation of the contents of the EentList Appendix C. Jaadoc HTML documentation for the EentList class 39

44 40 IBM Tioli Enterprise Console: Release Notes

45 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user s responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions 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 new editions of the publication. IBM may make improements 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 proided for conenience only and do not in any manner sere 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. Copyright IBM Corp

46 IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/ Burnet Road Austin, TX U.S.A. Such information may be aailable, 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 aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, 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 hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, 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 deeloping, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. Trademarks IBM, the IBM logo, Tioli, the Tioli logo, AIX, DB2, Informix, OS/2, NetView, Tioli Enterprise, Tioli Enterprise Console, TME, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation or Tioli Systems Inc. in the United States, other countries, or both. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. 42 IBM Tioli Enterprise Console: Release Notes