I have legitimate copies of Visual Studio 2008 installed on several computers, each with different license keys. I cannot remember what key was used on each install.

• Autodesk License File Location

Where in the registry can I find what license key was used for that PC's Visual Studio 2008 installation?

If you need to provide the same Toad functionality to all users, you can enter the default license key for all users. Upgrade Toad. To upgrade Toad. Run the ToadInstaller.exe installation program from the DVD or downloaded file. Select Uninstall Toad and continue with install. Complete the wizard. Each installation of Toad requires an authorized license key to. Completely different, or in a completely different folder than what you thought. I've used ProcessMonitor to validate that TOAD is locating and parsing the file, but I'm still prompted to enter the key at first launch. I'm installing the extracted.msi files via.bat file, and they all appear to work. Has anyone used the ProductLicenses.xml to silently license TOAD?

I would imagine that it is in the registry somewhere.

5 Answers

just run your computer and then type the word 'regedit'you'll find the four basic HKLM but i thin k just use this :

HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio9.0Registration2000.0x0000PIDKEY on my PC. not sure but just try because some of this working.

If you are using Win7, then try HKLMSoftwareWow6432NodeMicrosoftVisualStudio9.0Registration2000.0x0000PIDKEY

A couple of options listed here:

Magical Jelly is the best product key finder for Windows. It’s free and portable, hence you can use it without installation or modifying the Windows registry. It can be used to extract the product keys of paid software like Microsoft Office, Microsoft Visual Studio, Adobe Photoshop etc.

and

WinkeyFinder is another great program to find the CD keys of installed software as well as the operating system. You can use this program to

• Find product keys of Windows XP, Vista, Windows 2003, Windows 98 and Windows ME editions
• Find serial keys of Microsoft Office 2000, 2003 and Microsoft 2007.
• Change or copy the volume serial number.
• View .NET key.

You could try ProduKey from NirSoft. Its an app for listing Microsoft licence keys, however I don't think it'll work if your copy of Visual Studio was pre-pidded, i.e. it came from say an MSDN account.

If you go into regedit and browse to the following path: HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio9.0Registration.

The Product Key can be found in the ProductID Registry Key.

Hope that helps!

I've had positive experiences with Belarc Advisor http://www.belarc.com/Programs/advisor.exe. It gives out a neat list of software installed on your pc with Keys and I generally archive this on a secure cloud so even if My pc crashes, I can still get a registered copy of all the software installed.

Today its even possible to have the entire image of your installation archived so that You get a clean PC with the set of licenses refreshed on installed anytime you want one!

Not the answer you're looking for? Browse other questions tagged windows-registryvisual-studio-2008license-key or ask your own question.

Toad^® for IBM DB2

Version 4.5.2

Release Notes

November 2009

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.

Toad for DB2 4.5.2 is a maintenance release containing primarily internal fixes and enhancements to the previous 4.5 and 4.5.1 releases.

• For a description of customer issues resolved in this release, see Resolved Issues and Enhancements in 4.5.2.
• For a review of customer issues resolved in Toad for DB2 4.5.1, see Resolved Issues and Enhancements in 4.5.1.
• For a description of the new features and updates in Toad for DB2 4.5, see Features and Updates in Toad for DB2 4.5.

Click to review the updates and new features in the following areas:

Prerequisites and Installation

• Toad now requires .NET Framework 3.5 (Service Pack 1) or later. You can download the latest .NET Framework from this location: http://www.microsoft.com/Net/Download.aspx

• Because of the new .Net Framework 3.5 (Service Pack 1) requirement, Toad can no longer be installed on Windows 2000 systems. However, Toad can still connect and manage databases running on Windows 2000 systems.

• Toad ships and installs IBM DB2 for LUW Client 9.5 as the DB2 client. The new default location for the DB2 client is C:Program Files Toad for DB2 4.5SQLLIB.

• To provide an easier installation for Citrix environments, the default location for settings files has been changed to the following: C:Documents and SettingsUsernameApplication DataQuest SoftwareToad for DB2 4.5.

