Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Security >

OS/390 and z/OS Security

---

By default, DB2 restricts access to database resources unless privileges are specifically granted. A complete description of DB2 security is available in the DB2 UDB for OS/390 and z/OS Administration Guide. Access to database resources is established using one or more of the following authorization IDs:

Current SQLID. This is the ID that defaults to the user ID used when logging into DB2. It can be changed by a SET CURRENT SQLID command.
Secondary Authorization ID. This ID is generally known as a group ID. Siebel applications effectively use secondary authorization IDs that can be enabled through the DB2 exit DSN3@ATH. IBM provides a sample exit for setting secondary authorization IDs.
Specially bound package owners. The owner ID is used when DYNAMICRULES(BIND) is specified on packages used with DB2 Connect.

Bookshelf Home | Contents | Index | Search | PDF