Toad^® for IBM DB2

Version 4.0.1  (Click here for previous versions)

Release Notes

November 12, 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

Toad for DB2 4.0.1 is a maintenance release containing primarily internal fixes and enhancements to the 4.0 release, especially to the Object Migration feature.

For a description of resolved customer issues resolved in this release, see Resolved Issues and Enhancements in 4.0.1.

For a review of the updates and new features in the previously released Toad for DB2 4.0, refer to Updates in Toad for DB2 4.0 and New Features in Toad for DB2 4.0.

Note: The Log Reader component for Toad for DB2 (LUW) has been sunset and no longer ships with Toad for DB2.

Updates in Toad for DB2 4.0

Click to review enhancements in the following areas:

• Toad in general

• Database administration

• Data management

• Query development

• Version control

General

Updates to overall Toad environment include the following:

• Many of the menu items have been reorganized to help you locate features faster.
• You can now generate a report of assigned keyboard shortcuts. This is useful for keeping up with any customized shortcuts you create:

• You can now share notes about objects, lookup tables, and hidden column settings with other users by specifying a network share location under Object Annotation Cache in Tools | Options | Database | Cache.
• Toad now supports opening Excel 2007 (.xlsx) files. You can also export data to an Excel 2007 instance, but cannot export to an Excel 2007 file or import data from an Excel 2007 file.
• Toad includes performance enhancements in the following areas:
  • Database Explorer - Reduced time in fetching and formatting data and in populating object lists.
  • ALTER scripts - Reduced time in generating both native and Advanced Alter scripts.
  • Migration wizard - Reduced time in generating dependency lists and migration scripts.
  • Schema Compare - Reduced time in identifying object differences and generating synchronization scripts.

Additionally, new index recommendations are available to optimize overall Toad performance in your DB2 for z/OS environments. See Recommended Indexes to Optimize Toad Performance in DB2 for z/OS.

Database Administration

This release includes enhancements to the following areas of database administration:

For overall DB2 management

For DB2 for z/OS environments only

For DB2 for LUW environments only

For Overall DB2 Management

• The Database Browser has been renamed to Database Explorer.
• The Object Palette has been renamed to Object Explorer and automatically opens to a tree view when you connect to a database.
• The tree view in the Database Explorer has been enhanced to show detailed object information. When you click an object-type node in the tree, the right side shows a list of objects and their properties that you can sort and arrange. You can then right-click those objects to perform actions on them:
   

  
   

• A single new Dependencies tab replaces the former Use and Used By tabs for an object in the Database Explorer. This tab lists first-level dependencies in a tree view. Right-click a dependent object for a menu of actions you can perform on that dependency.
   

  
   

• To optimize performance, the Script tab no longer contains the Generate script for dependent objects option. Instead, use the DDL Script wizard or the Migration feature to generate scripts for objects and their dependencies. (In the Object Migration wizard, select Empty database for the target Connection type field.)
• For a more streamlined user-interface on object tabs in the Database Explorer and Object Explorer, some buttons that accessed object-management functionality have been removed. You now access these functions by right-clicking objects and selecting menu options.
• A new shortcut to the Drop Objects window is now available: Select one or more objects in the Database Explorer or Object Explorer, and press DELETE.

• When performing an advanced alter (an alter that requires the drop and re-creation of a DB2 object), you can no longer execute the resulting script from the object editor if the Always preview script in object editors option is enabled. Instead, after you review the script, Toad sends it to the editor, where you can edit the script using the editor's many features before executing it. The Always preview script in object editors option is found in Tools | Options | Database | General.
• When using the Generate SQL right-click menu from the Object Explorer or Database Explorer, SQL is no longer formatted by default. If you want to format SQL, select the Automatically format generated SQL checkbox in Tools | Options | Explorer | General.
• Toad allows you to save and reload global Schema Compare options in Tools | Options | Schema Compare.
• Constraints now have a separate tab and object editor in the Database Explorer or Object Explorer, allowing you to view their properties and to manage them easily:

