User Guide

SAP AG November 2002
Procedure
1. The database administrator (DBA operator [Page 137]) sets up a database user [Page
136] using the relevant CREATE USER statement.
2. The database administrator informs the operating system user what this database user’s
data is.
3. The operating system user saves the database user’s data using XUSER.
Result
When the Database Manager CLI or the C/C++ Precompiler is now called using the option -U
<user_key>, the system uses the data that was defined in user_key using XUSER. Enter
the user key exactly as it was defined in XUSER, that is, your entries are case-sensitive.
Applications such as SAP DB Loader [Page
148] and Database Manager GUI [Page 134]
and applications that use the ODBC interface (for example, SQL Studio [Page 65]) have no
way of accessing XUSER data.
Using XUSER
User data for setting up a database session [Page 135] can be predefined and saved by
entering a user key (USER_KEY) using the tool XUSER. When the DBMCLI [Page 133] or
the C/C++ Precompiler is called or an SAP system is started, the system can access the
required XUSER data [Page 35] by entering the relevant user key).
XUSER can manage up to 32 combinations of XUSER data per operating system user.
• Windows NT: XUSER data is stored in the database registry.
You are not permitted to make “manual“ changes in the registry because these may result
in inconsistencies in the operating system.
• UNIX: XUSER data is stored in the file .XUSER.62 (also referred to as the XUSER file) in
the user’s HOME directory.
Use
• XUSER data is generated using option -b (Generating XUSER Data in the Background
[Page 36]).
• XUSER data is called using option -U (User Data Using XUSER [Page
34]).
• All XUSER data is deleted by entering the following command:
xuser -b <empty_file>
The empty_file can only contain blanks or must be of length 0.
XUSER Data
Up to 32 combinations of XUSER data can be stored.
Parameter Explanation
User Manual: SAP DB 35