Toad^® for IBM^® DB2^®

Beta Version 4.5.0.722

Beta Release Notes

June 25, 2009

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

The Toad for DB2 4.5 Beta will be introducing new features, enhancements and fixes throughout the Beta cycle.

Optional Beta component downloads are available here!

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

Click to review enhancements in the following areas:

Toad in general
Database administration
Data management
Query development
Still under construction

General

New in this Drop

This drop contains fixes and enhancements to existing features.

From previous Drops

Toad DB2 now has a pre-requisite of the Microsoft .Net framework 3.5 Service Pack 1. (Previous versions/drops of Toad DB2 were able to work in .Net 3.5 environments without SP1). The Toad installation program will check to ensure that your machine has the .Net 3.5 SP1 pre-requisite. If it does not, the Microsoft .Net framework 3.5 SP1 download page will be displayed.

Misc.:

We have continued to add new features and address existing issues in this drop.
The SQL Recall window and the Code Snippets window can now be viewed by using the View menu.

Performance Improvements:

The startup code has been optimized and the result is a much faster startup time, especially for a “warm restart”.
The memory footprint has been reduced by optimizing the code and reducing the number of assemblies loaded.
The editor has been optimized to provide better support for medium to large scripts. Both the load time and memory footprint for loading scripts that are approximately 10 MB has been greatly improved.
Script output has been optimized to spool much faster and use less memory, especially in cases where large amounts of output are generated.

Options:

Many options that used to be managed in the Options window are now saved automatically when you close Toad. This allows increased consistency from session to session.
Toad includes new skins, such as Office 2007 and a true Default skin that better matches the standard Windows look-and-feel.

Misc.:

Toad now ships and installs IBM DB2 LUW Client v9.5.
The installation location for the DB2 client also has changed. It is now: C\Program Files\Quest Software\Toad for DB2 4.5 Beta\SQLLIB
Toad now has the .Net 3.5 framework as a prerequisite. During the installation, if it is determined that you do not have the appropriate version of .Net, a website will be displayed where you can download and install it as shown below.

To avoid unnecessary expansion when you accidentally mouse over a pinned window, you now have to click on a pinned window's tab to display it.

You can now easily close all tabs except the current tab when you right click on a tab and select "Close other Tabs"

You can now Drag and Drop a SQL file onto the Toad Toolbar to automatically open a SQL Editor with that file as shown below.

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

From previous Drops

Toad has introduced an option to keep the schema filter value per Database object type in the Database Explorer. To use this option navigate to Tools | Options | Explorer | General and check the 'Separate schema or database by type' checkbox as shown below. Checking this option is useful when you have different schemas for different object types.

The affects of checking the above option are seen back in the Database Explorer. Now you can set the schema filter to a different value per object type and Toad will retain and use those values when you go back and forth amongst different object tabs as shown below:

Note that the above Separate schema or database by type' option will work in the Database Explorer unless your Database Explorer view is in tree view.
Toad has also introduced a way for you to view all objects in the Database Explorer by default. If you specify an asterisk (*) in the 'Default schema/auth ID' value of your connection - as shown below:

Now with the asterisk specified above, when Toad opens a Database Explorer, the asterisk will be use as the Schema filter value, displaying all schema/objects by default.

You can now view and Grant/Revoke privileges at the column level for z/OS and LUW tables. The right-hand side 'Grants' tab displays column privileges if the user has them.

The Alter Table Privileges Editor now also allows you to quickly and easily generate Grants and Revokes at the column level.

You can now apply or remove a named filter using a drop-down beside the filter icon.

You can now hide object toolbars and access actions via a right-click menu instead. If you want to show the toolbars again, select Show Toolbar from the right-click menu.

A new 'Flat Tree' view can be selected to display Database Objects in a more traditional manner (similar to Quest Central for DB2).

The File...New Menu can now be used to create new database objects.

Additional Toolbar buttons have been added to the connection Manager to increase usability.
Click on the Tree-View button as shown below to create a host-instance-database hierarchical tree for easy database identification

Also, three additional buttons were added to improve connection management.

Toad now displays the TCPIP port number and platform on the connection screen for improved database identification.

Toad has added features for Aliases (and z/OS Synonyms) that allow you to view their data and columns, and easily generate SQL statements.

Toad has added the ability to easily tune SQL text for Views and triggers

Toad has added Code Completion capabilities into the View and MQT editors.

Toad has enhanced the permission editors to allow you to easily Grant or Revoke permissions to multiple users. First select the users, then right click on the column heading and select the action you want performed on those user permissions. See the picture below.

The Migration Wizard has been enhanced and updated in this beta:

You now can only invoke the wizard with a right-click context menu to migrate the objects that you have selected. (We have removed the main menu Tools | Migration option.) Since you will be invoking the wizard with objects, we have removed the wizard's old 'object filter' page.

The Migration Wizard no longer performs a compare and sync, but it will generate a migration script. If you wish to perform an object compare and sycn, you can use our new right-click context menu "Compare object". Since we are no longer performing a compare and sync in the Migration Wizard, you can no longer select "Empty Database" as your target connection type. You just need to select the target LUW Database or z/OS Subsystem.

