About Database Name Tables
When you secure the database name table resource type, you control who can issue DBTABLE definition statements and who can display or punch the DBTABLE load module. Until you secure the database name table resource type, any user can issue DBTABLE definition statements if database security is not in effect, and any user can display or punch the DBTABLE load module.
How to Secure Database Name Tables
If the system dictionary is secured, DBADMIN privilege on the system dictionary is required to manipulate database name table definitions.
Note: For more information, see Securing the Dictionaries and the User catalog.
The following discussion applies to securing database name tables explicitly.
To secure database name tables internally, include an entry in the SRTT:
#SECRTT TYPE=ENTRY, X
RESTYPE=DBTB, X
SECBY=INTERNAL
To secure database name tables externally, include an entry in the SRTT:
#SECRTT TYPE=ENTRY, X
RESTYPE=DBTB, X
SECBY=EXTERNAL, X
Additional parameters required
Note: For more information, see #SECRTT.
How to Grant Database Name Table Definition Privilege
To allow a user to create and maintain a database name table definition, you issue a GRANT statement on the database name table resource type, specifying the privilege or privileges and identifying the database name table. You can specify any combination of CREATE, ALTER, DROP, DISPLAY, and USE privileges, or you can specify all privileges (DEFINE).
Note: The USE privilege allows the user to punch the database name table load module and to associate the database name table with a DMCL.
As a holder of the applicable SYSADMIN or DBADMIN privilege, you can specify WITH GRANT OPTION when you grant these privileges to allow the recipient to grant the same privileges to another user. You must be connected to the system dictionary.
More Information:
|
Copyright © 2014 CA.
All rights reserved.
|
|