Setting dsm/scm security, Remapping an alias to a different guardian user id, Setting the dsm/scm user id – HP Integrity NonStop H-Series User Manual
Page 93: Setting security for planners
![background image](/manuals/397210/93/background.png)
Configuring DSM/SCM
DSM/SCM User’s Guide — 529846-014
5 - 8
Setting DSM/SCM Security
Setting DSM/SCM Security
The security settings for planners, database administrators, and operators specify what
tasks they can perform. The database administrator usually sets and maintains security
for all users in the DSM/SCM environment, including:
Check the current security information for a DSM/SCM user
Adding users to DSM/SCM and setting their security access
Changing security information for a user
Listing all DSM/SCM users
Deleting a user from DSM/SCM
Remapping an Alias to a Different Guardian User ID
Before you reconfigure an alias through SAFECOM, use the Maintenance Interface or
Planner Interface to check if the alias exists as a Planner, Database Administrator, or
Operator.
If the alias exists, delete the alias through the Maintenance Interface or Planner
Interface. Then you can reconfigure the alias.
If the alias does not exist, you can remap the alias to a different user or deleted
through SAFECOM.
Setting the DSM/SCM User ID
The default DSM/SCM user ID is the super ID (255,255). The DSM/SCM user ID is the
initial database administrator, responsible for specifying which users are allowed to use
DSM/SCM and what tasks they are permitted to perform.
The DSM/SCM user ID must have remote passwords to target systems to which it
is Expand connected.
To perform a First Real Apply Build, Initial Build Apply Bypass (FRABIBAB), the
DSM/SCM user ID must be the super ID (255,255). Otherwise, you might not be
able to start DSM/SCM after the system load.
To change the default DSM/SCM user ID, use INITENV with the change option.
Setting Security for Planners
For information about the tasks planners can perform, see
page 4-14. Security information for planners is stored in the host database. Users
configured as planners can have control characters in their passwords as long as
those control characters reside in a standard set available from many 6530 emulators.