This is the old filter page (appeared in previous releases of Toad DB2) that is no longer needed and no longer displayed in the Migration Wizard:

The Migration Wizard has several new options. The old option 'Force drop of any existing objects' has been renamed to 'Include DROP statements. If this option is selected the generated target script will contain DROP statements to drop the objects before they are generated. The 'Process multiple object levels' option is new. If unchecked only one level of dependent objects will be analyzed and migrated. If this option is checked multiple levels. for example, dependents of dependents will be analyzed and migrated.

Now in this Beta, if you are migrating a table Toad will automatically identify Indexes and triggers on that table and include them on the "Review Objects" panel.

The transformation Rules panel has been changed as it now pre-fills in target values with source values.

Since the Migration Wizard is no longer performing a compare and sync, if target objects already exist we will not be generating alter statements on those objects. The conflicts tab will display objects that already exist on the target. You can continue to generate the script or go back in the wizard and create a transformation rule that will get you around the conflict.

Toad has added a new Compare wizard. This wizard is invoked via a right-click context menu. The Compare wizard flows just like the Migration Wizard, however the Compare Wizard does perform a "compare and sync" against the target and will generate scripts that will create objects on the target and modify any existing target objects to be like the source objects. To invoke the Compare Wizard, select your object(s), right click and select the 'Compare Object' action as shown below.

Since the new Compare Wizard will perform a "Compare and Sync" to make any existing target objects just like the source objects, so the conflicts tab could flag additional conflicts as shown below.

Toad has introduced a new Extract DDL wizard. This wizard is also invoked via a right-click menu as shown below.

You can easily customize your script by clicking the option checkboxes on the wizard. If you select to include 'referenced' or 'dependent' objects you can granularly select Object types you want in your script as shown below. When the 'Build Script' button is clicked, a background task to generate your script is started and the resutling scrit is displayed in a newly opened SQL Editor tab.

Toad now provides the ability to generate scripts with #SYNC statements. These statements are syncpoints which can be used to restart scripts at certain statements. To enable this new feature go to Tools | Options | Database | DB2 | General and check the "Generate scripts with syncpoint statements" as shown below. To see how to restart a script in the editor at a syncpoint refer to the Editor section.

Extended alter and compare scripts now preserve Identity column values.

For DB2 for z/OS Environments Only

From previous Drops

You can now invoke the Toad SQL Tuning for DB2 on z/OS component with multiple statements.
To view information and download the Toad SQL Tuning for DB2 on z/OS Beta component click here.
Within a DB2 on z/OS SQL Editor session, you may now select one or more statements and click the button to launch the Toad SQL
Tuning for DB2 on z/OS component as shown below.

Toad SQL Tuning for DB2 z/OS will open with each statement as a separate scenario as shown below:

You can now also launch multiple statements from the Plan - DBRM SQL tab as shown below:

You can now view blobs and for bit data in EBCDIC in the data grid

Toad will now display a warning message when you attempt to use a feature requiring the Toad z/OS components being installed.

Toad now will generate extended alter, migration and compare scripts that will contain DB2 z/OS utility statements leveraging IBM DB2 parallelism during utility execution on partitioned database objects.
To enable this feature, ensure that the Unload and Discard template datasets use the &PART variable as part of the DSN mask. DB2 utilities will allocate, and write to/read from these datasets in parallel as the utilities are executing. The screen shots below show the two Dataset template definitions containing &PART:

Ensure those templates names are specified in your Tools | Options | Database | DB2 | z/OS | Load/Unload values:

The script below was generated via an extended alter on a table in a partitioned tablespace. This first screen shot shows the &PART used in the template dataset name for the unload utility:

This next screen shot shows the re-loading phase specifying a template dataset for each partition. The Load statement references each template, one for each partition:

The next screen shot shows the REORG utility using the SORTDEVT parameter which allows for parallel processing:

Toad has introduced support for generating REORG z/OS Utility statements for Tablespaces and Indexes. Note that the execution of z/OS Utility statements requires that the Quest DB2 components for z/OS be installed on your subsystem.
Now you can select one or more z/OS Tablespaces, right-click and select the actions in the 'Utilities' menu to easily generate and execute REORG utility statements as shown below.

On the windows shown below, you can easily specify Object parameters and command parameters to tailor your Utility statements.

Toad ships and uses a set of default Dataset templates. You can easily select a different Dataset template as shown below.

Scripts can be executed in the Utility window or sent to the SQL Editor for execution.

The Index...Utilities...REORG feature works in the same manner:

Toad has introduced the support to easily generate and execute Display, Start and Stop DB2 commands. Note that the execution of DB2 z/OS Commands requires that the Quest DB2 components for z/OS be installed on your subsystem.
Now you can select one or more z/OS Databases, Tablespaces, or Indexes, right-click and select the actions in the 'Commands' menu to easily generate and execute DB2 commands as shown below.

You can always send scripts to the SQL Editor for execution or execute them in the command window as shown below:

Toad introduced a new option to generate COPY statements before REORG statements in scripts generated during Tablespace Alters, Migrations and Compares. There are several new settings screens shown below related to this feature.