Connections

The Connection Manager and the Connections window provide more functionality to help you manage DB2 connections:

• A new tree view option displays your connections in a hierarchical tree for easy system identification.

• You can import local DB2 catalogs to the client to keep your cataloged connections synchronized with your DB2 environment.

• You can import all connections currently defined on the DB2 client.

• The System property for a connection profile on the Connections and Create New Connection windows now identifies the TCP/IP port number and operation system platform for a DB2 connection.

General Toad Environment and Functionality

• Optimized start-up code results in faster start-up times, especially for 'warm restarts.'

• Code optimization and a reduction in the number of assemblies loaded has reduced Toad's memory footprint.

• Toad offers new skins, such as Office 2007 and a default skin that more closely matches the standard Windows look-and-feel.

• You must now click the tab of a pinned window or pane to display it. This enhancement eliminates the unwanted expansion of a pinned item when you accidentally mouse over its tab:

• Document recovery now recovers any ER Diagram or Query Builder files to avoid losing your work. When you restart after an unexpected close, Toad checks the timestamp on the backup file against the original file, and opens the file that has the latest timestamp. The document recovery option is located in Tools Options Environment General.

• You can use the new File Transfer Protocol (FTP) utility to transfer scripts, reports, or other files from Toad. Toad supports unsecured (FTP) and secure (SFTP) file transfers. To open this utility, select View FTP Connections from the menu.

Windows 7 ultimate free download full version 32 bit with crack. After creating a connection, the following window displays:

You can also add an FTP connection to the Project Manager or an Automation script.

• Toad Security lets you identify a RACF, Unix, or Linux group as a Toad role. Toad automatically enforces the role's restrictions on each user that belongs to the specified group. This feature is available for the following:

  • DB2 for LUW 9 or later databases

  • DB2 for z/OS 8 or later subsystems

  • All for DB2 licenses except for the DBA license

Note: You must have the Quest IBM DB2 z/OS Component 4.5 installed on the DB2 subsystems that use the RACF group.

• Connection information for each Editor, Query Builder, or other document window is now available by selecting the Show connection info on document tabs checkbox under Tools Options Environment General.

• You can close the current tab in a window or all other tabs except the current one from the right-click menu.

• You can no longer rename document tabs in the Toad environment.

• Knowledge Xpert has been removed from Toad.

Automation

• Most activities now include support for variables. Variables are a powerful feature that allow you to change data in your script or use a dataset collected from an activity in the automation script. For example, you can use variables to perform the following tasks:

  • Send an email to a group of people where the list of recipients is automatically selected with a query

  • Generate repetitive reports where only the product number, date, region, or any other single element changes

  • Customize file names by including a variable in the file name or automatically including the date that the automation script ran

  • Find content in a file and replace it with the value of a variable

See the Use Variables in Automation help topic for more information.

• Automation now supports Find and Replace and FTP file activities.

• Automation supports new system activities, including program execution, defining variables, and setting up If and While conditions and loop datasets.

• The Select to File activity now supports Excel options.

Database Administration

Click a category in the list to view the features and updates for this release:

Object Explorer

• Toad offers the new Flat Tree view in which to display the object list in the Object or Database Explorer. (This view is similar to the view used to display the object list in Quest Central for DB2.)

• Toad has introduced the Separate schema or database by type option in Tools Options Explorer General. When you enable this option, you can set the schema filter to a different value for each object type in a specific DB2 database or subsystem. Toad then retains the schema settings as you move between the different object nodes. Additionally, these schemas are still in effect when you return to the database or subsystem.

Note: This option does not apply when the Treelist or Flat Tree view is in effect.

• If you specify an asterisk for the Default schema/auth ID property in the profile for a specific connection, all objects for an object type initially display as you move between object nodes in the Object or Database Explorer for that connection.

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

• You can hide object toolbars and use right-click menus instead to access object-management actions. To hide or re-instate the toolbars, toggle the Show Toolbar option.

Object Management - General

