Authorities and Privileges - IBM Database Add-Ins for Visual Studio

To create procedures, functions, and objects (such as tables and indexes) with the IBM^® Database Add-Ins for Visual Studio, you must contact your IBM database administrator to get certain required authorities and privileges, depending on your operating system.

In this topic:

Table 1. General authorities and privileges for IBM Database Add-Ins for Visual Studio tasks
Table 2. Authorities and privileges for DB2 for z/OS and OS/390

Table 1. General authorities and privileges for IBM Database Add-Ins for Visual Studio tasks

Task	Authorities and privileges
Access target database	CONNECT
Register procedures with a database server	CREATE PROCEDURE Also requires one of the following privileges: SYSADM or DBADM CREATEIN for the schema if the schema name of the procedure refers to an existing schema. IMPLICIT_SCHEMA to implicitly create an object with a CREATE statement and specify a schema name that does not already exist. SYSIBM becomes the owner of the implicitly created schema, and PUBLIC is given the privilege to create objects in this schema. Requires USAGE privilege on the SPL language and the RESOURCE privilege on a database in which the SPL procedure is written.
Retrieve rows from a table or view	SELECT
Create a view on a table	SELECT
Run the export utility	SELECT
Insert an entry in a table or view, and run the import utility	IMPORT
Change an entry in a table, a view, or one or more specific columns in a table or view	UPDATE
Delete rows from a table or view	DELETE
Test a procedure or function	SYSADM or DBADM EXECUTE or CONTROL for the package that is associated with the procedure (for SQL procedures or Java procedures with the embedded SQL). DBA or EXECUTE privilege for SPL procedures that were created with the CREATE DBA PROCEDURE statement.
Drop a procedure	You must own the procedure and have at least one of the following privileges: DELETE privilege DROPIN privilege for the schema or all schemas SYSADM or SYSCTRL authority You must own the procedure or have DBA authority.

Table 2. Authorities and privileges for DB2 for z/OS and OS/390

The IBM Database Add-Ins for Visual Studio access DB2 system catalog tables. The user ID that is used to log in to the IBM Database Add-Ins for Visual Studio must have the following privileges:

CONNECT privilege
CREATE PROCEDURE privilege
BINDADD privilege
CREATEIN privilege on each desired collection ID

For DB2 for OS/390, Version 6, the IBM Database Add-Ins for Visual Studio access the following tables:

SYSIBM.SYSPSM
SYSIBM.SYSPSMOPTS
SYSIBM.SYSPSMOUT
SYSIBM.SYSDUMMY1
SYSIBM.SYSPACKAGE
SYSIBM.SUSPARMS

For DB2 for z/OS and OS/390, Version 7, the IBM Database Add-Ins for Visual Studio access the following catalog tables:

SYSIBM.SYSROUTINES
SYSIBM.SYSDUMMY1
SYSIBM.SYSROUTINES_SRC
SYSIBM.SYSROUTINES_OPTS
SYSIBM.SYSPACKAGE
SYSIBM.SYSPARMS

Additional required privileges:

SELECT privilege
EXECUTE privilege on DSNTPSMP

The SELECT privilege is required to browse tables. The IBM Database Add-Ins for Visual Studio do not write to these tables. Data is written to these tables when the REXX procedure DSNTPSMP is called. Therefore, you also need the EXECUTE privilege on DSNTPSMP.

Using a secondary ID with the IBM Database Add-Ins for Visual Studio:

To use a secondary ID with the IBM Database Add-Ins for Visual Studio, the following privileges must be granted to the secondary ID:

BINDADD privilege. For example: GRANT BINDADD TO secondary-ID
CREATE IN privilege on the Collection ID. For example: GRANT CREATE IN COLLECTION collection-ID TO secondary-ID

After these privileges are granted, you can create procedures by adding the OWNER keyword to the BIND options. The format for this option is OWNER (secondary ID).

DDnames used by the DSNTPSMP procedure on WLM:

You need access to specific data sets that defined in the WLM environment in which the procedure DSNTPSMP is running. The actual data set names can vary from site to site, depending on how they are defined in the WLM JCL that they are running.