Now in generated scripts that contain REORG statements, a COPY statement will be generated before the REORG statement.

Toad has removed the 'Threads' tab from the Database browser and has created a New Subsystem tab. The right-hand-side of the Subsystem tab displays connection information and Threads.

Dataset templates are now displayed in the browser. You can now easily Create/Create Like/Alter/Drop Dataset template definitions. (Dataset templates are used during z/OS Utility statement generation.)

Toad has added a 'Datasets' tab on z/OS Tablespaces that displays Dataset, volume and space information. Note that the z/OS Components need to be installed for this new feature.

Toad has improved utility statement generation during extended alter, migration and compare script generation. Toad now generates utilities that act upon tablespaces where applicable. In Tablespace extended alter screen shot below you can see that now one UNLOAD statement was generated to off-load the data of all tables.

Toad now generates and executed z/OS Runstats statements. This feature is invoked via right-mouse-click context menu and can be used to quickly and easily generate and execute these DB2 Utility statements. You can select z/OS Tablespaces, Tables or Indexes and invoke the Runstats feature. The below shows an example of invoking with Tablespaces. Note that the objects you invoke Runstats with will be selected in the Runstats window.

Clicking on the 'Show Script' shows the generated Runstats statements:

Toad now generates and executed z/OS Rebuild Index statements. This feature is invoked via right-mouse-click context menu and can be used to quickly and easily generate and execute these DB2 Utility statements. You can select z/OS Tablespaces, Tables or Indexes and invoke the Rebuild Index feature. The below shows an example of invoking with Tablespaces.

Clicking on the 'Show Script' shows the generated Rebuild Index statements:

New options for DB2 z/OS Utilities will be used during native and extended alters and Migration script generation. Navigate to those options via Tools | Options | Database | DB2 | z/OS. There are separate tabs where you can now specify Check Data, Runstats, Reorg, Load and Unload options and Dataset Template to use. Several screen shots below provide more details.

REORG statement generation uses the following options. Certain attribute changes, such as tablespace storage attributes, will not take affect until a REORG is executed. In these cases Toad will generate the necessary utility statement regardless of the 'Execute Reorg' option value.

The z/OS Component installation wizard has been modified to now supports WLM environments up to 32 characters in length. This wizard also installs the latest Quest functions and procedures required for the new z/OS Tablespace 'Catalog' tab and to leverage RACF groups within the Toad Security feature.
The Toad Security feature has been updated to identify the RACF groups users belong to. You can now define a role with the RACF group name and Toad will automatically identify if a user is in that group and abide by the Toad Security Roles.
The z/OS Components are required to be installed for supporting the following features:
- The Subsystem - Threads tab
- The Tablespace - Catalog tab
- Dataset Templates
- z/OS Utility execution
The z/OS Components Installer is shipped with the beta. The installer is ZosInstallerWizard.exe and is located in the installed Toad DB2 directory.
- For example: C:\Program Files\Quest Software\Toad for DB2 4.5 Beta\Plugins\DB2\ZosInstallerWizard.exe

For DB2 for LUW Environments Only

From previous Drops

Toad has added a 'Storage unit display value' option that allows you to specify the unit used in Space Management features. To modify this value navigate to Tools | Options | Database | DB2 | LUW | Space Management and set the value as shown below:

The selected storage unit will be used in the Space Management Space Calculator, Space Usage and Space Exception features. An example is shown below:

Toad has introduces support for DB2 LUW v9.5 Roles. You can now easily create, modify, drop and manage privileges for Roles, as shown in the screen shots below:

We continue to roll out additional support for Federated objects. You can now Create, Create Like, Alter and Drop Nicknames. (Note that testing has only occurred on Nicknames on DB2 LUW servers at this point).
You can use the right-click context menu to invoke those actions on nicknames as shown in the below.

On LUW databases supporting federation, 'Function mappings', 'Type mappings', and 'User mappings' now are displayed in the Database browser and information on those objects are displayed on the right-hand-side.
We continue to roll out additional support for Federated objects. On LUW databases supporting federation, 'Function mappings', 'Type mappings', and 'User mappings' now are displayed in the Database browser and information on those objects are displayed on the right-hand-side.

The LUW Database browser tabs have been restructured to better organize Database specific information. There is a new Database tab containing right-hand-side tabs as shown below:

The new Space Usage Tab shows space allocated/used at the database level.

The new Monitor tab shows the current number of applications connected to the database, current locks, Lifetime number of SQL statements, and current Buffer Pool hit ratios.

LUW Database privileges are displayed on the right hand side "Grants" tab and can be edited using the context menu action "Edit Database Privileges" as shown below.

Toad has added support for Creating and Dropping LUW databases. From the Tools menu select the LUW Database Wizard (as shown below) to have the Wizard walk you through the process of creating or dropping a Database.

Toad has introduced a 'Utility File Directory'. Exported data files, created during extended alter, migration and compare scripts will be stored in this directory. Navigate to the Tools | Options | Database | DB2 | LUW | General Utilities tab to view or change this directory.

