Toad for IBM® DB2®

Version 3.0.1

Release Notes

September 2007


Contents

Welcome to
Toad for DB2

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information


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.

 


New in This Release

Review the following:

Updates in Toad for DB2 3.0

 

New Features in Toad for DB2 3.0


Resolved Issues and Enhancements

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

 

Resolved Issues and Enhancements in 3.0.1

Feature

Resolved Issue

Change Request

General
Toad has resolved the character issue that occurs when Regional Options is set to Turkish on the client computer. CR#224551
Case#555563
Editor
If a user attempts to close the Editor when a lock exists on an object because of an uncommitted transaction, the Editor notifies the user of this condition. CR#224712
Case#540318
Schema Compare Schema Compare is automatically enabled for users with commercial or term licenses for the Standard, Professional, or Xpert editions of Toad for DB2 2.5 or earlier. CR#223702
Case#550259

 

Resolved Issues and Enhancements in 3.0

Component

Resolved Issue

Change Request

General Korean code page issuesrepeating characters in the Editor and import and export issueshave been addressed or resolved. CR#201538
Case#484626
Option to have Toad remove comments from SQL before execution has been implemented under Tools | Options | Database | DB2. CR#213765
Case#529227
Connection information is now being properly added to the support bundle. CR#213808
Installation Silent installation is now available. CR#200792
Case#481561
Connection Manager In the Client Configuration wizard, the Authentication field now has an Not Specified (NOSPEC) option. CR#201753
Case#481133
The Operating System drop-down list on the Add a Host  page in the Client Configuration wizard now uses a single Windows option to represent all Windows types. CR#204638
Case#491829
Previously, if you upgraded IBM DB2 for LUW version 9 from FixPak 0 to FixPak 1, specifying the Work with Existing option, Toad for DB2 might issue an exception error when you tried to establish a database connection. To resolve the issue, Toad for DB2 version 3.0 now ships with the IBM DB2 for LUW version 9 FixPak 1 modules. CR#204844
Database Browser/ Obj Palette
You can now remove columns when altering a table. CR#156271
Case#391667
Performance time in generating table scripts has improved significantly. CR#191534
Case#460284
The expand bar between the Parent Table Information and the This Table sections is working properly. CR#192553
Case#462812
You can now generate DDL for dependencies (for example, triggers, views, grants, indexes, procedures, and so on) from the Script tab if you select Generate script for dependent objects. CR#195671
Case#468471
The USER and GROUP keywords are now properly generated in the GRANT statement of the table DDL. CR#196653
Case#472046
Newly created indexes are now showing in up on the Indexes tab on the right-hand side of the browser. CR#197858
Case#474681
Issues with separators in trigger scripts has been resolved. CR#201407
Case#480305
DDL script now shows ALLOW REVERSE SCANS on indexes. CR#201389
Case#484643
Table editor now supports both COMPRESS and VALUE COMPRESSION. CR#202702
Case#490028
CLOB columns now display their size with the correct byte designation. CR#204490
Case#494668
You can now generate the DDL for the selected objects and its dependencies from the Script tab if you select Generate script for dependent objects. CR#204491
Case#494685
Adding a container to a tablespace no longer generates the error "SQL0104N An unexpected token '-' was found following 'ADD TO STRIPE SET.'" CR#204658
Case#493644
DDL script now shows WITH DEFAULT clause. CR#206226
Case#498970
The error generated when processing a view script no longer occurs. CR#209844
Case#507431
The user can now use the lower-left green button to toggle between edit and read-only mode on the Data tab. CR#209106
Case#511935
The error "Object reference not set to an instance of an object" generated when browsing the Used By tab for tables could not be reproduced. CR#214721
Case#522183
The errors generated when clicking between different tables in the browser cannot be reproduced. CR#214723
Case#522187
Generating the script for a view on the Script tab no longer produces a script-processing error. CR#218072
Case#531345
You can now filter by the number of rows when setting schema filters. CR#187906
Trigger DDL no longer displays as a single row on the Triggers tab for a table. CR#201408
Double-clicking on a trigger on the Trigger tab for a table now takes you to that trigger in the browser. CR#201410
Debugger The "Unable to initialize debug session" error that is generated when you attempt to debug procedures in DB2 for LUW is a DB2-related issue. A future release of a DB2 unified debugger should help reduce the occurrence of this issue. CR#213765
Case#517909
Case#529227
Editor Toad has normal limitations on the performing row counts. CR#199771
Case#479827
If user changes the schema in the drop down, both SET CURRENT SCHEMA and SET CURRENT SQLID statements will be executed. CR#205955
Case#497777
The data grid no longer locks down after data is changed and the query rerun. CR#210700
Case#502892
You can now use the same parameter name more than once for multiple tables in a query. CR#163853
The inability to generate a DDL script when the code pages on the server and client do not match is no longer an issue. CR#136103
Explain Plan The explain plan now supports Korean characters. CR#184449
Export Data When exporting a large amount of data, the user is now prompted to re-execute the currently running query to avoid reading the complete dataset into memory. CR#201720
Case#484690
Log Reader for DB2
The code page issue has been resolved. Connecting to a database no longer generates the error "Object reference not set to an instance of an object" and shuts down Toad. CR#219371
Case#534404
Search conditions in the Log Reader Advanced Search feature are processed with OR logic, not AND logic. CR#194746
A message now displays on the Redo tab on the DML/DDL page if UPDATE command is not supported. CR#202373
Log Reader now generates the correct Undo script to insert BLOB, CLOB, DATALINK, or LONG VARCHAR values in a table. CR#202602
An exception error is no longer generated when the user attempts to select a transaction on the Transactions page after canceling a rerun of the Read Log File wizard. CR#202699
Migration Issue with migrating Oracle stored procedures to DB2 is resolved. CR#172843
Case#422459
Object Search You can search Unicode databases. CR#166781
Schema Compare Schema Compare now shows differences in the DB2-generated name for the same procedure on the source and target, but will not generate an ALTER script. CR#218070
Case#529304
SQL Modeler (now Query Builder) SQL generated in the SQL Modeler could not be executed in the Modeler. This has been fixed. CR#183510
Case#441482
SQL Optimizer (LUW only) The SQL Optimizer toolbar icon is enabled only when you have Quest SQL Optimizer for DB2 installed. You can download SQL Optimizer from the following location as part of the Toad for DB2 Xpert Edition trial:

