Toad^® for IBM DB2

Version 3.1  (Click here for previous versions)

Release Notes

February 2008

Contents

Welcome to Toad for DB2

Toad for DB2 is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to DB2 expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.

Back to Top

New in This Release

Review the following:

• Updates to Toad for DB2 3.1

• New Features in Toad for DB2 3.1

To review the updates and new features included in Toad for DB2 3.0, access the New in This Release section in the previous Release Notes.

Updates in Toad for DB2 3.1

This release includes updates in the following areas:

• General

• Database Administration

• Data Management

• Query Development

General

• Default connection document now set in Configuration wizard—Toad no longer prompts you in a separate window at startup to specify which document should open by default whenever you open a connection. You now specify this default using the Configuration wizard.

Database Administration

• General in Toad:
  • Drop Script option added to SQL Generation feature—The Generate SQL right-click menu in the Database Browser or Object Palette offers the option to generate a DROP script.
     

    

  • Formatter options applied to Generate SQL scripts—When you generate SQL using the Generate SQL feature in the Database Browser or Object Palette, Toad formats the SQL using the options defined on the Editor - Formatter page in the Options window.

• Specific to DB2 (LUW and z/OS platforms)
  • Schema Migration wizard enhancements—The following updates have been implemented:
    • The Migration wizard now automatically sends migration scripts directly to Toad's Editor, allowing you to review the scripts before executing the migration.
    • If a dependent tablespace listed on the Objects Selected for Migration page is the result of your selecting the Include dependencies option, the tablespace is initially shown as unselected. From this page, you can then select it for migration if that is your intention.

      

    • The wizard now automatically detects and displays any conflicts upon opening the Define Transformation Rules and Migration Options page. (You no longer have to perform an extra button-click to generate the list of conflicts.)
• Specific to DB2 for LUW
  • Table editor enhancements—The Create/Alter Table window layout and controls are easier to understand and navigate. Additionally, the new interface supports data partitioning (a new feature in DB2 for LUW 9).
     

    

  • Details for event monitor tables—In the Database Browser or Object Palette for an event monitor, select the Target Tables tab to view the list of tables to which an event monitor writes data. (The tab is available if the event monitor definition includes WRITE TO TABLE.) Double-click a table entry to view the details for that table.
  • Statistics profile support during advanced ALTERs and migrations—During advanced ALTERs, Toad preserves statistics profiles for tables. During migrations, Toad generates statements to migrate statistics profiles.
  • Index RUNSTATS execution during advanced ALTERs and migrations—During advanced ALTERs and migrations, Toad automatically generates statements to update statistics on indexes.

  • New code page support for Log Reader—Log Reader for DB2 now supports code page 923.

• Specific to DB2 for z/OS

  • CHECK DATA execution during advanced ALTERs and migrations—During advanced ALTERs and migrations, Toad generates statements to run CHECK DATA as needed to remove the CHECK PENDING status from objects. The most common case in which the CHECK PENDING status is applied occurs when the generated script loads data in an the object that has foreign keys or check constraints.

Data Management

• Significant memory enhancements—This release implements major memory improvements for queries that return large result sets. When retrieving results, Toad uses a few megabytes of memory initially regardless of the size of the result set. Subsequent scrolling of the result set adjusts the memory usage to only the amount needed to display the results.

• Grid customization—You can now customize the grid style when a skin is applied to Toad. Define the grid style in the Configuration wizard (Tools | Configuration Wizard) or in Interface Options (Tools | Options | Environment | Interface).
   

  
   

• Read-only data—You can make all data grids read-only by default. Go to Tools | Options | Environment | Grid, and select Show data as read-only.
   

  

• Search data-Word or phrase searches are now available for data grids. Simply press Ctrl+F to set the search criteria. You can select Mark All in the Find window to highlight all cells in the grid that match the criteria.
   

  
   

Query Development