The extended alter, migration and compare scripts will now use the %DATA_PATH% keyword to qualify import, export and load files. During Toad Editor Script execution the value for the 'Utility File Directory' (above) will be substituted for %DATA_PATH%. The use of %DATA_PATH% also enables scripts to be executed remotely on the Database server. The remote script execution feature has also been introduced in this beta. See the Editor section for more information regarding remote script execution. An example of an extended alter script that contains the %DATA_PATH% variable is shown below.

Toad has introduced support to have Load commands (instead of Import commands) generated in extended alter, migration and compare scripts to re-load table data. Load commands can be more efficient than Import commands when loading large amounts of data. To set this new option, navigate to Tools | Options | Database | DB2 | Advanced Admin and check the 'Use LUW load utility when applicable as shown below.

Toad now has Event Monitor features of Create/Create Like/Alter.

Description columns and fly-over hints were added to the LUW DB/DBM Parameters tabs as shown below.

You can now invoke the Runstats feature with Indexes. Only the indexes you invoke the Runstats feature with are pre-selected, making granular Runstats statement generation quick and easy as shown below.

For LUW Databases supporting Federation, Toad now displays Servers and Wrappers in the Database Browser along with property tabs on the right-hand-side, as shown below. Stay tuned for additional Federated support throughout the Beta Cycle! Note that Toad will only display Federated objects in the database browser if the DB2 instance DBM 'FEDERATED' configuration parameter value is YES.

Data Management

From previous Drops

You can now format XML when editing XML data so you can easily view XML tags, data and hierarchy.

Query Development

This release includes enhancements to the following query development functionality:

ER Diagrammer

Query Builder

Editor

ER Diagrammer

From previous Drops

You can now add manual relationships by dragging one column over to another.

Query Builder

From previous Drops

You can now compare the result set in the Query Builder to a result set of an editor window.

You can now see connection information and a part of the query when you mouse over the Query Builder tab.

For DB2 on LUW there is a new 'Top row count' option in the Query Builder that can be used to easily reduce the size of your result sets as you build and test your queries.

Using the new 'TOP row count' option modifies your query as shown below.

Toad now provides a new Query Builder column sort option that can be used to display Object column names in sorted alphabetic order. Navigate to Tools | Options | Database | Query Builder to view and set that option. See below screen shots for more details.

The results of selection 'Sort columns in diagrams by names' to 'Ascending' is shown below.

Editor

From previous Drops

The Document Recovery feature is now supported when running multiple instances of Toad.

Default Editor Result sets display

Toad has modified the default result set display to show all result sets on a single tab. There is a great performance gain when using this default view.

To display Script results sets on individual tabs (like in previous releases of Toad) go to the Tools | Options | Database | Script Result tab and select "One tab per query" for the "Script Result Grouping", as shown below.

You can now optionally view Dash comments (for example: -- comments) as well as block-style comments (for example: /* test */) in the Navigator as shown below.

Navigate to Tools | Options | Editor | Tools and in the 'Code Navigator' section check the "Block Comment" and "Dash Comment" to show those in the Navigator.

The Editor Messages tab has been modified to make it easier to view messages along with the statement they are associated with.

You can right-click in the Messages tab grid and change the view to 'Text Output' to see the messages in text format as shown below.

Script Restart-ability

Toad now provides you the ability to generate scripts with syncpoints which can be used to restart scripts at certain statements. To enable this new feature go to Tools | Options | Database | DB2 | General and check the "Generate scripts with syncpoint statements" as shown below.

Now when a script is generated, #SYNC statements will be included in the script (see below).

The #SYNC statements are commit points and restart points. If a script fails it can easily be restarted at a syncpoint by clicking the Editor " Restart script at syncpoint" toolbar button. This will display the "Script Restart" dialog with the failing SYNC point pre-filled. See the picture below.

Remote Server side script execution for DB2 on LUW

You can now send a script to an LUW DB2 server platform for Database server side script execution.
On the Editor toolbar, Click the LUW Remote Script Execution button (shown below) to invoke the LUW Remote Script Execution Wizard.

The wizard will display the following pages, walking you through the process of getting your scripts to the remote host.

Note that two files will be sent over to the database server. <Jobname.spf> and <Jobname.sql>. The spf file is a control file that contains information like the database to connect to, and directories for exported data and log files.
Note that remote server-side execution of LUW scripts requires one of the following:
- The Quest Central for DB2 LUW v4.9 or above agent has been installed on that Server
- The Toad DB2 LUW Beta Remote agent has been installed on that Server
To obtain more information on the Toad LUW Remote agents and to download those beta agents see Toad DB2 LUW Beta Remote Agents
Once you have the Remote agent installed and your remote scripts are on the database server, you can telnet to the remote database server and execute the following command: QcExec <jobname.spf> as shown below:

The Log file will contain success/failure messages as shown below.

With the new Toad DB2 LUW Beta Remote agent installed you can modify the QcExec.ini file to target where you want the log files to be placed by specifying a LogPath value.

SQL Scalability testing for DB2 on LUW