http://www.quest.com/toad-for-db2/Software_downloads.aspx

Once installed, click the SQL Optimizer toolbar icon in Toad to launch the SQL Optimizer.

CR#153015
SQL Recall You can now see the entire SQL query when you move the mouse cursor over the SQL Text entry in the SQL Recall window. CR#177941
Version Control Previously, some error messages are currently available with English language content only. This issue has been resolved by an overall design change. CR#140084

 


Known Issues

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

Feature

Known Issue

Change Request

General Customized options selected in the Configuration wizard are not applied if you are running as a Restricted user. CR#216699
Installation/

Upgrade

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 in some DB2 native tools. CR#192879
Case#462823
Connection Manually configuring a connection using the Client Configuration Wizard fails on a Windows 2003 64-bit machine. CR#202308
Attempting to launch Toad results in a System.Security.Policy.PolicyException error.
 

Workaround:
Ensure that the system administrator has placed Toad in the correct code group with permissions set to execute code.

CR#166752
Case#408845
Data Diff Viewer Comparing a script results grid with an XSD file does not work. CR#219662
Data Reports Currently, you cannot crate a Label Report in the Toad Data Report wizard. CR#215945
Database Browser/Obj Palette
Currently, you cannot grant privileges to a tables' columns for users. CR#184359
Any action that results in an advanced alteration on a table that contains constraints results in the tablespace being placed in a check pending state. This occurs because Toad loads the table data before re-creating the constraints.
 

Workaround:
Run the IBM DB2 Check Data utility to remove the pending state from the affected tablespace. The data loads correctly and the constraints are enforced.

CR#222564
An advanced alteration on a unique index generates an incorrect DROP syntax for dropping foreign key restraints. CR#219910
Performance problems might occur when browsing a large number of database objects.
 

Workaround:
If performance issues do arise and caching is enabled (that is, Enable caching is selected in Toad on the Tools | Options | Database | Cache page), do the following to help maximize performance: Verify that the Maximum in-memory size value specified on the Cache page is greater than or equal to the Current in-memory value displayed. If necessary, increase the Maximum in-memory size value.