• The Create menu has been removed because it duplicated functionality in the File menu. To create objects from a menu, select File New object_type.

• Code completion is now available when using object editors for views and MQ tables.

• When you are editing objects in the Alter window or sending ALTER statements to the Editor, Toad now uses data directly from the database instead of using the cache.

• Advanced alter scripts now preserve identity columns.

• You can view, grant, or revoke privileges at the column level for DB2 for LUW and DB2 for z/OS tables. The Grants tab on the right side of the Database or Object Explorer shows current column privileges for the selected table.

  The Edit Table Privileges or the Edit User (or Role or Group) Privileges functions let you grant or revoke column privileges for users on a table.

• You can now grant or revoke permissions on a given object for multiple users, groups, or roles. In the Alter object Permissions window, select the multiple grantees, right-click the column heading for the permission type, and select the action.

• The new Extract DDL feature generates the DDL script for existing objects and their dependencies. To open this feature, right-click one or more objects, and select Extract DDL.

Object Management - DB2 for LUW

• Toad introduces support for DB2 9.5 roles. The new Roles node in the Database or Object Explorer lets you browse current roles, as well as create, alter, drop, or assign privileges to roles.

• Toad now provides object editors to bind and rebind DB2 for LUW packages.

• You can now create, alter, or drop nicknames on federated DB2 for LUW databases.

• You can now browse the columns and data for aliases in the Database or Object Explorer, as well as right-click and select Generate SQL to generate SQL statements based on the alias DDL.

• Toad provides enhanced support for federated objects. You can now browse, create, alter, or drop nicknames, servers, or wrappers defined on your currently connected database (as long as the database manager configuration parameter FEDERATED is set to YES for the database). You can also browse user, function, and type mappings defined on your federated database.

• The enhanced Database node in the Database or Object Explorer provides the following features:

  • Applications tab (formerly a separate node in the Database or Object Explorer) showing information about the applications currently connected to the database

  • Connection tab showing the connection profile for the database

  • Utilities tab (formerly a separate node in the Database or Object Explorer) showing information about the DB2 utilities currently running on the database

  • Space Usage tab displaying space allocation and usage information for the database

  • Monitor tab graphing the number of current locks held and applications connected, the lifetime number of SQL statements executed, and current bufferpool hit rates

  • Grants tab listing current privileges on the database

• Toad introduces the LUW Database wizard to create or drop databases.

• Previous releases provided functionality to start or stop even monitors. This release provides an object editor to create or alter event monitors:

• The Parameters node in the Database or Object Explorer now includes mouse-over hints and a Description column to provide information about each DB2 database or database manager configuration parameter.

Object Management - DB2 for z/OS

• You can now browse the columns and data for synonyms or aliases in the Database or Object Explorer, as well as right-click and select Generate SQL to generate SQL statements based on the synonym or alias DDL.

• The Properties tab for the Tables node in the Database or Object Explorer shows the check-pending status for a table:

• Toad now supports the XML data type in tables.

• The Tablespaces node in the Database or Object Explorer now contains a Datasets tab on the right side, showing dataset, volume, and space information for a given tablespace.

  Note: You must have the Quest IBM DB2 z/OS Component 4.5 installed on the DB2 subsystem to view this tab.

• When altering a table, you can now add a tablespace partition. The generated script drops both the tablespace and table and re-creates them with the new partition added.

• Toad provides an easy-to-use interface to execute the DB2 DISPLAY, START, and STOP commands.

Note: You must have the Quest IBM DB2 z/OS Component 4.5 installed on the DB2 subsystem to run these commands in Toad.

• The Threads node in the Database or Object Explorer in previous versions has become the Threads tab on the right side of the new Subsystem node.

  Note: You must have the Quest IBM DB2 z/OS Component 4.5 installed on the DB2 subsystem to view this tab.

• The new Subsystem node shows connection profile information for the currently connected DB2 subsystem and information about the threads it is handling. (See the previous figure.)

• Toadsupports the management of DB2 for z/OS 9 universal tablespaces.

