1. Db2 Express C Installation Guide Reviews
2. Db2 Express C Installation Guide 2017

To install DB2 Express-C 9: Log on to the system as a user with root authority. If you are installing from a CD or DVD, enter the command to mount the DB2 installation media. Change to the install directory. Run the db2setup command. When the IBM DB2 Setup Launchpad opens, select 'Install a Product'.

Installation

System Requirements

Review the following client and database server requirements for Toad®for IBM® DB2®.

Client Requirements

Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:

Db2 Express C Installation Guide Reviews

Server Requirements

Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:

Virtualization Support

Db2 Express C Installation Guide 2017

User Requirements

User Requirements to Install Toad

Only Windows 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.
• 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 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, these users can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad.

• 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 requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or 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 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.)

Requirements for Full Access to Toad for DB2 z/OS Functionality

Install the following components on each DB2 for z/OS subsystem:

• Toad for IBM DB2 z/OS Components

  Notes:

  • Without the z/OS components installed, Toad for IBM DB2 provides limited support for managing DB2 for z/OS subsystems. With the z/OS component installed, you have access to a full range of Toad functionality needed to manage DB2 subsystems.

  • If no Toad for IBM DB2 z/OS components are installed on your subsystem, see the Toad for IBM DB2 z/OS Components Installation Guide for installation requirements and instructions.

• IBM stored procedure SYSPROC.DSNUTILU, installed and operational.

  Notes:

  • Toad requires SYSPROC.DSNUTILU to run DB2 utilities. For more information about this stored procedure, see Appendix B of the IBM DB2 Universal Database for z/OS Utility Guide and Reference.
  • A 32K character-size limit exists for each utility statement executing through DSNUTILU.

• Certain table alterations require that Toad perform advanced alters involving multiple UNLOADs and LOADs of table data. Before executing these types of alterations, ensure that the Mask value defined for the Toad dataset template that generates the Unload datasets includes the &SEQ variable. This variable creates a unique name for each Unload dataset. (The Unload dataset template is identified in Tools Options Database DB2 z/OS Load/Unload.)
• When Toad migrates data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. Ensure that the Reorg Unload dataset template (identified in Tools Options Database DB2 z/OS Reorg) generates a dataset that resides on a pack (VOLSER) accessible by both the source and target subsystem.

Compile and Debug Requirements for Stored SQL Procedures

Toad requires the following to compile and debug stored SQL procedures in DB2.

• DB2 for LUW Requirements

The following is required to debug and compile stored SQL procedures on DB2 for LUW databases:

• DB2 for z/OS Requirements

The following is required to debug and compile stored SQL procedures on DB2 for z/OS subsystems:

Install Toad

Toad for IBM DB2 is available in the following editions: Base, Professional and Xpert. DB Admin Module is an add-on module that provides extended admin functionality and can be added to any Toad edition.

Note: Your Toad for IBM DB2 license key determines the edition and will enable Toad for IBM DB2 functionality accordingly. In many cases, if functionality is disabled within Toad for IBM DB2, you may not have an appropriate license to use it. When Toad is running, you can see which components are licensed by selecting Help About.

To install Toad

1. Run the Installer.

2. Accept the License Agreement.

3. Select the products you want to install and click Install.

   Note: When installing Toad using Quest Software Installer on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message. Select This program installed correctly to continue installation.

Note: Check Prohibit saving passwords during the installation to prohibit users from saving their passwords in Toad.

Specify App Data Directory Location

Toad for IBM DB26.5 stores settings files in the user's Application Data directory. The default location cannot be modified from within the application. Toad provides two methods to change the default location: by using a Registry setting or by using a command switch in a Toad shortcut.

Use the Registry setting method to change the application data directory from Roaming to Local. Use the command switch method to change the location to any new path.

To change Toad Application Data directory location from Roaming to Local

In the Registry under Toad for IBM DB2 (ComputerHKEY_CURRENT_USERSoftwareQuest SoftwareToad for IBM DB26.5), add LOCALSETTINGS with a value of 1.

See the following table for default (Roaming) and resulting (Local) directory path.

Caution: All current Toad settings will be lost after applying this Registry setting unless you manually copy the settings files from the default location (Roaming directory) to the new location (Local directory). Copy the settings files BEFORE you add the Registry setting and BEFORE opening Toad.

To change Toad Application Data directory location using a command-line switch

You can override the default Application Data directory by running Toad with the command switch:

Toad.exe --datadir='YourNewDirPath'

To instruct Toad to always use the new directory path, add the command switch and the new directory path to a Toad desktop shortcut. Then use the desktop shortcut when opening Toad.

1. To add the command switch, right-click the Toad shortcut and select Properties.
2. Enter the command switch and add the directory path in quotes (replace 'YourNewDirPath' with your directory path).