• Editor:
  • XQuery support—You can now execute XQuery statements from the Editor.
  • View scripts in a full-size window—Use docking controls to auto-hide or group the Editor panel, Code Navigator, and result sets. To display the Editor and Results panels in a separate, full-size window, drag and drop the Results tab into the Editor window.
     

    

    Press F6 to switch between the two panels.
     

    
     

  • Error line highlighting—Now you can highlight the line in the Editor that caused an execution error. To do this, double-click the error message in the Script Output tab.
  • Change case and add comments—You can now easily apply upper or lower case to text or comment and uncomment lines by selecting options from the Editor | Advanced menu or the Editor's right-click menu.

    
    
     

• Query Builder:

  • Date ranges—When you add a WHERE condition for a column that uses a date or time data type, a new Date Range tab displays in the Where Condition window. The Date Range tab allows you to select a plain text tag, such as Today, Last week, Last 30 days, or Current year. The tab is added to the WHERE condition of your query and, when executed, is substituted with a BETWEEN command using the appropriate date range. Date Range tags are also used in the Editor so that you can create queries manually.
     

    

New Features in Toad for DB2 3.1

This release offers new features in the following areas:

• General

• Database Administration

• Query Development

• Version Control

To review the new features included in Toad for DB2 3.0, access New Features in Toad for DB2 3.0 in the previous Release Notes.

General

• DB2 9 FixPak 3 modules installed—Toad for DB2 now ships and installs IBM DB2 9 FixPak 3 modules.
• Spotlight on DB2 launch point—Within the context of the current DB2 connection, select Tools | Spotlight on DB2 (or Spotlight on DB2 z/OS) to open Spotlight on DB2 to monitor activity and performance your database or subsystem.
   

  
   

Database Administration

• Specific to DB2 (LUW and z/OS platforms):
  • Data migration available in Schema Migration—Schema Migration now provides the option to migrate data from source to target objects. The migration process uses DB2 utilities and commands to offload the data at the source and reload it on the target. The process produces two scripts that can be ported to machines of your choice. The first script runs on the source database and exports the source data. The second script runs on the target database and contains the DDL to create objects at the target database and IMPORT statements to load those objects with data.
     

    
     

  • Option to define the data-preservation method for advanced ALTERs—You can specify that advanced ALTERs use either temporary tables or DB2 utilities and commands to offload and reload data when preserving it. Go to Tools | Options | Databases | DB2 | General to define the default method for all advanced ALTERs. You can override this default on the Alter window when altering individual objects.
     

    
     

  • New advanced ALTER options—You can globally set default behavior for the utilities that advanced ALTERs use to preserve data. Go to the Tools | Options | Database | DB2 pages.
• Specific to DB2 for LUW:
  • Native IMPORT, EXPORT, and LOAD utilities available—Toad lets you run the DB2 IMPORT, EXPORT, or LOAD utility on one or more tables to move data in IXF, ASCII, or worksheet formats. You can customize command options and generate, execute, and save the utility scripts. Toad's version of these utilities is compliant with DB2 for LUW 9.
     

    
     

  • Statistical views—Toad supports statistical views. You can now optimize and collect statistics on views so that the SQL optimizer can use them in access paths.
     

    
     

  • Utilities menu—Toad has a new Utilities sub-menu for easy right-click access to utilities that you can perform on a specific object.
     

    
     

  • Ability to start and stop event monitors—You can now start or stop an event monitor listed in the Database Browser or Object Palette. Simply right-click the event monitor and select the appropriate option (or click the appropriate option from object editor toolbar).
     

    
     

• Specific to DB2 for z/OS:
  • Native BIND, BIND LIKE, REBIND, DROP (or FREE) utilities available—Toad provides these DB2 utilities to manage your packages and plans. You can customize command options and generate, execute, and save utility scripts.
     

    
     

  • Quick REBIND for packages and plans—This feature lets you run a simple REBIND command (using system defaults) on multiple plans or packages. Simply right-click multiple plans or packages, and select Rebind... .
     

    
     

Query Development

