Toad Data Studio 1.0 - User Guide

You installed a commercial version of Toad for DB2 after uninstalling the freeware version.

Solution:

You must remove run time information for the freeware version of Toad from the .NET system.config file.

To remove run time information

1. Exit Toad.

2. Navigate to the following .NET framework directory:
   C:\WINDOWS\Microsoft.NET\
   Framework\v2.0.50727\
   CONFIG

3. Create a backup copy of the system.config file.

4. Open the system.config file in Notepad.

5. Locate the <runtime> tag delete everything between the runtime tags (including <runtime> and </runtime>).

6. Save the file.

7. Restart Toad.

You are attempting to connect to a database version that is not supported in Toad.

Solution:

Review the list of supported databases in the Release Notes or Installation Guide.

You do not have any catalog entries defined for the connection.

Solution:

See Configure DB2 Client Connections for more information to determine the best method for cataloging a database.

You do not have SYSADM privileges for the DB2 for z/OS subsystem.

Solution:

Ensure that you are granted SELECT permissions on the DB2 catalog tables.

When using the Time-Sharing Option (TSO) to connect, the user ID, port number, or IP address entered may be incorrect.

Solution:

Ensure that you use the following for TSO connections:

• DB2 user ID for the DB2 subsystem

• Port number that DB2 listens on, for remote connections, via the DB2 DDF address space

• IP address for the z/OS subsystem

The DB2 installation job DSNTISG defines a set of DB2 procedures that the ODBC driver uses. The installation assigns these procedures (namely, those beginning with SYSIBM.SQL*) to a specific Work Load Manager (WLM) environment, which currently might not exist or be defined properly.

Solution:

Be sure that you have correctly set up and enabled the WLM environment to which the procedure definitions point.

In compatibility mode, the ODBC driver does not return enough information for the CommandBuilder to correctly generate update or insert statements.

Solution:

No solution exists. However, when you connect to a subsystem running in compatibility mode, Toad now provides a message, informing you of this condition and warning you that some features might not be available.

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:

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

This issue appears because the Toad z/OS Component tries to reference the QUEST.QC200ZPARM function.

Solution:

DROP the QUEST.QC200ZPARM function from your DB2 z/OS 10 subsystem. This will eliminate the possibility of the function being called into the WLM environment procedure and causing the S378 abend.

We do not recommend that you to just STOP the QUEST.QC200ZPARM function on the mainframe side, without actually dropping it, because that may case Toad or the batch process (QCEXEC – remote job execution) to hang. Dropping the QUEST.QC200ZPARM function is recommended.