CR#220761
Debugger Currently, the debugger does not support Unicode schema names. CR#184638
Editor Toad cannot execute an SQL script in the Editor if syntax highlighting is disabled (Tools | Options | Editor | Highlighting Styles). CR#167980
The following object types are not found when using the View Object at Cursor feature:
  • Triggers
  • Procedures
  • Functions
  • Users
  • Hosts
CR#164917
Export Data Binary data types cannot be exported in this release. CR#170430
When exporting large result sets (approximately 500K), you might run out of memory before the operation completes.

Workaround:
Create a view for the query and export that view.
CR#203483
Exporting more than 65,536 rows to an Excel 2007 instance causes an error.


Note: This issue does not affect Excel 2000 or 2003.

CR#211832
Help (LUW only) Object Details and Object Editor windows in the Database Browser/Object Palette have limited documentation in this release. This documentation will be expanded in a future release. N/A
Log Reader for DB2 If the user has selected the incorrect processor architecture, the wrong error message is displayed as the Log Reader reads files CR#181504
Log Reader does not support a proxy when using FTP to access log files. CR#199332
The Log Reader temporary files on the local drive are not deleted under the these circumstances: Toad is shut down via Task Manager while Log Reader is loading log information, or the FTP connection is aborted while Log Reader is loading log information. CR#199340
The Log Reader Undo/Redo SQL wizard currently does not provide a comment in the script to explain when the Log Reader is unable to redo or undo a specific command. CR#199336
Log Reader cannot parse commands involving DATALINK columns. CR#199338
Log reader creates temporary files in Log_Reader_installation_path/Tmp directory on the local disk. Normally, these files are deleted. However, these files can remain on the local disk if, while the Log Reader was loading files, either the FTP process was aborted or Toad was closed down through the Task Manager. CR#199340
Results from running the Advanced Search function show an invalid data type value for distinct type, structured type, and DATALINK columns. CR#202208
The Undo script for stored procedures contains incorrect syntax. CR#202327
Object names using different encoding schemes are not displaying properly in the Advanced Search window. CR#202667
The Log Reader can parse the log files for only the database to which it is currently connected. N/A
For a multi-partitioned database, the Log Reader can parse the log files for only the database partition to which you are currently connected. N/A
Schema Compare (LUW only) If the source schema contains a table alias with the same name as the target schema, synchronizing the schemas results in the target schema name being replaced with the actual table name from the source table. CR#140343
Toad Security The DBA edition of Toad for DB2 overrides all Toad Security settings. However, this override feature is currently not working. CR#221808
Version Control Toad is providing a more in-depth integration with popular VCS vendors. Currently, Toad integrated version control with Visual SourceSafe. If you are using CVS or SCC as the provider from the previous release of Toad, you currently cannot use those providers in Toad. Also, you might not want to migrate settings to the current release. N/A
The Update Schema function for version control often requires that objects be dropped and recreated. If tables are referenced by foreign key constraints, the following error occurs when executing the script:
 

"Could not drop object N because it is referenced by a FOREIGN KEY constraint."

CR#214601
Currently Version Control handles only DB2-standard schema names and file and folder names that are compatible with the underlying Version Control repository. CR#217475
You currently cannot check object list definitions into version control. CR#217524

 


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.

Feature

Known Issue

Change Request

General You cannot insert a double-byte character into a database with a single-byte codepage. IBM PMR30857,756,000 states that this configuration is not supported. CR#220327
Case#537948
Installation You cannot install DB2 for LUW 8 on the same system that already has Toad for DB2 3.0 installed. This problem exists because of a current DB2 limitation in which DB2 for LUW 8 cannot be installed on a system on which DB2 for LUW 9 resides. (Toad for DB2 includes a customized version of DB2 for LUW 9.)
 

Workaround:
If you need to install DB2 for LUW 8, uninstall Toad, install DB2 for LUW 8, and then reinstall Toad. For more information, refer to the Release Notes for IBM DB2 9 for Linux, Unix, and Windows.

CR#187913
An SQL0805N error occurs when performing a DML statement on a database.
 

Workaround:
Refer to the following IBM documentation for an explanation and a solution:

http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&dc=DB520&q1=DML&uid=swg21208123&loc=en_US&cs=utf-8&lang=en

CR#220160
Database Browser/ Obj Palette (z/OS only) Attempting to drop a distinct type or sequence with a delimited blank name results in following error due to server side abends:
 

"IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003"

This is a known IBM DB2 issue and IBM has opened APAR PK3269 to track this issue.

