Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Toad for DB2 7.4 - Installation Guide

Troubleshoot DB2 z/OS Issues

Review the following solutions to help troubleshoot DB2 z/OS issues in Toad.

Installation Issues

Issue Cause/Solution

Error: "Could not load file or assembly 'IBM.Data.DB 10.5.11, Version=10.5.11, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified."

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.

When installing Toad on Windows 10 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message.

Solution:

Select This program installed correctly to continue installation. For more information, see https://support.microsoft.com/en-us/windows?ui=en-US&rs=en-US&ad=US

Connection Issues

Issue Cause/Solution

ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001  

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.

ERROR [58031] [IBM] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031  

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.

ERROR [42501] [IBM][DB2] SQL0551N "UserName" does not have the privilege to perform operation "SELECT" on object "SYSIBM.SYSSTMT". SQLSTATE=42501

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.

ERROR [] [IBM] SQL1460N The environment variable "SOCKS_NS" required for SOCKS server name resolution is not defined or not valid.

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

ERROR [56038] [IBM][DB2] SQL0969N There is no message text corresponding to SQL error "-4700" in the message file on this workstation.' when connecting to compatibility mode database.

-or-

After connecting, some objects do not display properly or some functionality does not work as designed.

In general, Toad does not support a z/OS subsystem running in Compatibility mode.

Solution:

If possible, switch the subsystem's operating mode to Full Function mode.

If this is not possible, Toad now provides a message when you connect to subsystem, informing you of that the subsystem is running in compatibility mode and that some features might not be available.

Other Issues

Issue Cause/Solution

Poor performance when browsing DB2 for z/OS objects in Toad. Indexes are populated slowly.

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

Encountering the S378 Abend when running IBM DB2 z/10 subsystem in Conversion mode with older versions of Toad.

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.

 

Related Topics

Create DB2 Connections

Manage Connections

Connection/Navigation Manager 

Configure Version Control

About Version Control

Toad integrates with your existing version control system so you can maintain multiple revisions of objects and SQL scripts . See Configure Version Control for Objects for more information on configuring version control in Toad.

For Version Control of your files handled by Toad see Version Control for Toad Files.

Important: See Troubleshoot Version Control for more information about issues when upgrading version control from a previous version.

Notes: 

  • If you want to place database objects under version control, you must configure version control for objects using the Object Explorer. Once configured, you can manage SQL scripts there. The main advantage of managing scripts in the Object Explorer is that you can easily share them with team members who have version control configured. See Manage Objects under Version Control for more information.
  • If you rename a version controlled object, Toad drops the original object and its history from version control and prompts you to add the renamed object to version control. This newly renamed object does not have any history associated with it.
  • Currently, CLR objects are not supported by version control.

Prerequisites

You must install a supported version control client on the computer where Toad is installed. The following table lists the supported version control providers and the versions tested with Toad.

Supported Provider Server Version Tested Client Version Tested

Apache Subversion™

 

Subversion 1.7.5 on Windows

CollabNet Subversion Command-Line Client 1.7.5

Note: Any Subversion client must have svn.exe in its installation directory to use version control in Toad.

Git Toad works only with the local repository. For commands such as clone, pull and push use an external tool.

Team Foundation Server (TFS)

TFS 2008, 2010, 2012, 2013

Visual Studio® (2008, 2010, 2012, 2013) Team Explorer Client

 

File system based Toad allows to utilize practically any version control system using the external client tool. In this case Toad Version Control tool works with the directories at local HDD while you commit changes to the repository with version control client tool.

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

The following objects can be added to Version Control:

ALIAS

DISTINCT TYPE

INDEX

MQ TABLE

SCHEMA

SEQUENCE

TABLE

TRIGGER

USER

VIEW

FUNCTION

PROCEDURE

SCRIPT

Details of Team Foundation Server support:

Visual Studio/Team Explorer version TFS 2013 support notes TFS 2012 support notes TFS 2010 support notes
Visual Studio 2015 Supported (RTM or latest update) Supported (RTM or latest update) Supported (RTM or latest update)
Visual Studio/Team Explorer 2013 Supported (RTM or latest update) Supported (RTM or latest update) Supported (RTM or latest update)
Visual Studio/Team Explorer 2012 Requires latest Visual Studio 2012 update. Supports Git with Visual Studio Tools for Git extension Supported (RTM or latest update). Supports Git with Visual Studio Tools for Git extension Supported (RTM or latest update). Supports Git with Visual Studio Tools for Git extension

Note: Additional functionality and compatibility with older clients is possible but out of scope of what we are able to test.

 

Related Topics

