Return
-
Title
User Requirements, Permissions and Restrictions for Running Toad against LUW and z/OS databases -
Description
The following describes the requirements, permissions and restrictions for users who launch and run Toad -
Resolution
- 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 Vista Administrators group. Additionally, to enable full functionality in Toad for IBM DB2 when Vista’s User Access Control security feature is turned on, the standard user must run Toad for IBM DB2 as an administrator. (Right-click the Toad for IBM DB2 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 for IBM DB2 Client Configuration wizard. However, these users can use the Import Profile function in the Toad for IBM DB2 Client Configuration wizard to import catalog entries to Toad for IBM DB2.
- 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 Toad IBM DB2 LUW Authorizations Spreadsheet
- As a minimum requirement to manage a DB2 for z/OS subsystem in Toad for IBM DB2, the user ID defined in the Toad for IBM DB2 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 Toad IBM DB2 z/OS Authorizations 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.)
-
Additional Information
For a complete list of System Requirements, please review the Toad for DB2 Technical Documentation