• The Migration wizard has been reorganized to include a Customize Migration page. This page lets you specify exactly the types of information you want to migrate--for example, DDL, data, statistics, permissions, or packages and plans. Additionally, you can specify whether to drop existing objects, preserve target data, or execute RUNSTATS after the migration. The Advanced button provides options for more detailed customization, such as parameters for rebinding DB2 for z/OS procedures during migration and options to ignore certain object attributes during the object compare:

 

After you specify the options for the overall migration on the Customize Migration page, you can update whether to migrate DDL, data, and statistics for individual objects:

For DB2 for z/OS Environments Only

Advanced alter scripts in DB2 for z/OS now generate -STOP and -START tablespace commands when necessary.

For DB2 for LUW Environments Only

• Toad now provides a full object-editor interface to manage stored DB2 for LUW procedures and functions:

• When you click Applications in the Database Explorer or the Object Explorer, you can now view dynamic SQL and SQL statement information for an application running in your DB2 for LUW environment:

• Toad now has the functionality to attach and detach partitions in DB2 for LUW tables. Right-click a partitioned table, and select Attach/Detach Data:

Data Management

This release includes enhancements to the following data management features:

Data export

Data import

Data grids

Data Export

• You can now export data to an Excel 2007 instance, but cannot export to an Excel 2007 file.
• Export data into an existing spreadsheet, including an existing worksheet or a new one. You can also specify the column and row where you want to begin adding data. This allows you to build charts and graphs from an existing spreadsheet and “refresh” the report by updating the data worksheet.

• Save export settings as a template that you can use for scheduled automation scripts. For more information, see the new feature Task  Automation.

Data Import

• Import data into a new table you create on-the-fly or into an existing table.
• Save import settings as a template that you can use for scheduled automation scripts. For more information, see the new feature Task Automation.
• Currently, you cannot import data from an Excel 2007 file.

Data Grids

• You can now compare result sets from the current editor or a different editor in the Database Explorer's Data tab or the editor's Result Sets without having to save one of the sets to a file:

 

You can also save a result set and later use it for comparison. This is useful from the Database Explorer's Data tab when, over time, the data might be changing and can then be compared against this data that was saved.

• You can now right-click a data grid and select Show | option to customize the look and feel of the grid without having to open an options page:

• You can quickly find and replace data by pressing CTRL+F in any data grid.

• You can now make minor changes to the underlying query in a Toad pivot grid. To edit the query, right-click in the data area of the pivot grid and select Edit Underlying Query. If you add or remove a column, a dialog warns you that you should create a new query.

• You can specify an integer format that is separate from the number format in Tools | Options | Environment | Grid:

Query Development

This release includes enhancements to the following query development functionality:

Query Builder

Editor

SQL Optimizer for DB2 LUW

Query Builder

• You can now specify whether to generate a SELECT, INSERT, UPDATE, DELETE, or CREATE statement from the toolbar.

If you select this action to generate an INSERT, UPDATE, DELETE, or CREATE statement with a single table or view already in the Query Builder, you cannot add another table or view because this action can only apply to a single table or view. Also, if you add more than one table or view to the Query Builder, this action is disabled because it only applies to a SELECT statement.

You cannot execute an UPDATE or CREATE statement in the Query Builder. Instead, click to send the statement to the editor and execute it there.

• You can now manually edit a query in the Query tab of the Query Builder. Any differences between the SQL in the Query tab and Diagram tab are highlighted. Toad also supports full editor functionality in the tab, including code completion and snippets.

• Queries executed in the Query Builder are now saved to SQL Recall so you can re-use them.

Editor

• Group execution is now integrated in the editor so you can execute SQL across multiple instances.

• Execution of scripts and statements has been combined into the toolbar button (Keyboard: F5). If you do not select a statement in the editor, the default is to execute the entire script.
• A new button executes statements in the script from the cursor position through the end of the script. The button is useful when you need to restart a script from a certain location.

  Note: If the cursor is positioned at the end of a line, the script runs from the beginning of that line through the end of the script.

   To add this button to the editor toolbar, click on the toolbar, and select Add or Remove Buttons | Editor| Execute From Cursor.

