## user_logon

### Use

The specified DBM operator logs on to the Database Manager program.

Before you log on to the Database Manager, you have to open a session of the DBM server of the database instance you want to manage. You can open this session and log on at the same time (one step logon) or first just open the session and then log on to the Database Manager in a second step (two step logon).

A connection must always be made to the DBM server on the computer of the database instance to be administrated. If the database instance is located on a remote computer, you need to specify the name of the database computer too when logging on to the Database Manager.

See also:

Server Authorizations

Concepts of the Database System, Database Manager Operator (DBM Operator)

### Two Step Logon

You can first open the session with the DBM server and then log on to the Database Manager.

...

1. Open a DBM Server session:

>dbmcli –d <database_name> [-n <database_computer>]

dbmcli on DEMODB>

2. Log on to the Database Manager:

dbmcli on DEMODB>user_logon <dbm_operator>,<dbm_operator_password>

OK

dbmcli on DEMODB>

### One Step Logon

You can perform both logon steps at the same time by using the DBM option –u | -U. In this case, the Database Manager executes the user_logon DBM command implicitly.

Note that the option has different meanings depending on whether it is upper- or lowercase.

#### Using the DBM Option -u

>dbmcli -u [<dbm_operator>,<dbm_operator_password>] –d <database_name> [-n <database_computer>]

· -u: explicit specification of the Database Manager operator identified by <dbm_user_name> and <dbm_user_password>

#### Using the DBM Option –U (Logon with XUSER)

>dbmcli -U [<user_key>] –d <database_name> [-n <database_computer>]

· -U: logon with a user stored in the XUSER file

You can use the XUSER program to store sets of user data as user keys and use them when logging on. User keys for Database Manager operators can be used successfully only if the operators stored in them have actually been created for the database instance in question (see also: user_create)).

If you do not specify a <user_key> when using –U, the Database Manager attempts to use the data under the DBMUSR user key. It is therefore recommended that you create an XUSER entry with the user key name DBMUSR and the data of the Database Manager operator with the most comprehensive authorizations (see also: Creating or Changing XUSER Entries).

### Reply

dbmcli on [<database_computer>]: <database_name>

In the event of errors, see Reply Format.

### Examples

Two Step Logon

...

1. Call the Database Manager in session mode and connect to the local database instance DEMODB:

>dbmcli -d DEMODB

dbmcli on DEMODB>

2. Log on as user OLEG with the password MONDAY:

dbmcli on DEMODB>user_logon OLEG,MONDAY

OK

dbmcli on DEMODB>

or:

...

1. Call the Database Manager in session mode and connect to the database instance MAXDB on remote computer GENUA:

>dbmcli -d MAXDB – n GENUA

dbmcli on GENUA : MAXDB>

2. Log on as user OLEG with the password MONDAY:

dbmcli on GENUA : MAXDB>user_logon OLEG,MONDAY

OK

dbmcli on GENUA : MAXDB>

One Step Logon with User Key and Execution of a DBM Command

Call the Database Manager CLI, log on as an operator with the user key OLKEY, connect to the local database instance DEMODB, display the operational state of the database instance:

>dbmcli –U OLKEY –d DEMODB db_state

OK

State

OFFLINE

One Step Logon with Name and Password of a DBM Operator and Execution of a DBM Command

Call the Database Manager CLI, log on as operator OLEG with password MONDAY, connect to the local database instance DEMODB, display the operational state of the database instance:

>dbmcli –u OLEG,MONDAY –d DEMODB db_state

OK

State

OFFLINE