WebSphere MQ Workflow Version 3.4.0 - Service Pack #2 (June 2003) ------------------------------------------------------------------ INDEX -------------------------------------------------------------- 1. Installing Service Pack #2 1.1 Installing on Microsoft Windows NT/2000/XP 1.2 Installing on IBM AIX 1.3 Installing on Sun Solaris 1.4 Installing on HP-UX 2. Important Notes 2.1 Applying Service Packs to the Web Client 2.2 Documentation error for Portal Client 2.3 No more automatic changes to the CLASSPATH environment variable 2.4 Database problems 3. New supported Operating systems releases and Database releases 3.1 IBM AIX V5.2 for PowerProcessor Chip 3.2 Sun Solaris V9 3.3 Oracle Database 9i Release 2 (9.2.0.1) on IBM AIX and SUN Solaris 4. Changes 4.1 Changes in Service Pack #1 4.2 Changes in Service Pack #2 5. License Notices -------------------------------------------------------------- 1. Installing Service Pack #2 ============================= 1.1 Installing on Microsoft Windows NT/2000/XP ------------------------------------------------ 1.1.1 Which files must be downloaded? The Service Pack consists of several self-extracting and self-installing executables. There is one for each National Language version of IBM WebSphere MQ Workflow. To make the distribution of client updates easier, there are three types of self-extracting executables. They update Client, Buildtime, or full installations. The Client and Buildtime packages contain only certain WebSphere MQ Workflow components and they are only applicable if these components or a subset of these components are already installed. Use the full package to update installations that include more than these components. The Client package consists of the API Runtime Library, Program Execution Agent, Runtime Client, Lotus Notes API, Administration Utility, Samples, Java, and the Java Agent component. The Buildtime package includes just the Buildtime component and the associated samples. The following self-extracting executables are available: Full Package: ------------- W340ENA2.EXE - U.S. English language version W340CSA2.EXE - Simplified Chinese language version W340CTA2.EXE - Traditional Chinese language version W340DEA2.EXE - German language version W340ESA2.EXE - Spanish language version W340FRA2.EXE - French language version W340HEA2.EXE - Hebrew language version W340HUA2.EXE - Hungarian language version W340ITA2.EXE - Italian language version W340JPA2.EXE - Japanese language version W340KOA2.EXE - Korean language version W340NLA2.EXE - Dutch language version W340PBA2.EXE - Brazilian Portuguese language version W340PGA2.EXE - Portuguese language version W340PLA2.EXE - Polish language version W340TRA2.EXE - Turkish language version W340RSA2.EXE - Russian language version Client Package: --------------- W340ENC2.EXE - U.S. English language version W340CSC2.EXE - Simplified Chinese language version W340CTC2.EXE - Traditional Chinese language version W340DEC2.EXE - German language version W340ESC2.EXE - Spanish language version W340FRC2.EXE - French language version W340HEC2.EXE - Hebrew language version W340HUC2.EXE - Hungarian language version W340ITC2.EXE - Italian language version W340JPC2.EXE - Japanese language version W340KOC2.EXE - Korean language version W340NLC2.EXE - Dutch language version W340PBC2.EXE - Brazilian Portuguese language version W340PGC2.EXE - Portuguese language version W340PLC2.EXE - Polish language version W340TRC2.EXE - Turkish language version W340RSC2.EXE - Russian language version Buildtime Package: ----------------- W340ENB2.EXE - U.S. English language version W340CSB2.EXE - Simplified Chinese language version W340CTB2.EXE - Traditional Chinese language version W340DEB2.EXE - German language version W340ESB2.EXE - Spanish language version W340FRB2.EXE - French language version W340HEB2.EXE - Hebrew language version W340HUB2.EXE - Hungarian language version W340ITB2.EXE - Italian language version W340JPB2.EXE - Japanese language version W340KOB2.EXE - Korean language version W340NLB2.EXE - Dutch language version W340PBB2.EXE - Brazilian Portuguese language version W340PGB2.EXE - Portuguese language version W340PLB2.EXE - Polish language version W340TRB2.EXE - Turkish language version W340RSB2.EXE - Russian language version 1.1.2 Using the new Russian language support To use the Russian language support that is being introduced with Service Pack 2, perform the following steps: 1. Install the English version of the base package using the installation CDs. 2. Switch the installation language in the installation profile to Russian by entering the following command at a command prompt : fmczchk -c inst:i,Language,RUS 3. Apply the service pack, as described in 1.1.3. 1.1.3 Installing the Service Pack 1. Make sure that you have stopped all running WebSphere MQ Workflow processes and services before installing the Service Pack. 2. In the Windows Explorer, double click on the executable for the package-language combination that you require. 3. After the program has unpacked the files to the temporary directory, the installation starts. 1.2 Installing on IBM AIX ------------------------- 1.2.1 Which files must be downloaded? Download the package wf340a2u.tar.gz (56 MB) and unpack the file to a temporary subdirectory. You need approximately 113 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340a2u.tar.gz | tar -vxf - 1.2.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". 2) As root, perform the command 'slibclean'. 3) Update your WebSphere MQ Workflow 3.4.0.x installation (with or without hotfixes applied) using smit - "update to latest level" to level 3.4.0.20. Note: Your configuration (profiles, /var/fmc/...) will not be modified by the update. However, the installation profile /usr/lpp/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=2". After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.2.3 Using the new Russian language support The Russian language support message file is automatically added with Service Pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru_RU 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt: fmczchk -c inst:i,Language,rus Optionally, you can edit the file /usr/lpp/fmc/fmcrc. 1.3 Installing on SUN Solaris ----------------------------- 1.3.1 Which files must be downloaded? Download the package wf340s2u.tar.gz (44 MB) and unpack the file to a temporary subdirectory. You need approximately 155 MB to unpack the file. To create the update installation image, unpack the downloaded file using the command: gzip -dc wf340s2u.tar.gz | tar -vxf - For a client-only installation, use the file wf340s2c.tar.gz (16 MB), which needs about 53 MB to unpack. 1.3.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow System using the admin utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.x files (with or without having hotfixes applied) to level 3.4.0.20: Issue the following command line as user "root", replacing the path "/tmp/fmc340u2.pkg" from this example with the fully-qualified path and filename of your ".pkg" file: pkgadd -d /tmp/fmc340u2.pkg (full package) or pkgadd -d /tmp/fmc340u2cl.pkg (client package) Accept the installation of this package and overwrite files from the previous package 3.4.0.x. Note: Your configuration (profiles, /var/fmc/...) will NOT be modified by the update. However, the installation profile /opt/fmc/fmcrc will be updated to reflect the new level "ServiceLevel=2". After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.3.3 Using the new Russian language support The Russian language support message file is automatically added with Service Pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt: fmczchk -c inst:i,Language,rus Optionally, you can edit the file /opt/fmc/fmcrc. 1.4 Installing on HP-UX ----------------------- 1.4.1 Which files must be downloaded? Download the package wf340h2u.tar.gz (50 MB) and unpack the file to a temporary subdirectory. You need approximately 52 MB to unpack the file. To create the update installation images, unpack the downloaded file using the command: gzip -dc wf340h2u.tar.gz | tar -vxf - For a client-only installation, use the file wf340h2c.tar.gz (15 MB), which needs about 16 MB to unpack. 1.4.2 Installing the Service Pack 1) Stop all running WebSphere MQ Workflow processes, for example, by shutting down the WebSphere MQ Workflow system using the administration utility "fmcautil". Make sure that all WebSphere MQ Workflow processes are stopped and there are no product files in use. 2) Update your WebSphere MQ Workflow 3.4.0.x files (with or without having hotfixes applied) to level 3.4.0.20 as follows: a. Install the new package using 'sam'. If you prefer, You can use 'swinstall' with the appropriate command-line parameters. b. Select the "software" icon. c. Select "add software to local host". d. Choose 'installation from disk'. e. To install the client-only package, enter the fully-qualified path to the file "FMC340U2CL.PKG" and the filename itself. f. To install the full package, enter the fully-qualified path to the file "FMC340U2.PKG" and the filename itself. g. Choose "Install" from the "Actions" pulldown menu and confirm twice. h. After the installation proceed with step 3. Note: Your configuration (profiles in /var/fmc/...) will NOT be modified by the update. 3) Run the command fmczinsx -o upd to update the installation profile /opt/fmc/fmcrc with the new level "ServiceLevel=2". This value reflects the current service pack level of the installation. After you have performed these steps, your system is ready to run. You can restart your queue manager, the trigger monitor, and the administration server as usual by invoking the following programs: strmqm FMCQM & runmqtrm -q FMCTRIGGER -m FMCQM & fmcamain & 1.4.3 Using the new Russian language support The Russian language support message file is automatically added with Service Pack 2. To switch the Workflow language settings use the procedures described in Appendix D of the Installation Guide: 1. Change the system language code by using export LANG=ru_RU.iso88595 2. Switch the installation language in the Workflow installation profile to Russian ("rus"). To do this, enter the following command at a command prompt : fmczchk -c inst:i,Language,rus Optionally, you can edit the file /opt/fmc/fmcrc. 2. Important Notes ================== 2.1 Applying Service Packs to the Web Client -------------------------------------------- NOTE: The version String on the Logon page of the Web Client is not updated to 3.4.0.2. If you want to change it, it is recommended that you change the String in the Logon.jsp located in the \skeleton\WebClient\webpages directory. The version is then shown correctly when you follow the instructions below. It is recommended that you have a separate configuration for the Web Client. This way, you can easily apply service to the Web Client as follows: 1. Install the WebSphere MQ Workflow Service Pack 2. If you are using WebSphere V4, back up the Web Client files that you have changed (for example, WebClient.properties) to a directory that is NOT a subdirectory of \cfgs or \installedApps. This is because the complete subtree of your old Web Client configuration will be deleted in the next step. 3. Delete the Web Client configuration using the configuration utility 'fmczutil'. 4. Remove the Web Client's application server in WebSphere. If you are using WebSphere Version 4, you must remove the Web Client enterprise application before you can remove the application server. 5. Create a new Web Client configuration. 6. Merge the changes you made with the new Web Client files. This includes re-installing the samples for the Web Client, such as the AuditTrailHandler and the Groupworklist sample. NOTE: For the AuditTrailHandler, the Web Client needs Xalan-Java 2, which is available from http://xml.apache.org/xalan-j It is recommended that you delete the temporary directory that you created for the compiled JSPs of the Web Client on your application server. When using IBM WebSphere V3, this temporary directory is \temp\\MQWFClient-, for example, d:\WebSphere\AppServer\temp\default_host\MQWFClient-WEBC. When using IBM WebSphere V4, this temporary directory is \temp\\WebClient_Server_-_. If you want to use https in WebSphere 4.0.2, set the system properties under jvm settings. Set the property 'java.protocol.handler.pkgs' to the value 'com.ibm.net.ssl.internal.www.protocol'. For further update details, see the WebSphere documentation. 2.2 Documentation error for Portal Client ----------------------------------------- Installation Guide, Appendix H, page 411, parts 1a and 3g refer to the Portal Client war file as 'MQWFPortalClient.war'. This is incorrect, the actual file name is 'fmcopcli.war'. 2.3 No more automatic changes to the CLASSPATH environment variable ------------------------------------------------------------------- Before Service Pack 2, the installation of a Service Pack updated the CLASSPATH variable to contain the latest version of the workflow .jar file. Starting with Service Pack 2 you must update the CLASSPATH manually to switch to the latest version. This is to prevent breaking any existing Java client configurations. The latest .jar files can be found in \bin\java340 where is the number of the Service Pack. It is recommended to add "fmcojagt.jar" to the CLASSPATH. If you have a thin installation, where "fmcojagt.jar" is not installed, then you must add "fmcojapi.jar". 2.4 Database problems --------------------- 2.4.1 DB2 Version 8 If you use DB2 Version 8.1, make sure that you have installed the fix for DB2 APAR IY39361. 2.4.1.1 DB2 Version 8 on Sun Solaris On Sun Solaris, there is a known problem in the setup of the XA communication. IY41550 is the corresponding DB2 APAR number. As long as there is no fix available, the SQL error 998 with a reason code of 09 and a subcode of 02 might occur. You must make sure that the value of the database manager configuration variable "tp_mon_name" is set to "mq" (rather than mqmax). The DB2 instance owner can set this configuration parameter using the following command: db2 update dbm cfg using tp_mon_name mq Furthermore, the Websphere MQ Series library directory has to be checked for the existence of a library or link named "libmqmax.so". If neither the link nor the library exists, then the link can be created by the MQ installation owner using the following command: ln -s /opt/mqm/lib/libmqmax.so /opt/mqm/lib/libmqmax.a 2.4.2 Oracle Database 8i Release 3 (8.1.7) Make sure that you have installed Oracle 8i patchset 8.1.7.1, or higher. With earlier versions of the Oracle DBMS, the runtime servers do not start. On AIX, do not use Oracle 8i patchset 8.1.7.2. 2.5. Problems with the configuration checker fmczchk ----------------------------------------------------- When you use the fmczchk utility to check a server configuration, it might display the error message: FMC34032E: Cannot load TP Monitor library mq.dll: The specified module could not be found (rc = 126). Erroneously, the utility checks for mq.dll (or libmq.a|.so|.sl) instead of mqmax.dll. If you receive this message, check that the library mqmax (for Windows mqmax.dll, for AIX libmqmax.a, for Solaris libmqmax.so, and for HP-UX libmqmax.sl) exists, is accessible and loadable. If so, you can ignore the error message. 3. New supported Operating systems releases and Database releases ================================================================= 3.1 IBM AIX V5.2 for PowerProcessor Chip ----------------------------------------- With service pack 2, IBM AIX Version 5.2 can be used. Install the product on IBM AIX 5.2 and follow the IBM AIX installation steps for the service pack. 3.2 Sun Solaris V9 ------------------ With service pack 2, SUN Solaris 9 can be used. Install the product on SUN Solaris V9 and follow the IBM AIX installation steps for the service pack. 3.3 Oracle Database 9i Release 2 (9.2.0.1) on IBM AIX and SUN Solaris --------------------------------------------------------------------- With service pack 2, Oracle 9.2.0.1 can be used as the runtime database for WebSphere MQ Workflow on IBM AIX and SUN Solaris. Make sure that you have installed Oracle 9i Release 2. Before you can use this database version in a new configuration, you must set the environment variable 'FMC_CFG_RT_DBVERSION' to '9.2' and then start the configuration utility fmczutil to create a new configuration. 4. Changes ========== Service Pack 2 includes all the changes that were made in Service Pack 1. 4.1 Changes in Service Pack #1 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 17991 Canceling the suspending of a process instance makes list portlet unusable 18007 fmczchk on UNIX: Warning is displayed (default port 5010 not found) 18184 Some actions from PropertiesView are not executed 18318 Web Client Logon screen: German Language, Umlaut not shown correctly 18332 Question mark appended at process instance name 18363 Error with XML-Msg via SDDS together with MQ531beta 18451 IY39345 FMCZUTIL does not allow 8 character SIDs 18456 IY39437 System Log and Error Log are not deleted automatically. Depending on the FDL settings MESSAGE_RETAIN_PERIOD and ERROR_RETAIN_PERIOD, system log entries and error log entries in the MQWF runtime database are now deleted automatically by the administration server. 18467 IY39760 Rounding problems with float/string conversion 18468 IY39759 Expiration and Notification are not updated with ForceRestart 18472 IY39717 Web Client with JNDI Locator Policy and a remote JNDI Name Service does not work 18477 PMR49020 FMC00100E Internal Error on Workitem::Transfer() call 18486 IY39929 Creating MQWF databases using raw devices (remote) not possible 18507 Buildtime: No Mapping possible. Pressing OK leads to FMCKRequire 18518 PMR31252 An MQWF EXE Server address space controlled by WLM was not terminated 18542 Web Client: 'Suspend Instance' year field cannot be left empty 18543 Remove of deadlocks in a scenario with parallel processing of scheduling and cleanup server. Remove of deadlocks in scenarios with high workload and parallel processing of QryWorkItem and Checkout/CheckinWorkitem. 18544 IY40460 FMCEMAIN fails with FMC12250E error in FMCSYS.LOG when for example refresh on a process instance is called by a user who is not authorized. 18545 Use "MQ" instead of "mqmax" as TP_MON_NAME 18546 Unattended (default) configuration is not DB2 V8 enabled 18559 LDAP Bridge, sample command runbr on UNIX, z/OS: The parameter handling of this command file was not correct. 18587 IY41141 Allow Cookie ID different from JSESSIONID 18596 HP-UX: Configuration switch for Oracle or MQServer fails 18600 BufferPool not customizable in DB2 part 18608 IBM Java 1.4 RTE is not found by Workflow 18622 Transfer item in Portal Client does not work 18623 Web Client does not work with SupportPac WA82 18639 Error pages are not working correctly in Web Client 18657 Empty directory \bin\JAVA3401 if config Web Client WAS4.x/5.0 18658 IY41977 Queries with multiple GDC tables in order statement 18666 PQ72169 Long and Float constants in "IN" predicate of filter strings in queries 18668 Configuration Win: Registry contains a corrupted path for fmcerr.log\fmcsys.log 4.2 Changes in Service Pack #2 ------------------------------ The following problems are fixed: Nr. PMR/APAR Description 17583 A new MQWF SP modifies a System classpath wrong. 18140 Additional support for Oracle 9i Release 2 (9.2.0.1) 18578 IY41133 PEA GIVES CORE WITH LARGE NUMBER OF AUTO ACTIVITIES 18584 IY41200 Admin server shutdown on codepage conversion error. 18591 IY41159 When deploying the WebClient within WebSphere 4.0 using a name service port other than 900, fmczuitl fails with "FMC33993E Failed to execute the file 'GenPluginCfg.sh ..." 18601 IY41136 When adding a WebClient to a configuration, the advanced configuraion wizard shows "FMC33843E Incorrect Java Agent Cycle 0" 18630 Provide Russian translation for WebClient 18635 IY42398 On Microsoft Windows NT/2000/XP all servers terminate after a database deadlock. 18661 IY41930 Fmczutil aborts configuration after saving the profile when specifiyng an invalid path for the channel definition table. 18664 IY39472 FMCZCHK REPRESENTS XAOPENSTRING INCORRECTLY 18665 IY42006 MQWFPORTALCLIENT.WAR IN APPENDIX H SHOULD BE FMCOPCLI.WAR 18707 Honour MQMD report options for XML input queue 18718 LDAP Bridge: Forward references for PERSON not handled correctly 18723 Cleanup PortalClient.properties 18745 PQ73201 CLIENT API CHANGES ON HOST 390 - CALL SERVICE FOR DETAILS 18779 Support of WPS 4.2 18780 Potential security issue in Web Client 18790 IY43908 On Solaris: password prompt of fmcautil and fmcibie truncates passwords to 8 characters 18793 PMR50519 FMCHEPRO does not contain all API modules (CICS) 18805 IY43934 FMC21913E during verify with asynchronous UPES in blocks 18825 Can't find resource bundles for Web Client samples 18886 WebClient NullPointerException in servlet.log if no custom CommandHandler is enabled 18894 PQ74477 Profile or keyword in profile not found (RC=124) in CICS 18908 IY44826 WEBCLIENT'S SESSIONCONTEXT OBJECT GETS CORRUPTED 18929 IY45044 Create or query a persistent list may return FMC_ERROR_DYNAMIC_QUERY_SIZE_TOO_LONG RC=141) even, if the persistent query works fine in the past. 18950 IY45198 Web application aborts on SUN Solaris. 18951 IY45203 Long DBCS process names truncated incorrectly 18975 IY45519 API call UserSettings() on the service object returns RC=100 on clients before V340, if the server is V340. Set a new profile variable on the server to allow back-level clients to connect to a server with 3.4. without the RC=100 error. With the fmczchk utility, you can change your profile. You need to change all server profiles with back-level clients, if this API is used. The following example sets the needed profile variable for the configuration ID FMC. "fmczchk -c inst:m,FMC_BEHAVE_LIKE_332,1 -yFMC" 18987 IY45592 Global container mapping within subprocesses is not performed 5. License Notices ================== This product internally uses the XML4C parser and therefore is obliged to distribute the following license text: --------------------------------------------------------------------- * The Apache Software License, Version 1.1 * * * Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "Xerces" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation. * * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * ==================================================================== * * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation and was * originally based on software copyright (c) 1999, International * Business Machines, Inc., http://www.ibm.com. For more * information on the Apache Software Foundation, please see * . */ --------------------------------------------------------------------- ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2001 International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. ---------------------------------------------------------------------- All trademarks and registered trademarks mentioned herein are the property of their respective owners.