• Query Builder:
  • FROM clause subquery support—You can now add a subquery to a FROM clause using the Query Builder toolbar or the right-click menu. A Queries panel displays on the left side of the window showing the From Clause Subquery element in the query tree. You can add tables and views and create joins for the subquery in the same way that you normally use the Query Builder to create queries.

    After creating the subquery, click the parent query in the Queries panel to return to the original query. A From Clause Subquery table now displays in the Diagram panel with all the columns in the subquery. Use this new table as you would any other database object.
     

    
     

Version Control

• New provider support—In addition to Visual SourceSafe (server and client version 6.0d), Toad Version Control now supports the following providers:
  • CVS (server version 1.11.22 on Solaris and 2.5.03 on Windows; client version 2.5.03)
  • Subversion (server and client version 1.4.2)

Back to Top

Resolved Issues and Enhancements

To review the resolved issues and enhancements included in the previous 3.0.0 and 3.0.1 releases of Toad for DB2, click here to access the "Resolved Issues and Enhancements" section in Toad for DB2 3.0.1 Release Notes.

The following is a list of issues addressed and enhancements implemented in this release of Toad for DB2:

Resolved Issues and Enhancements in 3.1

Back to Top

Known Issues

The following is a list of issues known to exist at the time of the Toad for DB2 release.

Back to Top

Third Party Known Issues

The following is a list of third party issues known to exist at the time of the Toad for DB2 release.

Back to Top

Upgrade and Compatibility

Please review upgrade information in the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Back to Top

System Requirements

Verify that your system meets the minimum requirements described in the following sections:

• Client Requirements

• Server Requirements

• User Privilege Requirements

• Citrix Requirements

• LDAP Requirements

• Compile and Debug Requirements for Stored Procedures

• Requirements for Executing DB2 for z/OS Utilities

• Recommended Indexes to Improve Toad Performance in DB2 for z/OS

• Requirements for Object Migration

• Version Control Requirements

Client Requirements

Toad for DB2 client installation requires the following.

Note: If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality is some DB2 native tools.

Server Requirements

Each DB2 database server requires the following:

User Privilege Requirements

The following user privileges are required for installing and running Toad:

• Only Power users and Administrators can install Toad.

Note: Power users cannot install Toad on a Windows Vista Enterprise machine. This Windows limitation is due to the fact that the Power User mode is no longer used in Vista and therefore cannot install applications.

• A Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS.
• If a Power user installs Toad, a Restricted user can run the application but cannot do the following:

  • Associate file extensions.

  • See the Toad for DB2 icon on the desktop or the Toad for DB2 menu options in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application from the install directory and place the shortcut on their desktop.

• If an Administrator installs Toad, the Administrator can share the Toad for DB2 desktop icon and menu items with any user on the computer.
• Network and LAN installations are currently not supported.
• In order to use Toad with DB2 for z/OS, any user who does not have SYSADM privileges must be granted SELECT permissions on the DB2 catalog tables.
• In order to run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

  1. From the Windows Start menu, select Settings | Control Panel.

  2. Double-click Administrative Tools.

  3. Double-click Microsoft .NET Framework 2.0 Configuration.

  4. Click + to expand My Computer, and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.

  5. Click Evaluate Assembly from the lists of tasks in the right panel. An Evaluate an Assemble window displays.

  6. Browse to the location of Toad.exe in the File field.

  7. Click Next to view permissions for Toad.exe.

  8. Set the permission to Unrestricted.

• In order to set or modify Toad Security settings, users must have privileges to create the QuestSoftware.ToadSecurity table if it does not already exist. If the table does exist, users must have privileges to insert, update, and delete data in the table.
• Power users and Restricted users do not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function to import catalog entries to Toad.
• To load log files on the Toad client machine for a Log Reader session, the user must have the following privileges:

  • READ permissions on the log files belonging to the database and on the directory where these files are stored

  • Database administrator privileges to read the database's log.

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server Service Pack 2 using the Metaframe Access Suite 3.0 and Citrix Presentation Server Clients 10.0. For information about installing Toad in a Citrix environment, refer to Install Toad on a Citrix Machine in the Toad for DB2 Getting Started Guide.