N/A
(z/OS only) In some cases, a user can revoke INSERT privileges on a table for the owner and cause a cascading revoke of privileges for any user (including the revoker) who was granted privileges by the table owner. This is a known IBM DB2 issue and IBM has opened APAR PK30558 to track this issue. N/A
Schemas containing empty names or special characters are not supported in this release and will display as QUEST_SCHEMA_PLACE_HOLDER when used. CR#133127

CR#133139

A Microsoft .NET Framework issue causes an exception error when you attempt to browse the Data tab for a table containing a decimal value with a precision greater than 28 or 29. This issue is described in http://msdn2.microsoft.com/en-us/library/xtba3z33(vs.71).aspx. CR#186529
(z/OS only) The following DB2 error is generated when you try to refresh an MQ table:
 

"ERROR [58031] [IBM] SQL1034C The database is damaged..."

This error is identified in APAR PQ97328. The APAR states that, if the statement text in the CREATE TABLE statement for a materialized table is more than 4K, the statement text stored in the SYSVIEW.VIEWS catalog table entries for the table (after the first three sequence number entries) contains garbage.

The APAR has been fixed with PTF UK00557. However, any materialized tables created before this fix need to be dropped and recreated and REFRESH rerun.

N/A
Timestamp data causes exceptions when you click the Data tab or attempt to query the table. This issue is related to the IBM DB2 APAR IY87346. CR#220839
Data Grid (z/OS only) Tables that contain decimal data larger than 28 or 29 decimals results in an error stating:

"Value was either too large or too small for a Decimal."

This is due to a limitation in the .NET Framework in which the maximum decimal that the Framework can handle is 10^31 with 0 decimal.

Workaround:
Perform the following:

  1. Click the Filter Data icon in the data grid.
  2. Select the SQL tab.
  3. Select the Enable custom SQL checkbox.
  4. Enter a query that casts the decimal column as a character data type with 32 characters similar to the following:

SELECT COLUMN, CAST ("DECIMALCOLUMN" AS CHAR (32)) AS DECIMAL FROM DB2ADMIN.TESTDECIMAL

Note: When using this workaround, if the number of characters is less than 32, leading zeros display.

CR#186529

CR#186535

You cannot add data to tables that include columns that have the GENERATED ALWAYS AS option enabled. The IBM Command Builder generates the INSERT statement and includes the generated always column, which results in the following error:

"A value cannot be specified for column "GEN" which is defined as GENERATED ALWAYS. SQLSTATE=428C9"

Workaround:
Use the Editor to insert data into tables that include the "Generated always as" option set.

CR#142504
Debugger When compiling with debug, it is recommended that you disable AutoCommit (Tools | Options | Database | General) to allow a rollback if there is a problem when dropping and creating the procedure. Once you successfully create the procedure, commit the changes before starting the debugging session. N/A
When debugging, you must enter a value for every start parameter, regardless of whether they are input or output values or an error message incorrectly informs you that the procedure must be compiled with debug information. CR#143234
(LUW) The following error message is displayed when you attempt to modify a watch value during a Debug session on a DB2 for LUW 9 database:
 

"ERROR [57011] [IBM][DB2/NT] SQL0954C Not enough storage is available in the application heap to process the statement. SQLSTATE=57011"

The call to modify the watch value fails on DB2, and the server runs out of heap memory.

Workaround:
To avoid the heap memory issue, increase the application heap size on the server.

CR#188846
(z/OS) A message stating that a procedure is not compiled with the Debug code, when in fact it is, is being generated. This issue is due to an error in the z/OS implementation of Create_Session. CR#207662
The "Unable to initialize debug session" error that is generated when you attempt to debug procedures in DB2 for LUW is a DB2-related issue. A future release of a DB2 unified debugger should help reduce the occurrence of this issue. Case#517909
Case#529227
CR#213765
Editor Attempting to create an object in the SQL Editor when the schema selected from the drop-down list in the Editor toolbar is different than the schema you logged into, results in an error. Toad issues a SET CURRENT SCHEMA statement the first time you execute a script/statement.
 

Workaround:
You can use either of the following methods as a workaround:

  • Select the schema that you are logged into and fully qualify the schema name for the objects.
  • Issue a SET CURRENT SQLID statement to set the schema on which you want to create objects.
CR#183855
Export Wizard In order to export to an Office 2003 or 2007 Excel instance, the Office 2003 Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations:
 

