Syntax for Securing Database Resources › GRANT Access Module Execution Privilege › GRANT Access Module Execution Privilege Usage

GRANT Access Module Execution Privilege Usage

CA IDMS Internal Security Enforcement

When executing an access module in a database for which CA IDMS internal security is in effect, the owner of the access module must either hold the applicable privileges on the table-like objects named in the SQL statements in the module, or own the table-like objects. You own the access module if you own the schema associated with the access module.

For a user who is not the owner to execute an access module, these conditions must be satisfied:

• The user must hold execution privilege on the access module.
• The owner must either hold the applicable grantable privileges on the table-like objects named in the SQL statements in the module, or own the table-like objects.

These rules allow you to restrict a user's means of accessing data to application programs. If you grant table access privileges, the user can also access data through the Command Facility.

External Security

When executing an access module in a database for which external security is in effect, the user, regardless of ownership, must hold the applicable privileges on all tables accessed by SQL statements in the module, whether accessed directly or indirectly through a view.

Granting Execution Privilege

The following GRANT statement gives execution privilege on all access modules associated with schema HR that begin with 'EMP' to the groups PER_GRP_1 and PER_GRP_2:

grant execute
   on access module hr.emp*
   to per_grp_1, per_grp_2;