Object Migration

Enhancements to the Object Migration feature include the following:

• To avoid the overhead of filtering objects for migration, you now invoke the Migration wizard from only the right-click menu for the objects you have selected. (Access to the feature is no longer available from the Tools menu.)

• The Object Migration feature generates a migration script only. It no longer compares and synchronizes source and target objects. (The new Object Compare feature does this.) However, before the wizard generates the migration script, it detects and lists as conflicts those objects that already exist on the target. You can continue to generate the script or go back in the wizard to define transformation rules to resolve the conflicts.

• The reworked Include DROP statements option inserts DROP statements before the CREATE statements for the migrated objects in the migration script.

• When enabled, the new Process multiple object levels option analyzes and migrates all dependent levels of the selected objects. If the option is disabled, Object Migration analyzes and processes only one level of dependencies.

Object Compare

The new Object Compare feature compares source objects with objects on the target and generates a script that synchronizes the target objects with the source. The script creates objects missing on the target or alters existing target objects to be like the source objects. To launch Object Compare, right-click one or more source objects, and select Compare Object.

Object Compare features include the following:

• Options to compare and synchronize dependencies, preserve data (including identity column data) on existing objects, migrate source data and objects statistics, and execute RUNSTATS:

• Ability to customize synchronization options for individual objects:

• Identification of potential conflicts before script generation:

• Definition of transformation rules to resolve conflicts before script generation:

Utility Execution - DB2 for LUW

• Toad provides object editors to bind and rebind packages.

• The new Utility File Directory option in Tools Options Database DB2 LUW General Utilities identifies the directory path that stores exported-data files created during advanced alters, object migrations, and Object Compare synchronization. The scripts for these processes insert the %DATA_PATH% variable to qualify the import, export, and load files. During script generation, Toad then replaces this variable with the path specified for the Utility File Directory option. The following picture is an example of an advanced alter script that contains the %DATA_PATH% variable.

Note: The %DATA_PATH% variable enables you to use the new Remote Script Execution feature, which executes remote scripts on database servers. See the Editor section for more information about this feature.

• Toad now uses the LOAD command to preserve data during advanced alters, object migrations, and Object Compare synchronization. This command is often more efficient than the IMPORT command for loading large amounts of data in re-created tables. To specify that Toad use the LOAD command whenever possible to preserve data, select the Use LUW load utility when applicable option in Tools Options Database DB2 Advanced Admin.

• Toad now generates and executes DB2 RUNSTATS statements for indexes. Right-click one or more indexes, and select Utilities Runstats.

Utility Execution - DB2 for z/OS

Note: Many of the following new features require that you have the Quest IBM DB2 z/OS Component 4.5 installed on the DB2 subsystem. See the Quest IBM DB2 z/OS Component Installation Guide for more information.

• Toadships with a set of dataset templates that it uses during utility script generation. Additionally, Toad provides an object editor that enables you to edit these templates or create and alter your own. You can browse the and user-defined templates on the new Dataset Templates node in the Database or Object Explorer.

• Toad now leverages IBM DB2 parallel processing during UNLOAD, LOAD, and REORG utility execution on partitioned objects during database administration tasks.

• Toad generates and executes DB2 REORG utility statements on tablespaces or indexes. Right-click the objects, and select Utilities Reorg.

• Toad generates and executes DB2 RUNSTATS utility statements for tablespaces, tables, or indexes. Right-click the objects, and select Utilities Runstats.

• Toad generates and executes REBUILD INDEX utility statements on tablespaces, tables, or indexes. Right-click the objects, and select Utilities Rebuild Index.

• Advanced alter, object migration, and Object Compare synchronization scripts now execute utilities at the tablespace level when applicable, instead of on individual tables in the tablespace. For example, the following advanced alter script uses a single UNLOAD statement to offload data from all tables in the tablespace, instead of a separate UNLOAD statement for each table.

• Toad provides an option to insert a COPY statement before each REORG statement in scripts generated for ALTER, object migration, or Object Compare synchronization. This option ensures that a copy of the original data is available for recovery purposes.