• Toad Insight (Intellisense) has been redesigned and renamed to Code Completion. Additional code completion enhancements include:
  • Additional statement types are supported including update, delete, insert, call, and truncate table.
  • Comments, object data types, and parameters display, if available.
  • Functions that return a table type now display.
  • Complete join statements are now generated.
  • Local variables now display when you enter the @ symbol. To display global variables, enter the @@ symbol.

Code completion options are located in Tools | Options | Editor | Code Completion:

• You can now press CTRL+SHIFT+SPACE to invoke the "Surround With" code snippets. To use this functionality, select the text you want the template to surround and press the shortcut key to select from the following:

SQL Optimizer for DB2 LUW

The latest release of SQL Optimizer for DB2 LUW (3.0) is now available for Toad for DB2.

Version Control

This release includes the following updates to version control functionality:

• Toad now supports the Team Foundation Server (TFS) version control provider. In order to use TFS, you must install the Visual Studio Team Foundation Server MSSCCI Provider on the same computer as Toad.

  Note: This is not the same client that you install with Visual Studio. You can download the MSSCCI Provider from one of the following locations:

  2005 MSSCCI Provider: http://www.microsoft.com/downloads/details.aspx?FamilyID=87e1ffbd-a484-4c3a-8776-d560ab1e6198&DisplayLang=en

  2008 MSSCCI Provider: http://www.microsoft.com/downloads/details.aspx?familyid=FAEB7636-644E-451A-90D4-7947217DA0E7&displaylang=en

  For more information about configuring TFS, see Configuration Prerequisites in the help.

• To eliminate identification errors, Version Control stores procedures with a new name format.

New Features in Toad for DB2 4.0

The following new features were added to this version of Toad for DB2:

• Task automation

• Space management features

• SQL tuning in your DB2 for z/OS environment

• Support for additional DB2 utilities

• Data compare and synchronization

• Editor support for DB2 for z/OS commands

• Reverse query execution

• Auto-save feature in the Editor

• New DB2 for LUW database administration features

Task Automation

The Automation tool is now available with Toad for DB2. Automation helps you build a script containing a sequence of activities--common SQL tasks--that you can execute immediately or schedule for later execution using Toad Job Management functionality. To invoke Automation, select Tools | Automation. Here are some of the Automation features:

• Support for these automation activities:

  Select to File	Execute an existing SQL script or Query Builder query and export the results to an Excel, HTML, or CSV file. You can then use additional activities to add the exported result file to a zip file, attach the file to an email, or copy the file.   Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script.
  Execute SQL	Execute an existing SQL script or Query Builder query.   Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script.
  Select to Editor with Results	Execute an existing SQL script or Query Builder query and save it and any results sets in a Toad editor file (.tef). This file format is useful for building scripts that have large result sets that you do not want to continue executing or for saving results when you have not finished building a script.
  Export Wizard	Export data from databases, tables, views, or query into a CSV, Excel, or other file. You can save the export settings as a template that you can use for scheduled automation scripts.
  Import Wizard	Import data from a CSV, Excel, or other file into a new table or append to an existing table. You can save the import settings as a template that you can use for scheduled automation scripts.
  Toad Pivot Grid	Refresh an existing Toad pivot grid and export results to a report. You can then use additional activities to add the pivot grid to a zip file, attach it to an email, or copy it.
  Delete File	Delete one or more files from a specified location.

• You can click an activity to automatically add it to the Design pane.
• Toad automatically adds a connection to the current database anytime you add an activity that requires a connection:
   

  
   

• Exception handling lets you set exception handling and error logging by double-clicking the Script Settings activity that displays by default in the Design pane. Once you specify these settings, they are used by all subsequent automation scripts.
   

  
   

• You can save properties for any activity as a template for future use.

Space Management

Toad for DB2 offers a new set of features that manage space in your DB2 for LUW environments:

Space Calculator

Space Exceptions Report

Table Partition Analysis

Space Usage Report

Space Estimator (when creating a tablespace)

Space Calculator

Space Calculator lets you simulate adding and deleting objects and updating object sizes to determine the impact these changes might make on space usage in a DB2 for LUW tablespace. Space Calculator also provides options to run maintenance utilities on objects and to generate scripts that actualize your space-usage scenarios.

