Entering content frame

Syntax documentation -us: Creating or Changing XUSER Entries Locate the document in the library structure

Use

You can use the XUSER program with the DBM option –us in the Database Manager to create new XUSER entries for users, or overwrite existing entries.

XUSER entries are sets of user data that are defined by user keys. They facilitate the logon process to programs that support XUSER. You can use an XUSER key together with the DBM option –U to logon to the Database Manager (see user_logon.) This means you do not have to specify a DBM operator name and password (DBM option –u), since the Database Manager CLI takes the required data from the relevant XUSER entry.

Recommendation

We recommend that you use the XUSER program directly to create or change XUSER entries.

See also: Utilities, Structure linkXUSER

Caution

You can access the database instance with a user stored under an XUSER entry only if that user was actually created for this database instance. DBM operators have to be created using the Database Manager (see also user_create)
Database users can be created with the Structure linkquery tools or the Database Manager (see also db_execute).

Unlike user names and passwords, the Database Manager treats user keys as case sensitive. If you define the user keys DBMUSR and DEFAULT for the default values of the Database Manager, you have to write the user keys in upper-case letters.

Creating XUSER Entries

You do not need to connect to the XUSER program to create new XUSER entries.

You can define a user key for an XUSER entry, under which this entry is to be stored.

You can also instruct the Database Manager CLI to generate this user key from a combination of the database name and computer name. You do so by specifying the database instance and database computer in addition to the user name and password.

To work in the Database Manager, we recommend that you create an XUSER entry with the user key DBMUSR and the user data for the first DBM operator. If you specify the DBM option –U without a user key, the Database Manager CLI attempts to access this key implicitly when you log on to this program.

To execute other functions, you have to log on with the user data stored under the DEFAULT user key. For this reason, we recommend that you also create an XUSER entry with the user key DEFAULT and the user data of a valid database user.

Changing XUSER Entries

To change XUSER entries, you must log on with the data of the user that you want to change, or with the data stored under the DEFAULT XUSER key.

If you log on with the data stored under the DEFAULT XUSER key, you are authorized to change all XUSER entries. To identify the XUSER entry you want to change, use the DBM option –uk or a combination of the database name and computer name (DBM options -d and –n).

Syntax

-us <new_user_name>,<new_user_password>

Options

Option

Description

<new_user_name>

Name of the user you want to save in the key

<new_user_password>

Password of the user you want to save in the key

 

Examples

Creating a New XUSER Entry

...

       1.      Call the Database Manager CLI, create a new XUSER entry (example: user BORIS with password PINK), save under a defined user key (example: user key DEFAULT):

>dbmcli –uk <user_key> –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –uk DEFAULT –us BORIS,PINK

 

       2.      Call the Database Manager CLI, create a new XUSER entry (example: user MONA with password RED), save under a defined user key (example: user key MOKEY):

>dbmcli –uk <user_key> –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –uk MOKEY –us MONA,RED

 

       3.      Call the Database Manager CLI, create a new XUSER entry (example: User MONA with password RED), saving under the user key generated from the database name and computer name (example: database instance DEMODB, computer name GENUA):

>dbmcli –d <database_name> [-n <database_computer>] –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –d DEMODB –n GENUA -us MONA,RED

Changing an Existing XUSER Entry

...

       1.      Call the Database Manager CLI. Log on to the XUSER program with the data of the XUSER entry that is to be changed and with DBM option -u (example: change user MONA, password RED to user DAVID, password BLUE):

                            a.      Specify which XUSER entry is to be changed by entering the user key (example: user key MOKEY):

>dbmcli -u <user_name>,<user_password> -uk <user_key> –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –u DAVID,BLUE –uk DAKEY –us BORIS,PINK

 

                            b.      Specify which XUSER entry is to be changed by entering the combination of database name and computer name (example: database instance DEMODB, computer name GENUA):

>dbmcli -u <user_name>,<user_password> –d <database_name> [-n <database_computer>] –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –u DAVID,BLUE –d DEMODB –n GENUA –us BORIS,PINK

 

       2.      Call the Database Manager CLI, log on to the XUSER program with the data stored under the DEFAULT XUSER key and using the DBM option -ux (example: user BORIS, password PINK):

                            a.      Specify which XUSER entry is to be changed using the DBM option –uk (example: user key: DAKEY).
Specify the new data using the DBM option
–us (example: user BORIS, password PINK):

>dbmcli -ux <default_user_name>,<default_user_password> -uk <user_key> –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –ux BORIS,PINK –uk DAKEY –us BORIS,PINK

 

                            b.      Specify which XUSER entry is to be changed using a combination of the database name and computer name (example: database instance DEMODB, computer name GENUA).
Specify the new data using the DBM option
–us (example: user BORIS, password PINK):

>dbmcli -ux <default_user_name>,<default_user_password> –d <database_name> [-n <database_computer>] –us <new_user_name>,<new_user_password> [options]

Example

>dbmcli –ux MONA,RED –d DEMODB –n GENUA –us BORIS,PINK

 

Leaving content frame