• New options for executing DB2 utilities during regular and advanced alters, object migration, and Object Compare synchronization are now available in Tools Options Database DB2 z/OS.

Quest IBM DB2 z/OS Component

The Quest IBM DB2 z/OS Component 4.5 contains updates that many of the new Toad features require to manage your DB2 for z/OS subsystems.

• A message now displays when you attempt to perform a database administration function that requires the Quest IBM DB2 z/OS Component, explaining that you need to install the component.

• The installation wizard for the z/OS component now supports WLM environment names up to 32 characters.

• The z/OS component includes the functions and procedures required to display the new Datasets tab for tablespaces in the Database and Object Explorer and to leverage RACF groups in Toad Security.

Master Detail Browser

When sending tables or views to the Master Detail Browser, Toad now automatically selects all columns.

Space Management

A new option lets you specify the unit of storage used to display statistics in Space Management features. You can find this option in Tools Options Database DB2 LUW Space Management.

Data Management

Click a category in the list to view the features and updates for this release:

General

• Toad is now Federal Desktop Core Configuration (FDCC) Compliant; however changes to the architecture to ensure compliance will result in a loss of existing data filters when upgrading to this release.

• Hexadecimal values of up to 255 bytes for binary data now display in the grid.

• You can now copy and paste rows in the grid.

• You can now create pivot grids and charts directly from the results by selecting the Pivot & Chart tab.

• You can now format XML data.

• You can now view BLOB and For Bit data in EBCDIC.

• You can add a total value to a column of data or can add a subtotal value to grouped data if the Summary Footer Panel is displayed (right-click the data and select Show Summary Footer Panel). To add a total value, right-click the data and select one of the following options:

• If you have grouped columns using the Grouping panel (right-click and select Show Grouping Panel), you can add a subtotal value to grouped records:

Export Wizard

• You can now export data to Microsoft Access files.

• When you export to an Excel Instance only, columns are automatically resized to the width of the data.

• You can now create a new table and tablespace within a database when exporting data.

• The Export wizard now supports binary data types.

Data Compare

• You can right-click tables or views in the Object Explorer and select Compare Data to compare data within the context of the current connection and database.

• When comparing data, you can now auto-map target columns for selected source tables.

• When you select a record, Data Compare displays a side-by-side comparison of the values of the source and target row automatically in the Row Viewer tab.

• When you synchronize a script, Data Compare now opens a script using an existing connection.

Query Development

Click a category in the list to view the features and updates for this release:

Query Builder

• When you mouse over a Query Builder tab, Toad shows connection information and part of the query you are building to help you identify your Query Builder instance.

• You can now sort columns alphabetically in the Diagram pane by selecting an option from the Sort columns in diagram by name drop-down list in Tools Options Database Query Builder.

• You can now create a view in the Query Builder.

• When you save a Query Builder file, Toad prompts you to save query results with that file.

• You can now add an INTERSECT, INTERSECT ALL, EXCEPT, EXCEPT ALL, UNION, or UNION ALL operator to queries.

• For DB2 on LUW, a new Top row count option in the Query Builder lets you limit the number of rows returned. Use this option to reduce the size of your result sets as you build and test your queries.

• You can use the right-click menu to compare results from a Query Builder query to data from the Database Browser window or the Editor Results pane.

Editor

• Messages now show the SQL with which they are associated for better identification of the result or issue.

• You can now view messages in text format. Right-click in the message pane, and select Text Output.

• Toad provides the ability to restart scripts at syncpoints. To enable script generation with syncpoints, select Generate scripts with syncpoint statements in Tools Options Database DB2 General. To restart a script at a syncpoint, click in the Editor toolbar.

• Toad has modified the default Result Sets layout to show result sets for multiple queries on a single Set x tab, greatly improving performance.

  To display script result sets on individual tabs (as in previous releases of Toad), go to the Tools Options Database Script Result, and select One tab per query in the Script Result Grouping section.