LDAP Requirements

To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.

Note: You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the machine is already configured to support LDAP.

To configure Toad to use LDAP

1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window.
2. Type the following command to enable LDAP support:

db2set DB2_ENABLE_LDAP=YES

3. Type the following command to specify the TCP/IP host name and port number of the LDAP server:

db2set DB2LDAPHOST=hostname[:port]

The port number defaults to 389 (default LDAP port) if you leave the port number blank.

4. Exit the Command Window.
5. Launch Toad and open the New Connection window.

Databases on the LDAP server should be available from the Database Alias drop-down list.

Note: At this point, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries (such as adding or removing them) Debugger Requirements

Compile and Debug Requirements for Stored SQL Procedures

The following are the requirements for using Toad to compile and debug stored SQL procedures in DB2 for z/OS.

Toad Client Requirements

To use the Toad debugger on stored SQL procedures, the following Toad client requirement must be met:

• The Toad client is running on a Windows XP machine.
• Java Runtime 1.4 or later is installed and specified in your system path.

DB2 Subsystem Requirements

Each DB2 subsystem on which you want to compile and debug stored SQL procedures must meet these requirements:

• To compile stored SQL procedures in Toad, the DB2 stored procedure SYSPROC.DSNTPSMP must be operational on the subsystem.
• To debug stored SQL procedures in Toad, the IBM DB2 installation job DSNTIJSD must be executed on the subsystem.

Requirements for Executing DB2 for z/OS Utilities

To bind and rebind packages and plans and to invoke utilities during advanced ALTERs on a DB2 for z/OS subsystem, Toad for DB2 requires the following:

• Each subsystem on which you are executing utilities must contain the DB2 objects that support the Quest DB2 z/OS dataset templates. These objects already exist on a subsystem if you have installed either of the following products on the subsystem:
  • The z/OS components for Quest Central for DB2 4.9 or later
  • The Quest IBM DB2 for z/OS component available with Toad for DB2 3 or later

If you neither product is installed on a subsystem, run edit and run the DDL that creates these objects. Click the following link to open the file containing this DDL:

http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadzOSTemplateDDL.txt

• The IBM stored procedure SYSPROC.DSNUTILU must be installed and operational on each subsystem on which you are executing utilities. For additional information about SYSPROC.DSNUTILU, refer to Appendix B of the IBM UDB for z/OS Utility Guide and Reference.

Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.

• When Toad generates an ALTER script that contains multiple UNLOADs and LOADs of table data, ensure that the DSN values in the dataset templates include a &SEQ variable to create unique dataset names. For examples on including this variable, refer to the dataset template definitions in the file http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadzOSTemplateDDL.txt.
• When you migrate data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. The definition for Reorg Unload template should define a dataset that resides on a pack (VOLSER) that is accessible by both the source and target subsystem.

Recommended Indexes to Improve Toad Performance in DB2 for z/OS

User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. To ensure the best possible performance from Toad, create the following indexes in each subsystem to which you are connecting in Toad:

• On the TSNAME column in SYSTABLES.
• On the BNAME column in SYSPACKDEP.
• On the COLLID  and NAME columns in SYSPACKAGE.
• On the  SYSCOLUMNS table, as defined in the following DDL. Edit the DDL as needed for your site.