2003 PIAs
http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en

2007 PIAs
http://www.microsoft.com/downloads/details.aspx?FamilyID=59DAEBAA-BED4-4282-A28CB864D8BFA513&displaylang=en

CR#138239
Help After installing Microsoft Security Update 896358, selecting a topic in the help file when using the Web Browser (Internal Help) results in the topic displaying in the navigation pane.
 

Workaround:
Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. If you want to use Internal Help, you will need to disable some features in the security update. Refer to Microsoft Knowledge Base article http://support.microsoft.com/kb/896905/ for steps to re-enable these features in ActiveX.

CR#129554
After installing Microsoft Security Update KB922616, attempting to view the Help file from the Web Browser (Internal Help) results in the following error:
 

"COM object that has been separated from its underlying RCW cannot be used"

Workaround:
Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. If you want to use Internal Help, you will need to disable some features in the security update. Refer to Microsoft Security Bulletin MS06-046:

http://www.microsoft.com/technet/security/Bulletin/MS06-046.mspx

N/A
Log Reader Sometimes DB2 writes an UPDATE command to the log after a CREATE TABLE command is executed. An exception error occurs when the Log Reader attempts to parse the record for the UPDATE command because the record contains unexpected or unparsed data. CR#201537
Schema Compare (LUW only) You cannot synchronize schemas if the Code Pages on the compared schemas do not match. CR#141383
Version Control Quest recommends using the native VSS implementation in Toad rather than VSS via SCC integration. When using VSS via SCC, if the file does not have the attributes that SCC expects, issues with the file being updated properly might occur. CR#138078

 


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.

 


System Requirements

Verify that your system meets the following minimum 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.

Platform

600 MHz minimum

Memory

512 MB of RAM minimum, 768 MB recommended

Note: The memory required may vary based on the following:

  • Applications that are running on your system when using Toad
  • Size and complexity of the database
  • Amount of database activity
  • Number of concurrent users accessing the database
Hard Disk Space

171 MB of disk space required to run Toad

Note: The disk space required can vary based on the edition of Toad installed.

Operating System

Microsoft® Windows® 2000, XP Professional (32-bit or x64), 2003

Windows Vista (tested on 32-bit Ultimate edition with XP Graphics)

Additional Software

.NET Framework
Microsoft .NET Framework 2.0 or later

Note: In order to run Toad, the .NET security policy must be set to unrestricted. For more information, see User Privilege Requirements.

Browser
Microsoft Internet Explorer 6.0

PDF Viewer
Adobe® Acrobat® Reader 5.0 or later (for viewing the Toad for DB2 Getting Started Guide)

Other Requirements SVGA monitor with a minimum resolution of 800x600, 1024x768 recommended

 

Server Requirements

Each DB2 database server requires the following:

Database Versions

IBM DB2 UDB for z/OS 8.1 or later

Note: Toad supports DB2 for z/OS running in Full Function mode, but does not support DB2 running in Compatibility mode at this time.

IBM® DB2 UDB for Linux, UNIX, and Windows (LUW) 8.1.5 or later, 9.0

Database Operating System Platforms z/OS (V1R6 Base Services [5694-A01] or later)

Linux, UNIX, and Windows:

  • IBM AIX 5.1, 5.2, 5.3
  • HP-UX 11i 1.5, 2 (32- and 64-bit)
  • Red Hat Enterprise Linux AS release 3 and 4 (32- and 64-bit)
  • Solaris 7, 8, 9, 10 (32- and 64-bit)
  • SuSE 7, 8, 9
  • Windows 2000, 2003 (including 64-bit), XP

 

User Privilege Requirements

The following user privileges are required for installing and running 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.

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

  1. 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.

  1. Exit the Command Window.
  2. 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:

DB2 Subsystem Requirements

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

 


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. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. 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:

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

 


Getting Started

Contents of the Release Package

The Toad for DB2 release package contains the following products:

  1. Toad for DB2 3.0
  2. Quest IBM DB2 z/OS component
  3. Product Documentation, including:

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.

Caution:
  • Do not attempt to manually import catalog entries from the IBM CLP window provided with Toad. If you have any DB2 ODBC entries, db2cfimp will overwrite your existing ODBC system DSN entries and can cause previously configured DB2 ODBC connections to stop working.
  • 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 in some DB2 native tools.

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.


For More Information

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

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:

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