The Editor in Toad now provides a launch point to the Quest Benchmark Factory product. Benchmark Factory is a separate Quest Database Scalability Testing Product. Place the cursor on the statement you want to send to Benchmark Factory for SQL Scalability testing and then click the "Test SQL for Scalabilty" button. (You can also highlight and select multiple statements and then click the button to pass in multiple statements). If you have Benchmark Factory installed we will launch nicely into it! See the picture below.

Batch JCL Job execution for DB2 on z/OS scripts

You can now save an Editor script as a Batch JCL Job. You can save the JCL to a PDS or Submit the Job from Toad.
On the Editor toolbar, click the button shown below to invoke the z/OS Remote Script Execution Wizard.

The Wizard displays and walks you through the steps to create and save/submit your JCL Batch Job, as shown in the following screen shots.

Note that z/OS Remote Script Execution requires the Quest z/OS Components to be installed. The Quest z/OS Component Install wizard ships with Toad DB2. After installing Toad DB2, go the the directory where Toad was installed and execute ZosInstallWizard.exe to start the wizard.

Under Construction

This section lists the features that are still under development. You should be aware that these areas are not complete and will be changed in subsequent drops. Check the Beta Release notes during the the Beta Cycle for information on features that have completed their 'construction' phases and become available.
Still under development at this drop:

None at this time

Resolved Issues and Enhancements

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

Resolved Issues and Enhancements in 4.5

Feature	Resolved Issue	Change Request	Beta Drop
View Editor	Column Validation now occurs when creating or altering a view	ST#42965 CR#228913	4.5.0.206
z/OS Utilities	Extended alter and Migration scripts now generate z/OS utilities per tablespace (instead of per table) where applicable	ST#42745 CR#227143	4.5.0.206
Editor	Send to Editor -> As Script will now display the Results tab as the default tab	ST#42939 CR#228649	4.5.0.206
Migration Wizard	Toad is now saving and using the directory settings for migration Scripts/Reports	ST#43113	4.5.0.206
z/OS Component Install	Now supports WLM environment names up to 32 characters in length	ST#53146	4.5.0.206
LUW Database Partition Group - Redistribute	You will obtain a Null Reference exception Error when right click on an LUW Database Partition Group and select Redistribute.	ST#58004	4.5.0.251
Data Compare	Clicking Tools->Compare->Data Compare or right-clicking on a Table and selecting 'Data compare' causes BaseException	ST#58022	4.5.0.251
LUW Tablespace Transfer Ownership	A message box will show an internal message when you select an LUW Tablespace and select 'Transfer Ownership' from the right-click context menu.	ST#58070	4.5.0.251
Options - Job Management	Clicking on Options - Job Management raises a FileLoadException	ST#58017	4.5.0.251
Options - Editor - Formatter Management	Error occurs in Options page "Editor" > "Formatter" raises a DirectoryNotFoundException	ST#58189	4.5.0.251
Tools - Administer - Job Manager	Clicking on Tools - Adminster - Job Manager raises a FileLoadException	ST#58019	4.5.0.251
File \| Open	If you migrate settings from a previous version, then opening a SQL file throws exception	ST#58439	4.5.0.251
Extra SQL Tuning Menu Item	An extra 'SQL Tuning' Menu item is displayed in the Tools \| Quest Tools menu. This should not be display	ST#58145	4.5.0.251
Prompting to save Documents	The save prompt is not being displayed when un-saved documents are closed individually. Please save your documents manually to ensure your changes are kept.	ST#57803	4.5.0.251
LUW Alter Event Monitor	The Alter Event Monitor GUI will generate a DROP and CREATE script when no modifications are made to the event monitor definition.	ST#58007	4.5.0.307
z/OS Subsystem Threads tab	Issue with the 'threads' tab on a v9 z/OS subsystem when there are a lot of active threads	ST#59985	4.5.0.351
z/OS Components	Warning messages are now displayed when the Quest z/OS components are not installed and features requiring those components are invoked.	ST#58377	4.5.0.351
Database Browser	Retain schema in the browser per object types. Now when you switch between object types the schema filter will remain unchanged per object.	ST#57380	4.5.0.351
Database Browser	Ability to list all objects in the database explorer.	ST#57692	4.5.0.351
Table Editor	You can now specify XML column data types for DB2 on z/OS v9	ST#57443	4.5.0.351
Data Grid	For DB2 on z/OS data, blob and for bit data should optionally be viewed as EBCDIC	ST#42077	4.5.0.351
LUW Space Management	Add option to display space information in KB, MB, GB	ST#54869	4.5.0.351
z/OS Table Properties	The Check Pending value should be displayed on the z/OS Table Properties tab	ST#54052	4.5.0.351
z/OS Universal Tablespace	The Create editors for z/OS tables and indexes needs to support Universal Tablespaces for DB2 z/OS v9	ST#56740	4.5.0.351
Stored Procedure Output	Toad does not display the precision and scale when displaying the output of a Stored Procedure call that returns a decimal with precision and scale	ST#59461	4.5.0.351
Exporting Timestamp Values	The Export wizard was not keeping the precision (milliseconds) of exported timestamp column values. Note that all file types now, except Excel, will keep the timestamp precision values when exported.	ST#60104	4.5.0.368
Groups and Users	An error will occur when you attempt to generate a script for a new Group or User.	ST#60294	4.5.0.368
z/OS Index Creation and Runstats	During the creation of an Index, when a lower case index name is entered, the generated RUNSTATS statement will fail because the index name in that statement is escaped.	ST#58504	4.5.0.368
Extract DDL	On a z/OS Version 9 compatibility mode system, Toad will throw an error you will use Extract DDL to create a script.	ST#60739	4.5.0.419
Data Compare	Several issues have been addressed and this is ready for Beta testing.	NA	4.5.0.419
Database Browser	Duplicate 'Dependencies' tabs appear on the right-hand-side for LUW Tablespaces	ST#60674	4.5.0.521
Runstats	When you are creating a Table, a RUNSTATS statement is not being generated, even though the option to have that generated is checked.	ST#60985	4.5.0.602
Extract DDL	With DB2 on z/OS - when you invoke extract DDL and you specify options that will cause the DDL for a Database to be generated, you may see an assertion message box. To get around this for now, please click the 'ignore' button on that box.	ST#62330	4.5.0.602
Compare Object	With DB2 z/OS when you compare several tables on the same subsystem and perform a Schema mapping Toad might indicate that tables are equal when there are some differences.	ST#62119	4.5.0.602
Compare Object	When comparing objects on DB2 z/OS on the same subsystem in different tablespaces and the tablespace name is mapped, the generated sync script may include a drop of the tablespace but not all tables will be of the source tablespace will be recreated.	ST#63259	4.5.0.687
LUW Alter Tablespace	When extended altering an LUW tablespace that only contains empty tables, the generated alter script will not contain the necessary statements to recreate all of the empty tables.	ST#63210	4.5.0.687
Query Builder	Indicators for notes created on relationships in the Query Builder and in ER Diagrammer are not showing.	ST#52943	4.5.0.687
LUW command execution	Toad was automatically binding LUW packages necessary for DB2 Command execution. Toad now will also grant access to those packages so all users with proper DB2 authority may execute DB2 LUW commands within Toad.	CL#729796, ST#42690, ST#64055	4.5.0.722
Version Control	This CR applies only if you are using version control. The incorrect source may be checked into version control when you alter an objects and send the alter script to the SQL Editor and execute it in the SQL Editor.	ST#64052	4.5.0.722
Database Browser Notes	Currently, no option exists that allows the user to remove notes on objects in the Database Explorer.	ST#52941	4.5.0.722

