Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

CREATE SYSTEM_USER - Create system entry

You use CREATE SYSTEM_USER to define a system entry, i.e. assign authorization identifiers to the system users. You can assign an authorization identifier to more than one user, and a single user may have more than one authorization identifier.

A local UTM system user is identified by the local host name, the local UTM application name and the UTM user ID.

A UTM system user working with SESAM databases via UTM-D is identified by the local host name, the local UTM application name and the local UTM session name (LSES).

A BS2000 (TIAM) system user is identified by the host name and the BS2000 user ID.

Please note that before you move a database to another system, you must first define a valid system entry for the new system. If this is not possible for technical reasons, please contact your service agent.

The current authorization identifier must have the special privilege CREATE USER. If you want to assign a system user an authorization identifier with the special privilege CREATE USER and with GRANT authorization (see section "GRANT - Grant privileges"), the current authorization identifier must also have GRANT authorization.



CREATE SYSTEM_USER

   { utm_user | bs2000_user } FOR authorization_identifier AT CATALOG catalog


utm_user ::= ({ hostname |*},{ utm_application_name |*},{ utm_userid |*})

bs2000_user ::= ({ hostname |*},[*],{ bs2000_userid |*})



utm_user

Defines a system entry for a UTM system user.


bs2000_user

Defines a system entry for a BS2000 system user.


FOR authorization_identifier

Name of the previously defined authorization identifier to be assigned to the system user.


AT CATALOG catalog

Name of the database for which the assignment of an authorization identifier to a system user is valid.


utm_user

Specification of the UTM user.


hostname

Alphanumeric literal indicating the symbolic host name.

If DCAM is not available on the host, the host is assigned the name “HOMEPROC”.

For UTM-D: Specification of the local host on which the SESAM/SQL database connection was generated.

* All hosts.


utm_application_name

Alphanumeric literal indicating the name of the UTM application.

For UTM-D: Name of the local UTM application.

* All UTM applications


utm_userid

You specify the UTM user ID as an alphanumeric literal defined with KDCSIGN for local UTM system users. For UTM-D, you specify the local UTM session name (LSES).

* All UTM user IDs.


bs2000_user

Specification of the BS2000 user.


hostname

Alphanumeric literal indicating the symbolic host name.

If DCAM is not available on the host, the host is assigned the name “HOMEPROC”.

* All hosts.


bs2000_userid

Alphanumeric literal indicating the BS2000 user ID.

* All BS2000 user IDs.

Example

In this example, two previously defined authorization identifiers are assigned to system users.

CREATE SYSTEM_USER (*,*,'PHOTO') FOR utiusr1 AT CATALOG ordercust


CREATE SYSTEM_USER (*,*,'TEXT') FOR utiusr2 AT CATALOG ordercust

This enables the authorization identifier UTIUSR1 to access the ORDERCUST database from the BS2000 user id PHOTO. This enables the authorization identifier UTIANW2 to access the ORDERCUST database from the BS2000 user id TEXT.

See also

DROP SYSTEM_USER, CREATE USER