CREATE INDEX TOADIX01
ON "SYSIBM"."SYSCOLUMNS"
("TBCREATOR" ASC,
"TBNAME" ASC,
"TYPESCHEMA" ASC,
"TYPENAME" ASC,
"COLTYPE" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 3600
SECQTY 3600
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;

• On the SYSTABLES table, as defined in the following DDL. Edit the DDL as needed for your site.

CREATE INDEX TOADIX02
ON "SYSIBM"."SYSTABLES"
("NAME" ASC,
"CREATOR" ASC,
"DBNAME" ASC,
"TSNAME" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 7200
SECQTY 7200
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;
 

Requirements for Object Migration

Adhere to these requirements when you use the Toad's Schema Migration wizard to migrate DB2 objects and their dependencies.

Methods for Handling Target Tablespaces

You must handle target tablespaces in one of two ways:

• Use the wizard's Transformation Rules to specify target tablespaces that already exist. If the specified tablespaces (and, in DB2 for z/OS, the databases to which these tablespaces belong) do not exist, Schema Migration assumes that you will create these tablespaces (and databases) before the you run the migration script. The wizard does not generate the DDL for these objects in the migration script.

  or

• Skip the Transformation Rules section, and let the wizard generate the migration script to include the DDL that creates the target tablespaces. However, the wizard bases this DDL on the DDL for the source tablespaces. You must edit the migration script before executing it to customize the DDL for the target environment.

  Notes:

  • Schema Migration does not migrate DB2 for z/OS databases. Therefore, it does not generate the DDL for databases to which the tablespaces belong.
  • In DB2 for z/OS, Schema Migration supports migrating a target tablespace that was implicitly created on the source. The DDL generated creates an explicit tablespace that uses the same name and database as the source tablespace. Additionally, Schema Migration generates the DDL to migrate all the tables in the tablepace.

Migration of Tables with Referential-Integrity Relationships

When migrating a table that has referential-integrity relationships to other tables, select the Include dependencies option on the Select Objects for Migration page in the wizard. This option generates the statements necessary in the script to migrate the related tables. If you do not select this option, you must edit the migration script to include these statements.

Additional Special Specifications for Sources and Targets

The following requirements and restrictions exist for source and targets:

• You cannot migrate objects between a DB2 for LUW and DB2 for z/OS platform and vice versa.
• You can migrate objects between different versions of DB2 on the same platform (for example, between DB2 for LUW 8 and DB2 for LUW 9) as long as both the source and target databases (or subsystems) exist on the same computer.

  Note: When you are migrating objects between different versions, the Include statistics by default on the Select Objects for Migration page in the wizard is disabled.

• Do not map two source schemas to the same target schema. (For example, you cannot map both source Schema A and source Schema B to target Schema C.)

Version Control Requirements

Toad for DB2 supports the following version control providers for the versions and platforms listed. Testing is not complete for versions and platforms not listed:

Ensure that you install the following on the same computer on which you installed Toad:

Back to Top

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

This release has the following known capabilities or limitations:

• Toad for DB2 for z/OS Advanced Developer and Suite Editions only:

  The SQL Optimizer feature for DB2 for z/OS supports single-byte character sets. Double-byte or multi-byte character sets are not supported.

  All product components should be configured to use the same or compatible character encodings and be installed to use the same locale and regional options.

• Toad Editions that contain Knowledge Xpert:

  The Knowledge Xpert feature is available with English language content only.

   

Back to Top

Getting Started

Contents of the Release Package

The Toad for DB2 release package contains the following products:

1. Toad for DB2 3.1
2. Quest IBM DB2 z/OS component
3. Product Documentation, including:
   • Getting Started Guide
   • Online Help

Installation Instructions

For important information about installing Toad for DB2, refer to the Toad for DB2 Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

For instructions on installing the Quest IBM DB2 z/OS component, refer to the Quest IBM DB2 z/OS Component Installation Guide. This guide is available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Back to Top

For More Information

Contacting Quest Software:

Refer to our Web site for regional and international office information.

Contacting Quest Support:

(Commercial and Trial Support only)

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com/.

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase articles/documents).
• Download patches and upgrades.
• Seek help from a Support engineer.
• Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.

Yahoo Group

(Freeware Support)

You can join the Toad for DB2 discussion group by sending an email to: toad_db2-subscribe@yahoogroups.com

Back to Top

© 2008 Quest Software, Inc.

ALL RIGHTS RESERVED.

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 If you have any questions regarding your potential use of this material, contact:

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries.  Other trademarks and registered trademarks used in this guide are property of their respective owners.

If you have any questions regarding your potential use of this material, contact:

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Back to Top