Known Issues

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

Feature	Known Issue	Defect ID
LUW Nicknames	Toad supports scripting, creation and alteration of Nicknames that are based on DRDA type wrappers only in this release.	N/A
Tools Knowledge Xpert	The Tools \| Quest Tools \| Knowledge Xpert feature is not available.	N/A
General	Customized options selected in the Configuration wizard are not applied if you are running as a Restricted user.	CR#216699
	(DB2 for z/OS) Toad has issues when handling LOBs. These issues can occur, for example, when you attempt to migrate auxiliary tablespaces, preserve LOB data in advanced alters, or generate DDL for base table dependencies.	ST#53,640
	As a security measure in Windows Vista, when a standard user belonging to an Administrators group launches a process and the Vista User Access Control security feature is enabled, the process launches with only standard user privileges. However, under these restricted privileges, Toad can have problems cataloging DB2 systems (including transferring a DB2 catalog at Toad setup) and running utilities through CLP, thus affecting advanced alters and other Toad functionality. Additionally, this user does not have write access to the Toad default storage folder (the Toad installation folder) where files, such a the license key file and export profiles generated in the Client Configuration wizard, are stored when no explicit path is specified. Instead, Vista automatically copies files to C:\Users\db2admin\AppData\Local\Virtual Store\Program Files\Quest Software\Toad for DB2 version. The Toad user can have the following issues: When the user attempts to launch Toad again, Toad cannot find the license key file. The user might not know where to find the export profiles since they are stored in an unexpected location. Workaround: When launching Toad as standard user belonging to an Administrators group, right-click the Toad icon on the Vista desktop and select Run as administrator.	N/A
	Toad DB2 4.0 installs a db2cli.ini file, which is set to have connections connect to the catalog node. If you need to change this node specification for any reason, use the following steps to edit the file: Locate db2cli.ini in the DB2 Client folder in your Toad installation folder. (The default installation location for the file is C:\Program Files\Quest Software\Toad for DB2 4.0\DB2 Client.) Open the file and do one of the following. In the section labeled [COMMON], edit the following line with the correct node specification: ConnectNode=SQL_CONN_CATALOG_NODE or Comment out the line by placing a semi-colon at the beginning of the line: ;ConnectNode=SQL_CONN_CATALOG_NODE	ST#53,860
Installation/ Upgrade	If a Vista standard user belonging to an Administrators group attempts to uninstall Toad when the Vista User Access Control security feature is enabled, the uninstall might hang. Workaround: Turn off the User Access Control security feature and then uninstall.	ST#52,914
	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
	Network and LAN installations are currently not supported.	N/A
