DB2 Server-side licensing

Yesterday dinner came back a little late, did not write in time, today to fill up.
DB2 server-side installation will not say, many online. Let's talk about authorization today. It's a matter of trouble.
The installation will allow you to create a database. You just have to follow the prompts to create it.
First step: DB2 Connect to database user username using a password connected to the corresponding database
See if you can connect properly to the database you created.
Step two: DB2 get authorizations See how many permissions the current user has obtained
Step three: The real mandate begins.
DB2 update dbm CFG using Sysadm_group user name Grant SYSADM permissions to the user
DB2 update dbm CFG using Sysctrl_group user name Grant Sysctrl permissions to the user
DB2 update dbm CFG using Sysmaint_group user name Grant Sysmaint permissions to the user
The above will be authorized success, trouble in the following, let me go a lot of detours.

DB2 Grant SECADM on the database to user authorization Secadm permission for user name
Note: He must connect to the database using the user group. Otherwise, authorization will fail.
Column: DB2 Connect to Txhy
This does not write the user name will be automatically based on the user's user group login.

DB2 Grant SECADM on the database to user user name
Authorization Secadm Permission discovery will prompt the command to complete successfully
Other SECADM-Related authorization commands:

DB2 Connect to sample

DB2 Grant DBADM on the database to user user name

DB2 Grant Accessctrl on the database to user username DB2 grant DataAccess on the database to user username DB2 grant SQL ADM on database to user username DB2 grant WLMADM on database to user username
These are exactly what the authority will not say. Should be able to guess.
It's over. You'll find your local DB2 database connection DB2 server-side can manipulate the contents of the database table

DB2 Server-side licensing