There are many terms used within the native DB2 environment. The following list provides the terms that are used throughout the subsequent chapters of this guide.
A Structured Query Language that can be used within DB2 to access data and to control access to resources through GRANT and REVOKE statements.
A term used for a unit that has the same basic properties in every environment but depends on the environment. It involves the execution of one or more programs, and is the unit that contains allocated resources. The execution of an SQL statement is always associated with some process.
The primary owner of a DB2 object is the ID recorded in the CREATOR column of the relevant Catalog table.
Anything that can be created or manipulated with SQL, such as: databases, table spaces, tables, views, or indexes. In CA Top Secret Option for DB2 these objects are also known as resources.
This represents a user during a process to perform a DB2 operation. The primary authorization ID is also the user's original authorization ID, unless an exit changes it.
This represents an optional ID, which can hold additional privileges available to a process.
This is the current authorization ID of the user for those commands or statements where composite privileges are not used. The term “composite privileges” means that the execution of an SQL statement can be based on the privileges of more than one authorization ID of the process.
A specific privilege given to a process by execution of a GRANT statement.
A privilege which is not the result of any GRANT statement. The user has an implicit privilege as the owner of an object.
|
Copyright © 2011 CA Technologies.
All rights reserved.
|
|