Advanced ALTER
Advanced ALTER	(DB2 for z/OS only) When you alter a table to reduce the size of a column referenced in other tables via RI, the LOAD phase in the advanced ALTER fails with a DSNU334I INPUT FIELD INVALID error. The load cards show the original column length.	ST#44,753
Connection Manager
	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 to execute code.	CR#166752 Case#408845
	If Toad is running on a Vista machine that does not have another DB2 client installed, problems might occur when you use the Connection Manager to catalog databases. After you specify the connection information for a database, its catalog information does not display on the Client Configuration wizard Results window. Consequently, Toad cannot connect to the database. Workaround: Use either method: Use the Client Configuration wizard to import connections. Right-click the Toad for DB2 icon on your desktop, and select Run as. On the Run As window, select The following user and specify an administrator in the User name field. This workaround should enable you to use the Add Catalog Entry feature in the Client Configuration wizard to catalog databases.	ST#42,813 CR#227752
Data Reports	Currently, you cannot create a Label Report in the Toad Data Report wizard.	ST#42,133 CR#215945
Database Explorer/Object Explorer
Database Explorer/Object Explorer	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 CR#220757
Debugger	Currently, the debugger does not support Unicode schema names.	ST#41,770 CR#184638
Editor
	The following object types are not found when using the View Object at Cursor feature: Triggers Procedures Functions Users Hosts	ST#41,627 CR#164917
	When you edit a script in Toad, you must delimit SQL identifiers that begin with @ to differentiate these identifiers from named parameters. For more information, refer to the following IBM documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.dndp.doc/htm/frlrfIBMDataDB2DB2CommandClassCommandTextTopic.htm	CR#224375 Case#552946
