To use DB2, log on with a valid user ID that has the appropriate authority level for the commands you want to execute. If the SYSADM_GROUP parameter is defined in the database manager configuration file, the user performing administration tasks (such as cataloging, starting the database manger, or creating the sample database) must belong to the System Administrative group. The SYSADM_GROUP parameter is not set when DB2 is first installed; therefore, the following criteria are used to determine SYSADM authority:
 |
You can override this default case by explicitly providing a group name for the SYSADM_GROUP parameter. If you do this, the only way to assign SYSADM authority is by membership to this group. See "Changing Default Privileges for Users" for more information
|
See Appendix D. "Naming Rules" for a list of restrictions on valid user IDs.
To log in from OS/2 locally, use UPM.
| Note: | If you are using OS/2 Warp Version 4, OS/2 Warp Connect, or OS/2 Warp Server, an administrative user ID was created during installation. Use this user ID to perform the steps that require administrative authority or to create additional users with the correct authority. Previous versions of OS/2 are initially set up with a default user ID (USERID) and password (PASSWORD). Try logging on with the defaults if you are unsure of any other administrative user on your system. |
As well as using the local operating system security to authenticate users, there is also the option of using DCE security. Refer to the Administration Guide for information on DCE security.