Background documentation-us: Creating or Changing XUSER Entries Locate this document in the navigation structure

 

XUSER entries are sets of user data, which are defined by user keys. They facilitate the logon process to programs that support XUSER.

In Database Manager, you can use the XUSER program with the DBM option –us to create new XUSER entries, or to overwrite existing entries.

You can use an XUSER key together with the DBM option -U to log on to Database Manager (see: user_logon). This means that you do not need to specify a DBM operator name and password (DBM option –u), since Database Manager CLI takes the required data from the relevant XUSER entry.

Recommendation Recommendation

We recommend that you use the XUSER program directly to create or change XUSER entries instead of using this DBM option.

End of the recommendation.

Note Note

You can only access a database with a user stored under an XUSER entry if that user has been actually created for this database. DBM operators can be created using Database Manager. (see: user_create). Also database users can be created using Database Manager (see: db_execute).

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

End of the note.
Creating XUSER Entries

To create new XUSER entries, no logon to the XUSER program ist required.

You can define a user key for an XUSER entry, under which this entry is to be stored. You can also instruct Database Manager CLI to generate this user key from a combination of the database name and the database computer name. You do so by specifying the database name and database computer name in addition to the user name and password.

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

Other functions require that you log on to Database Manager 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, 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 the database computer name (DBM options -d and -n).

Structure

-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

Example

Creating a New XUSER Entry
Saving Under a Defined User Key

Call Database Manager CLI, create a new XUSER entry for the user BORIS with the password PINK, save this user data under the user key DEFAULT):

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

with example data:

>dbmcli -uk DEFAULT -us BORIS,PINK

Saving Under a Generated User Key

Call Database Manager CLI, create a new XUSER entry for the user MONA with the password RED), save this user data under the user key, which is generated from the database name DEMODB and the database computer name GENUA:

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

with example data:

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

Changing an Existing XUSER Entry
Logging on with the Data of the User to be Changed

Call Database Manager CLI, log on to the XUSER program with the DBM option -u and the data of the XUSER entry to be changed (user MONA, password RED), change the data of this XUSER entry to the user DAVID with the password BLUE,

  • and specify the XUSER entry 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]

    with example data:

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

  • or specify the XUSER entry to be changed using the combination of the database name and the database computer name (DEMODB and GENUA):

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

    with example data:

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

Logging on with the User Key DEFAULT

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

  • and specify the XUSER entry to be changed using the DBM option –uk (user key: DAKEY), specify the new user data (user MONA, password RED) using the DBM option –us:

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

    with example data:

    >dbmcli -ux BORIS,PINK -uk DAKEY -us MONA,RED

  • or specify the XUSER entry to be changed using a combination of the database name DEMODB and the database computer name GENUA, specify the new user data (user name MONA, password RED) using the DBM option -us:

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

    with example data:

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

More Information

Utilities, XUSER