Note: To provide accurate SMS tablespace information, Toad requires that the BUFFERPOOL database manager monitor switch be turned on.

To access this feature, right-click one or more tablespaces, tables, or indexes in the Database Explorer or Object Explorer, and select Space Management | Space Calculator. Or right-click objects in an object list, and select Tablespace (or Table or Index) | Space Management | Space Calculator.

Space Exceptions Report

The Space Exceptions feature is an online report that identifies those tables and indexes in your DB2 for LUW database that would benefit from a reorganization to improve space usage and performance. From the report, you can open a Toad for DB2 Reorg or Runstats session on those objects that require maintenance.

To access this feature, right-click one or more tables or indexes in the Database Explorer or Object Explorer, and select Space Management | Identify Exceptions. Or right-click objects in an object list, and select Table (or Index) | Space Management | Identify Exceptions. You can also select Tools | Identify Exceptions and drag objects on to the report.

Table Partition Analysis

The Table Partition Analysis tool helps you determine how best to redistribute the data among the current data partitions in a DB2 for LUW table. Using this tool, you set up data distribution scenarios. Table Partition Analysis then calculates the number of table rows that DB2 would store in each partition for the current scenario and shows a graphical depiction of this data distribution. Once you determine the best scenario for redistributing the data, you can have Table Partition Analysis generate the script that alters the data partitions using the scenario values and redistributes the table data accordingly.

Space Usage Report

The new Space Usage tab for Tablespaces in the Database Explorer reports current space-related information (gathered from the system catalog) for a selected tablespace in your DB2 for LUW database. The tab shows space allocation for the tablespace itself, for the containers that make up the tablespace, and for the objects that reside in the tablespace.

Note: To provide accurate SMS tablespace information, Toad requires that the BUFFERPOOL database manager monitor switch is turned on.

Space Estimator

When you create a DB2 for LUW tablespace, use the Space Estimator page in the Create Tablespace window to estimate the size of the tablespace you are creating. You can then apply these estimations to help you adjust container space or select appropriate containers in the tablespace definition.

SQL Tuning in Your DB2 for z/OS Environment

Toad introduces SQL Tuning for DB2 z/OS to help you optimize SQL that you execute in your DB2 for z/OS environment. SQL Tuning provides an interactive workspace in which you tweak the SQL in various scenarios and then run Explains on the scenarios to compare their access plans, costs, I/O and CPU usage, and results. To assist you in optimizing SQL, SQL Tuning generates and implements tuning advice for each scenario.

SQL Tuning is integrated with other components in Toad for DB2 to accommodate your workflow. For example, during your Toad session you can do the following:

• Invoke a SQL Tuning session from the editor to optimize the performance of SQL that you are currently editing:
   

  

• Directly open a SQL Tuning session on SQL included in a package or plan listed in the Database Explorer or Object Explorer.
   

  

• Open a blank SQL Tuning session (Tools | Quest Tools | SQL Tuning) to tune SQL you enter manually or import from an external file:
   

  

Support for Additional DB2 Utilities and Commands

New functionality supports even more DB2 utilities and commands:

• Toad has added the ability to generate SET INTEGRITY statements for DB2 for LUW tables. Select one or more tables, right-click, and select Utilities | Set Integrity:

• The new Utilities tab in the Database Explorer or Object Explorer for DB2 for LUW shows information about currently executing commands and utilities. Right-click on a utility to set its impact priority:

Data Compare and Synchronization

Toad provides an easy way to compare and synchronize data in your tables. The Data Compare wizard (Tools | Compare | Data Compare) sets up and runs data comparisons based on specific columns and keys in one or more source and target tables:

Data Compare then builds the synchronization script for you:

Editor Support for DB2 for z/OS Commands

The editor now provides the DB2 for z/OS command support described below. This support requires that the Quest IBM DB2 z/OS component, available with Toad for DB2 3.0 or later, be installed. For more details, see the Quest IBM DB2 z/OS Component Installation Guide that resides in your Toad installation folder.

• The editor supports execution of DB2 for z/OS commands.
• DB2 for z/OS command snippets are now available for insertion in your editor script.