• After a group execution, instead of viewing individual result sets for the different connections, you can view the retrieved records for multiple connections in a single list on the Result Sets tab. Simply select a level in the Group Execute tree that is higher than the individual connections you selected for group execution (for example, select the DB2 or host level). The retrieved rows for all connections under that level display on the Result Sets tab, with each record showing to which connection it belongs.

• You can now optionally view dash comments (for example, -- comment text --) as well as block-style comments (for example, /* comment text */) in the Navigator.

  
  

  To enable this feature, navigate to Tools Options Editor Tools, and select Block Comment and Dash Comment in the Code Navigator section.

• Toad provides a new facility that transfers scripts to remote DB2 for LUW servers for execution. To invoke this facility, first open a script in the Editor. Then click to open the LUW Remote Script Execution wizard, which transfers the script and required control information to the remote server. You can then telnet the remote server and execute the script. Additionally, you have the option to change the location of the log files that the remote script execution generates.

  Note: The Remote Script Execution feature requires that Toad for DB2 Agent 5.1 be installed on the remote server to which you are transferring the script. (For information about installing this agent, see the Toad for DB2 LUW Agent Installation Guide, located in your Toad for DB2 client directory.)

• Toad provides a new facility that transfers scripts from the Editor to remote z/OS systems for execution. To invoke this facility, first open the script in the Editor. Then click to open the z/OS Remote Script Execution wizard, which transfers the script to the mainframe and submits it as a JCL job that runs against the specified DB2 for z/OS subsystem. Optionally, you can save the script to a PDS.

Note: This feature requires that the Quest IBM DB2 z/OS Component 4.5 be installed on the subsystem against which you are executing the script. See the Quest IBM DB2 z/OS Component Installation Guide, located in your for DB2 client installation directory, for more information.

• The Editor provides a launch point to Quest Benchmark Factory. This product lets you test the scalability of your SQL in the connected database.

• You can now drag and drop an SQL file onto the toolbar to automatically open an Editor session containing the contents of the file.

• You can share Formatter settings for your team in a network share folder in Tools Options Editor Formatter to ensure consistent coding standards.

SQL Recall

• Toad supports deleting multiple statements in the SQL Recall window.

• SQL Recall now logs only single statements.

Debugger

You can right-click a breakpoint in the Editor to edit its properties.

SQL Analysis and Optimization

• Toad SQL Analysis for DB2 LUW is now available for tracking and analyzing SQL statements captured in SQL collections that you define and manage. You can view SQL statistics and trends at the workload level or at the individual statement level and send bad-performing SQL to the Quest SQL Optimizer for tuning.

Note:

• Toad SQL Analysis is accessible only through your Toad session; it is not a stand-alone product.

• SQL Analysis requires that the Toad for DB2 Agent be installed on each DB2 for LUW instance on which you are running SQL collections. See the Toad for DB2 LUW Agent Installation Guide for more information.

• You can now open a Quest SQL Optimizer for DB2 LUW session on the SQL in a view, MQ table, or trigger definition. (Previously you could open a session on only the SQL used in packages or in Editor scripts.)

• You can now open a SQL Tuning for DB2 z/OS session on the SQL in a view, MQ table, or trigger definition. (Previously you could open a session only on the SQL used in packages or plans or in Editor scripts.)

• You can now invoke SQL Tuning for DB2 z/OS on multiple SQL statements, including the statements that you select in a package or plan or in an Editor script. Each statement opens a separate scenario in the SQL Tuning session.

Project Management

Support for FTP connections, SQL Recall named SQL statements, and Database connections has been added to the Project Manager via the right-click menu. For Database connections, only databases that are currently connected can be added to the Project Manager.

Version Control

• Toad now supports TFS 2008.

• When configuring TFS, you can now specify a user name and password, instead of using your Windows credentials, to log into TFS.

• This release shows improved performance during the working-directory initialization and in the overall handling of the root folder and working directory.

• Toad now supports multiple version-control configurations that are active simultaneously.