Configure Version Control for Objects

Manage Objects under Version Control

File Version Control

Toad can integrate with your existing version control system allowing you to maintain multiple versions of Toad files. After you integrate Toad with your version control system, you can perform version control tasks directly from within Toad, such as commit file changes and retrieve revisions.

Toad supports the following version control systems for managing Toad files:

  • Apache Subversion™—Toad has been tested with Subversion 1.7.5 and 1.8.

The following types of files can be managed using version control from within Toad: Editor (.tef, .sql, .txt), Query Builder (.tsm), ER Diagram (.ter), and Automation (.tas).

Toad supports version control for database objects, as well as files. Version control for objects is configured separately from version control for files. For more information about version control for objects, see Configure Version Control for Objects.

To configure version control for Toad files

  1. Ensure that an Apache Subversion client is installed on the same computer as Toad.

  2. In Toad, open one of the supported file types. Then right-click the document window tab and select File Version Control | Version Control Wizard. This action opens the Version Control Wizard which allows you to configure Toad for your version control system.

    Note: Even if you previously configured version control for objects, you must run the Version Control Wizard again to configure version control for files.

  3. Use the wizard to provide information about your version control system to Toad. Review the following for additional information:

    Field/Button  
    Version Control System Page  

    Type

    		 Select Subversion.

    Properties

    Click the Properties button and enter the path to the Subversion executable (svn.exe) on the client computer. For example, if using TortoiseSVN, the path might be:

    C:\Program Files\TortoiseSVN\bin

    Note: Do not include svn.exe in the path.

    Server

    Enter the URL for the Subversion repository on the Subversion server.

    Login and Password

    		 Enter the user name and password for your Subversion account.
    Default Version Control Settings Page  

    Version Control Folder

    Select the folder on the Subversion server where you want to check in files.

    If you currently have files under version control, select the folder on the server where these files are located.

    Working Folder

    Select a folder on the client computer to use as the root working folder. This is the location into which you will check out files.

    If you currently have files under version control, select your existing working folder.

To add a file to version control

  1. After configuring version control for files, you can start adding files to version control from within Toad. Right-click a document window tab and select File Version Control | Add file to working folder.
  2. Select a location in your working folder in which to save the file. Click Save.
  3. In the Commit dialog, enter a comment and click OK to add the file to version control.

To browse the repository

  1. Right-click the document window tab (of one of the supported file types) and select File Version Control | Repository Browser.

  2. In the Repository Browser you can right-click a file to perform one of the following actions. Available actions depend on the file's status.

    Action Description
    Open Open the file in Toad.
    Commit Commit your changes. Available for Modified or Untracked files.
    Undo Changes Discards your changes and reverts to the previous revision of the file (previous commit). Available when the file status is Modified.
    Get Latest Version Check out the latest revision from the remote repository. Available when the file status is OutOfDate.

To commit your changes

  • After modifying a file, right-click the document window tab and select File Version Control | Commit.

To compare revisions (Editor files only)

  • After modifying and saving an Editor file, you might want to compare your changes to the remote copy (last commit) before committing your changes. Right-click the document tab and select File Version Control | Diff with latest revision.
  • You can compare two revisions of an Editor file (.tef, .sql, or .txt) by using the History dialog.
    1. To open a file's History dialog, right-click the document tab and select File Version Control | Show history.
    2. Select two revisions to compare. Then right-click the revisions and select Compare revisions.
    3. For an OutOfDate file, right-click the latest revision in the History dialog and select Compare with working copy to compare the remote file to your working copy.

To check file status

  • The status of a currently open file displays in the status bar of the document window. You can also place the cursor over the document tab to display status.
  • You can check the status of one or more files by using the Repository Browser. To update file status in the Repository Browser, right-click a folder and select Update folder.

  • Review the following file status definitions.

    File Status Definition
    Untracked The file has not been added to version control. Right-click the file in the Repository Browser and select Commit to add it to version control.
    UpToDate The file in your working folder is synchronized with the file in the remote repository. No changes are detected. No action is required.
    Modified The working copy of this file was modified. The changes are stored in the working folder only. Commit this file to add the changes to the remote repository.
    OutOfDate A more recent revision of this file exists in the remote repository. To update your working copy, check out the latest revision from the remote repository (right-click the file and select Get Latest Version).
    Unknown The file is under version control, but its status cannot be determined.
    Deleted The file was under version control, but it was dropped or renamed in the working folder and exists only in the remote repository.

Additional Actions

  • To open the folder where a file is located, open the file and then right-click the document tab and select File Version Control | Open in Windows Explorer.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation