HP 3000 Manuals HP 3000 Manuals
Task 7:Deleting IMAGE/SQL Users
This task describes how to delete IMAGE/SQL users.
Getting Ready
To perform this task, you must be both the TurboIMAGE/XL DBC and an SQL
DBA.
If you want to check the current users before adding new IMAGE/SQL users,
issue the DISPLAY USER command. For example:
________________________________________________________________
| |
| >>DISPLAY USER |
| |
| TurboIMAGE/XL DB : SALES.SERED.ATC |
| DBEnvironment : PARTSDBE.SERED.ATC |
| |
| USER LOGON DBOPEN MODE USER PASSWORD USER CLASS|
| ---------- ----------- ------------- ----------|
| |
| NANCY.ATC 5 ; 64 |
| SMITH.ATC 5 CLERK 14 |
| |
| >> |
________________________________________________________________
Performing the Task
Use the DELETE USER command to delete an IMAGE/SQL user. For example:
_____________________________________
| |
| >>DELETE USER SMITH.ATC |
| >> |
_____________________________________
Here, SMITH.ATC is deleted as an IMAGE/SQL user and removed from the
corresponding authorization group.
The DISPLAY USER command now reflects the deletion.
________________________________________________________________
| |
| >>DISPLAY USER |
| |
| TurboIMAGE/XL DB : SALES.SERED.ATC |
| DBEnvironment : PARTSDBE.SERED.ATC |
| |
| USER LOGON DBOPEN MODE USER PASSWORD USER CLASS|
| ---------- ----------- ------------- ----------|
| |
| NANCY.ATC 5 ; 64 |
| |
| >> |
________________________________________________________________
Note that SMITH.ATC is still configured as an SQL user because
ALLBASE/SQL tables and views may be owned by this User.Logon.
Task Reference
* When the last SQL user logon associated with a TurboIMAGE/XL
user class is deleted, the SQL authorization group
(OwnerName_UserClass#) and views associated with this user class
are not dropped. Doing so would invalidate any views that may
have been created based on these IMAGE/SQL views.
* The SQL syntax User@Account (or User.Account) is used to add an
IMAGE/SQL user. This name, referred to as the DBEUserID, is made
up of an MPE/iX user and account name, connected with the @ symbol
(or period). It must contain valid logon syntax.