• When you manage version-controlled SQL scripts from the Object Explorer, creating a script opens a new Editor.

Click the following links to view issues addressed and enhancements implemented in the Toad for DB2 4.5.x releases, including this latest release 4.5.2:

Resolved Issues and Enhancements in 4.5.2

The following is a list of issues addressed and enhancements implemented in the current release:

Resolved Issues and Enhancements in 4.5.1

The following is a list of issues addressed and enhancements implemented in the current release:

Resolved Issues and Enhancements in 4.5

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

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

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

Upgrade Toad for DB2

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.

Upgrade the Quest IBM DB2 z/OS Component

An upgrade to the Quest IBM DB2 z/OS component is available with Toad for DB2 4.5.2. To ensure you have the latest z/OS component upgrade on a DB2 subsystem, do one of the following:

• If neither the Quest Central for DB2 mainframe component nor the Quest IBM DB2 z/OS component resides on the DB2 subsystem, perform a complete installation of the Toad IBM DB2 z/OS component available with Toad for DB2 4.5.2. See the Toad IBM DB2 z/OS Installation Guide for more information.

• If the Quest Central for DB2 mainframe component or a pre-4.5.0 Quest IBM DB2 z/OS component resides on the DB2 subsystem, perform the following two-part upgrade:

• If Quest IBM DB2 z/OS Component 4.5.0 resides on the DB2 subsystem, perform Part 1: Update the LOADLIB only.

Determine Current Quest IBM DB2 z/OS Component Version

To determine the Quest z/OS component version currently installed on a DB2 subsystem

1. Open a Toad Editor on the DB2 subsystem connection.
2. Execute the following query:

SELECT * FROM TABLE(QUEST.QCVER()) AS UDF;

If the returned value is 5.1.0.14, the component version is 4.5.0. A value less than 5.1.0.14 indicates a pre-4.5.0 version.

Part 1: Update the LOADLIB

To update the LOADLIB

1. Allocate a sequential file on the mainframe using the following attributes:

RECFM=FB

LRECL=80

BLKSIZE=3120

2. Use FTP or an IND$FILE transfer to copy loadlib.xmi (located in the PluginsDB2zOS folder where the Toad for DB2 4.5.2 client is installed) to the sequential file you set up in step 1. Transfer the file in binary mode.
3. At a TSO command prompt, type the following, where 'sequential.file.name' is the file you allocated in step 1:

TSO RECEIVE INDATASET (‘sequential.file.name’)

4. At message INMR906A, type the following:

DATASET(‘loadlib.name’)

The variable ’loadlib.name’ is either the name of the new PDS/E or the name of the old LOADLIB you are replacing, depending on whether you created a new PDS/E or are using the existing LOADLIB.

5. If you chose to receive the xmi dataset into a new PDS/E, do the following:

1. Update the WLM-started tasks and QPDSNAT procedures to reflect the new load library name.

2. APF-authorize the new LOADLIB.

Part 2: Define the New Functions

To define the new functions

1. Locate the U4045DDL member in the PluginsDB2zOS folder where the Toad for DB2 4.5.2 client is installed.

2. Open this file in the Toad Editor.

3. Change the %COLLID% and %MULTTCB% variables in the script to match those currently used in your system.

4. Execute the script to define the two new functions.

5. Grant these functions the same EXECUTE privileges granted to other QUEST functions.

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

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

Toad supports any of these DB2 and operating system versions.

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.
• View the Toad shortcut icon on the desktop or the Toad menu options on 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 a 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 saved to an file (via the db2cfexp command) into the Toad client catalog.
• To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document:
• 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 privileges 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:
• 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 version 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.
6. In the File field, locate and select Toad.exe.
7. 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.
• For information about defining a RACF, Unix, or Linux group as a Toad Security role, see the About Setting Up Toad Security topic in the Toad online help. This topic explains how to add the Toad Security icons to your toolbar and how to define Toad Security roles that apply to your current connection. (The ability to define RACF, Unix, and Linux groups as Toad Security roles works with DB2 for LUW 9 or later databases and DB2 for z/OS 8 or later subsystems.)

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 requirements 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 Using Toad DB2 for z/OS Functionality