Reverse Query Execution

You can now reverse engineer queries from the Editor or Query Builder. For more information, see Reverse Engineer Queries in the help.

Auto-Save Feature in the Editor

Toad automatically saves a backup copy of open editor files that have been modified at five minute intervals (default). It also saves a backup copy anytime you execute the SQL. If the application does not terminate normally, the next time you open Toad the backup copies automatically open in the editor so you can either save changes to your regular file or discard them.

You can specify the backup interval in Tools | Options | Environment | General:

Note: You cannot load multiple copies of Toad when this option is selected.

New DB2 for LUW Database Administration Features

This release adds new functionality to edit catalog statistics for tables; edit multiple tables and tablespaces from one Alter window; rebuild indexes, triggers, and views; and manage array types in your DB2 for LUW environment.

• The new Edit Catalog Statistics feature lets you manually modify catalog statistics for a DB2 for LUW table, its columns, or its indexes to influence the behavior of the query optimizer when SQL executes against the table. This feature is especially helpful if you use your test environment to simulate optimization behavior in your production environment. To access this feature, right-click a table and select Edit Catalog Statistics.

• A new multiple-object Alter window that lets you conveniently alter certain common properties for a group of DB2 for LUW tables or tablespaces in one alter session. To launch this window, select multiple tables or tablespaces in the Database Explorer or Object Explorer, right-click, and select Alter Table (or Tablespace):

• Rebuild DB2 for LUW indexes, triggers, or views easily. Select one or more of these objects from the Database Explorer or Object Explorer, right-click, and select Rebuild object type. The Rebuild window lists the objects you selected and generates the REBUILD script. Simply execute the script.

• You can now create, alter, and drop DB2 for LUW 9.5 array types. Use the Distinct Type object editor to manage array types:

Resolved Issues and Enhancements

Click the following links to view issues addressed and enhancements implemented in the Toad for DB2 4.0 releases, including this latest release 4.0.1:

• 4.0.1

• 4.0

Resolved Issues and Enhancements in 4.0.1

Resolved Issues and Enhancements in 4.0

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

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 Toad for DB2 Installation 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 Requirements

• Citrix Requirements

• LDAP Requirements

• Compile and Debug Requirements for Stored Procedures

• Requirement for Capturing Container Information in a DB2 for LUW Multi-Partition Database

• 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 in some DB2 native tools.

Server Requirements

Each DB2 database server requires the following:

User Privilege Requirements

The following are user requirements for installing and running Toad:

User Requirements to Install Toad

Only Administrators and Power Users can install Toad.

Note: The following exceptions exist for Power Users:

• A Power User cannot install Toad on a computer running Windows Vista Enterprise. This is a Windows limitation because Vista does not support Power User mode.
• (DB2 only) A Power User cannot install Toad if a DB2 for LUW version earlier than 8.1.7 already exists on the computer. Only an Administrator can install Toad under this condition. However, if the computer has an existing DB2 for LUW 8.1.7 or later installation, a Power User can install Toad as long as this user belongs to the DB2ADMNS or DBUSERS group.

If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any user--a Power User, Restricted User, Vista standard user--on the computer.

If a Power User installs Toad, a Restricted User cannot do the following:

• Associate file extensions.
• See the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop.

User Requirements and Restrictions for Running Toad

The following describes the requirements and restrictions for users who launch and run Toad:

• A Windows 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).
• A Windows Vista user must be either an administrator or a standard user that belongs to an Vista Administrators group. Additionally, to enable full functionality in Toad when Vista’s User Access Control security feature is turned on, the standard user must run Toad as an administrator. (Right-click the Toad icon on the Vista desktop, and select Run as administrator.)
• A Windows Power User or Restricted User does not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, this user can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad.
• As a minimum to manage DB2 for z/OS subsystems in Toad, the user ID specified in the Toad connection profile for a specific subsystem must either have SYSADM privileges or be granted SELECT permissions on the DB2 catalog tables. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document:

  http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSAuthorizations.doc

• To run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