Export Data (Toad core feature)	Binary data types cannot be exported in this release.	ST#41,665 CR#170430 Case#419715
Export Data (Toad core feature)	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.	ST#41,935 CR#203483 Case#483802
Help in Toad	The help does not state the DB2 restriction that you cannot drop packages containing triggers	N/A
Schema Compare
	(DB2 for 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
	(DB2 for z/OS only) A comparison of materialized query tables generates an "undefined name" error. You may use the new Object Comparison feature instead.	ST#42,913 CR#228511
	Synchronization script does not create tablespaces on target. You may use the new Object Comparison feature instead.	ST#41,983 CR#210132 Case#491910
Version Control
	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."	ST#42,093 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.	ST#42,184 CR#217475
	You currently cannot check object list definitions into version control.	ST#42,188 CR#217524
	(CVS only) Each version control configuration should point to a unique Root Folder location on the Source Repository to avoid conflicting file usage.	CR#228422
	(CVS only) You might receive an "Unknown Error..." message when using the sspi protocol to connect to a CVSNT server. Possible Workaround: Include "user@" in the Provider Information Server field. Information in the Server field should use the following format: :sspi:user@server:/cvsrepository	CR#226256
	(CVS only) You cannot successfully configure CVS using the SSH protocol. Workaround: If the CVS binary is not accessible from the user's SSH home directory, set the CVS_SERVER environment variable on the client to enable the Unix shell account to access the CVS binary: CVS_SERVER=CVSbinaryPath where /CVSbinaryPath is your path for the CVS binary. (To display the list of environment variables to edit, right-click My Computer, and select Properties. From the System Properties window, select the Advanced tab, and click Environment Variables.) Run the client from a command prompt so that the user's password for the server gets cached. (You cannot enter the password within Toad.) cvs -d ":ssh:user@server:repositoryPath" login where repositoryPath is your path to the CVS repository. Start Toad for DB2, and configure CVS (through the Options window), entering :ssh:user@server:repositoryPath as the server string in the Server field. Log in to CVS.	CR#228718

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	The processing of the snapshot queries to generate the script in the RHS script tab for an LUW Database Server on AIX 5.2/DB2 might cause an instance crash. Opened IBM PMR 48277,756,000. IBM APAR: IY79365 addresses this.	N/A
	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
	(DB2 for LUW only) Certain Toad functions use the DB2 snapshot monitor to capture information about containers used in a database. To capture this information in 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.	N/A
Installation/ Upgrade	You cannot install DB2 for LUW 8 on the same system that already has Toad for DB2 4.5 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
Installation/ Upgrade	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 Explorer/ Object Explorer	(DB2 for z/OS only) There is a known z/OS issue when attempting to ALTER partitioning index values for PRIQTY and SECQTY. If these values are changed in Toad, the subsequent ALTER statement is generated without ENDING AT values for the partition keys. The generated syntax is correct; however a database error will occur. IBM has issued z/OS APAR PK69271 to address the issue.	ST#49,829
	(DB2 for 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
	(DB2 for 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
	(DB2 for 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 unusable data. 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	Database Explorer Data grid is read-only for DB2 tables which have a Primary Key column of data type REAL. Toad calls the IBM GetUpdateCommand and that is throwing an exception, but according to IBM doc this functionality should be supported. IBM PMR 49796 opened.	ST#51,685
	Attempting to update a table column value that is not generated causes an error when another column in the table is defined as GENERATED ALWAYS. This issue is related to the DB2 9.5 APAR JR30189, which IBM expects to fix in a future 9.5 fixpak.	ST#51,035
	(DB2 for 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: Click the Filter Data icon in the data grid. Select the SQL tab. Select the Enable custom SQL checkbox. 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
	(DB2 for LUW only) 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
	(DB2 for z/OS only) 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
Editor	Dropping a nickname does not drop its primary key. This issue (PMR 30432,756,000) was fixed in DB2 9.1 Fixpak 3.	ST#42,503 CR#223155
Export Data (Toad core feature)	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
Schema Compare	(DB2 for LUW only) You cannot synchronize schemas if the Code Pages on the compared schemas do not match.	CR#141383
Space Management	(DB2 for LUW only) APAR IY90197 states: RUNNING SNAPSHOT TABLE FUNCTIONS CAN CORRUPT MEMORY INSIDE THE DB2FMP (C) PROCESS DUE TO STACK OVERFLOW. This issue was fixed in DB2 8.1 Fixpak 14.	N/A

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.

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

Platform	1 GHz minimum
Memory	512 MB of RAM minimum, 1 GB 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	185 MB of disk space required to run Toad If installing the Toad SQL Tuning for DB2 z/OS component, allocate an additional 45 MB. If installing the Quest SQL Optimizer for DB2 LUW, refer to the Release Notes for that product for disk space requirements.
Operating System	Any of the following: Windows XP Professional (32-bit only) Windows 2003 (32-bit only) Windows Vista (tested on 32-bit Ultimate edition with XP Graphics)
Additional Software	.NET Framework Microsoft .NET Framework 3.5 SP1 or later Note: Consider the following: 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 Note: Toad installs a DB2 v9.5 client as part of the installation process. The DB2 v9.5 client can co-exist with an existing DB2 v8 client; however, it is incompatible with a DB2 v7 client. If a DB2 v7 client is already installed on the system, the Toad installation stops and cannot complete. You must upgrade to the DB2 8 client and restart the Toad installation to avoid losing functionality in some DB2 native tools. PDF Viewer Adobe^® Acrobat^® Reader 7.0 or later (for viewing the Toad for DB2 Installation 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 for z/OS 8.1 or later

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

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

Note: To run RUNSTATS and the native REORG utility on tablespaces and indexes, Toad supports version 8.2.2 or later.

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, 6.1
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

Operating Systems Supported by the Toad LUW Agent (for the new optional remote server side script execution)

Microsoft Windows 2000, 2003, or XP
Sun Solaris 7 or later
IBM AIX 4.3 or later
SuSE Linux Enterprise Server 8 and 9 for zLinux
SuSE Linux Enterprise Server 8 and 9 United Linux for Intel x86
SuSE Linux 9 (2.6 Kernel) on AMD64 (x86_64)
RedHat Enterprise Linux AS 3.0 and 4.0 zLinux (31-bit)
RedHat Enterprise Linux AS 2.1, 3.0, and 4.0 for Intel x86
RedHat Enterprise Linux AS 4.0 (2.6 Kernel) on AMD64 (x86_64)

Note: You must install the compat-libstdc++-7.3-2.96.122.i386.rpm compatibility library. You will find this package on the RedHat Advanced Server 3.0 installation CDs.

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:

Select Control Panel from the Windows Start menu.

Double-click Administrative Tools.

Double-click Microsoft .NET Framework 2.0 Configuration.

Select My Computer, and then select the Runtime Security Policy node.

Select Evaluate Assembly from the list of tasks in the right panel and browse to the location of Toad.exe in the File field.

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

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.
Type the following command to enable LDAP support:

db2set DB2_ENABLE_LDAP=YES

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.

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

Supported Provider	Server Version Tested	Client Version Tested
Visual SourceSafe (VSS)	VSS 6.0d	VSS 6.0d
Concurrent Versions System (CVS)	CVS 1.11.22 on Solaris CVSNT 2.5.03 on Windows	CVNT 2.5.03
Subversion	Subversion 1.4.2	Subversion 1.4.2
Team Foundation Server (TFS)	TFS 2005	Visual Studio 2005 Team Foundation Server MSSCCI Provider

Toad 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

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.

Provider	Prerequisite
VSS	VSS client
CVS	CVS client
Subversion	Subversion binary package Note: When configuring version control in Toad, specify the binary path in the BinaryPath field on the Command Based Version Control Properties page in Toad. Do not include the executable file name in the path.
TFS	Visual Studio Team Foundation Server MSSCCI Provider client Notes: This is not the same client that you install with Visual Studio. See Version Control for information about downloading this client. You must specify the workspace name for the provider in the Team Foundation Server Properties window in Toad.

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.

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.

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:

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

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:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

www.quest.com

Email: legal@quest.com

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.

Component	License or Acknowledgement
EDraw Office View 5.3	Copyright © 2008, EDrawSoft
IBM DB2 Client Merge Modules Version 9	CONTAINS Runtime Modules of IBM DB2 Runtime Client Merge Modules Version 9; Copyright IBM Corporation 2006 All Rights Reserved
SharpZipLib 0.84	SharpZipLib License

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.