• To perform any of the following functionality in Toad, you must have Quest IBM DB2 z/OS Component 4.5 installed on your DB2 for z/OS subsystems:

  • Bind and rebind DB2 for z/OS packages and plans

  • Invoke DB2 for z/OS utilities and commands within scripts that Toad for DB2 advanced alters, migrations, and synchronizations generate

  • Run stand-alone DB2 for z/OS utilities and commands in Toad

  • Run DB2 for z/OS commands from the Editor

  • Execute remote DB2 for z/OS scripts

  • Create, alter, or drop dataset templates

  • Run Display, Start, and Stop commands on DB2 for z/OS databases, tablespace, and indexes

  • Access accurate buffer-pool information for the DB2 subsystem

  • View volumes available for defining storage

  • Access information about current threads connected to the DB2 subsystem

  • Assign a RACF group to a Toad Security role to control the Toad features available to all users belonging to the RACF group.

If you currently have the Quest Central for DB2 z/OS component or a previous Quest IBM DB2 z/OS component installed on your DB2 subsystem, perform an upgrade. Use the instructions found in Upgrade and Compatibility.

If the neither the Quest Central for DB2 z/OS component nor a previous Quest IBM DB2 z/OS component currently exists on your DB2 subsystem, perform a new installation of Quest IBM DB2 z/OS Component 4.5. Use the instructions found in the Quest IBM DB2 z/OS Installation Guide (available from the Windows Start menu under Program Files Quest Software Toad for DB2 Documentation).

• The IBM stored procedure SYSPROC.DSNUTILU must be installed and operational on each DB2 subsystem on which you are executing DB2 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.
• When Toad migrates data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. The definition for Reorg Unload dataset 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:

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 specifications for using Toad's Object Migration wizard to migrate DB2 objects and their dependencies:

• You cannot migrate objects between a DB2 for LUW and DB2 for z/OS platform and vice versa.
• Unexpected results can occur if you map two source schemas to the same target schema, and the two source schemas contain same-named objects (for example, if you map both source Schema A and source Schema B to target Schema C, and Schema A and Schema B both contain a table with the name Table1).

ConfigurationRequirements for SQL Analysis

Autodesk License File Location

SQL Analysis requires the following configuration on the database servers on which you intend to run SQL collections:

• 36 4-kilobyte pages to run event monitors.
• The mon_heap_sz database manager configuration parameter set appropriately to support event monitors. See the IBM DB2 for Linux, UNIX, and Windows System Monitor Guide and Reference for more information about setting this parameter.

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:

Configuration Prerequisites

You must configure Toad to work with your existing version control system. Ensure that you install the following on the same computer where 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.

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.

However, this release has the following known capabilities or limitations:

• During the Toad for DB2 installation process, a user can override the default installation path, but cannot include Unicode characters in the new path specification. This limitation exists because Toad installs a DB2 for LUW client in the specified Toad installation path, and DB2 installations do not support Unicode characters.
• (Toad for DB2 for z/OS Xpert Edition and Toad for DB2 for LUW or z/OS DBA Edition only) The Toad SQL Tuning for DB2 z/OS, Toad SQL Analysis for DB2 LUW, and Toad Remote Script Execution (for DB2 LUW or z/OS) features support single-byte character sets only. These features do not support double-byte or multi-byte character sets. All DB2 client and server installations should be configured to use the same or compatible character encodings and the same locale and regional options.

Contents of the Release Package

The Toad for DB2 release package contains the following products:

• Toad for DB2 4.5.2
• Quest IBM DB2 z/OS Component 4.5,2
• Product documentation, including:
  • Toad for DB2 Installation Guide
  • Quest IBM DB2 z/OS Component Installation Guide
  • Toad for DB2 LUW Agent 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.

Installation Instructions for Additional Components

To install other Toad for DB2 components, refer to the following documentation:

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

© 2009 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.

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.