1. Select Control Panel from the Windows Start menu.
2. Double-click Administrative Tools.
3. Double-click Microsoft .NET Framework 2.0 Configuration.
4. Select My Computer, and then select the Runtime Security Policy node.
5. Select Evaluate Assembly from the list of tasks in the right panel and browse to the location of Toad.exe in the File field.
6. Click Next and set the permission to Unrestricted.

• To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features.

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server Service Pack 2 using the Metaframe Access Suite 4.0 and Citrix Presentation Server Clients 10.2. For information about installing Toad in a Citrix environment, refer to Install Toad on Citrix Systems in the Toad for DB2 Installation 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: Keep the following mind:

• 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.
• Currently, Toad for DB2 supports only access to DB2 LDAP catalog entries. Toad does not support the management of these entries.

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 Connections window.

Databases on the LDAP server should now be available from the Database Alias drop-down list in the Connections window. To complete the Toad connection setup, you must create a Toad profile for each database. See Create Toad Connection Profiles in the Toad for DB2 Installation Guide.

Requirement for Capturing Container Information in a DB2 for LUW Multi-Partition Database

Certain Toad functions use the DB2 snapshot monitor to capture information about containers used in DB2 for LUW databases. To capture this information for a multi-partition database, the snapshot monitor requires that all database partitions be active. Therefore, to ensure that Toad obtains container information across all partitions, execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. This command keeps all partitions on the database active. For more information about ACTIVATE DATABASE, refer to the IBM DB2 for Linux, Unix, and Windows documentation.

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 DB2 Universal Database 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. The following link contains the DDL for indexes that can optimize Toad performance on your DB2 for z/OS subsystem. Keep in mind that the creation of these indexes is a recommendation only. The indexes can have different results in different environments, depending on the number of DB2 objects and the amount of data involved. To create these indexes, edit and run the DDL contained in the following file:

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

Additionally, if the schema drop-down lists in the Object Migration wizard populate slowly, consider creating an index on the SCHEMA and CREATOR columns in the catalog table for each object type. Here is a list of some of the object-type tables:

SYSIBM.SYSSYNONYMS
SYSIBM.SYSSEQUENCES
SYSIBM.SYSROUTINES
SYSIBM.SYSTABLES
SYSIBM.SYSDATATYPES
SYSIBM.SYSINDEXES
SYSIBM.SYSTRIGGERS
SYSIBM.INDEXES

Requirements for Object Migration

The following are requirements for using Toad's Object Migration wizard to migrate DB2 objects and their dependencies.

Migration of Tables with Referential-Integrity Relationships

When migrating a table that has referential-integrity relationships to other tables, select Include objects referenced by those originally selected and Include objects that are dependent upon those originally selected on the Customize Migration page in the wizard. These options generate the statements necessary in the script to migrate the related tables. If you do not select these options, 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 exist on the same computer.

  Note: When you are migrating objects between different versions, the Migrate catalog statistics on the Customize 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

Supported Providers

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:

Required Provider Clients

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

Note: Toad connects to your version control system based on login information included in your configuration. Your version control client does not need to run for Toad to connect.

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 Xpert and DBA editions for z/OS ONLY -- other editions of Toad for DB2 on z/OS and all versions of Toad for DB2 on LUW are fine.
   

  The Toad SQL Tuning for DB2 z/OS feature 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:

• Toad for DB2 4.0.1
• Quest IBM DB2 z/OS component
• Other components based on the Toad for DB2 edition that you purchased
• Product documentation, including:
  • Toad for DB2 Installation Guide
  • Quest IBM DB2 z/OS Component Installation Guide
  • On-line help
  • Other documentation based on the Toad for DB2 edition that you purchased

Installation Instructions

For important information about installing Toad for DB2, refer to the Toad for DB2 Installation 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, Akonix, Akonix, AppAssure, Benchmark Factory, Big Brother, ChangeAuditor, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, 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.

Third Party Contributions

Toad for DB2 contains some third-party components (listed below). Copies of their licenses may be found on our web site at http://www.quest.com/legal/third-party-licenses.aspx.

 CONTAINS Runtime Modules of IBM DB2 Runtime Client Merge Modules Version 9; Copyright IBM Corporation 2006 All Rights Reserved

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