sam(1M)sam(1M)NAMEsam - HP System Administration Manager (HP SAM)
[ login | ]
The command launches the HP System Management Homepage (HP SMH) program
for performing system administration on the HP-UX operating system. HP
SMH is an enhanced web-based program of HP System Administration Man‐
ager (HP SAM) in the HP-UX 11i V3 release. For more information, see
If the environment variable is set, the Web-based HP SMH is displayed.
If the environment variable is not set, the terminal user interface of
HP SMH is displayed.
The command is deprecated in HP-UX 11i V3 release. HP recommends you
use the command.
recognizes the following options.
Execute SAM with the privileges associated with the specified
login. When used in conjunction with the Restricted
SMH Builder is invoked and initialized with the privi‐
leges associated with the specified login.
You must be a superuser to use this option. See below
for more information.
Invokes Restricted SMH.
This enables the system administrator to assign lim‐
ited privileged user access to SMH functionality. You
must be a privileged user to use this option. See the
section below for more information.
Generally, SMH requires privileged user rights to execute successfully.
However, through the use of Restricted SMH, SMH can be configured to
allow subsets of its functionality to certain non-privileged users or
groups of users.
System administrators access Restricted SMH by invoking SMH with the
option (see above). In Restricted SMH, system administrators may
assign subsets of SAM functionality on a per-user or per-group basis.
When Restricted SMH is used, non-privileged users are promoted to priv‐
ileged users when necessary to enable them to execute successfully.
By default, Restricted SMH executes all applications as privileged
user. However, certain applications, like software distributor have
their own security mechanism and do not follow the Restricted SMH secu‐
rity model. In such cases, the application launched through Restricted
SMH will be executed with the login ID of the user who invokes it.
A non-privileged user who has been given Restricted SMH privileges sim‐
ply executes and sees only those areas the user is privileged to
All the SMH functional areas require the user to be promoted to be a
privileged user in order to execute successfully. SMH does this auto‐
matically as needed.
SMH provides a default set of SMH functional areas that the system
administrator can assign to other users.
Restricted SMH applies only to terminal user interfaces. Restricted
SMH does not apply to Web-based GUI (HP SMH) since HP SMH has its own
roles. For more information, refer to the HP SMH documentation avail‐
able at and the HP SMH product online help system.
SAM Functional Areas
SAM has been replaced by SMH. For more information on the various
functional areas, see smh(1M).
All actions taken by SAM are logged into the SAM log file at The log
entries in this file can be viewed using the SAM utility command (see
samlog_viewer(1)). can filter the log file by user name, by time of
log entry creation, and by level of detail.
Functionality Obsolescence and Changes
The following functional areas of the previous SAM interface have been
removed, changed, or are planned to be obsolete in a future release of
HP-UX. Alternate procedures are listed as appropriate.
· Trusted systems is planned for obsolescence post HP-UX 11i V3
· Backup and Recovery. Use the and commands from the HP-UX system
prompt. You can also use backup tools, such as pax(1), from the HP-
UX command prompt.
· Tape Drives. Add or remove device entries by editing the file or use
and commands from the HP-UX command prompt.
· Terminals and Modems. Use and commands from the HP-UX command
· Uninterruptable Power Supplies.
· Performance Management. Monitor the performance of HP-UX using the
· Process Management. To manage processes for such functions as stop‐
ping, continuing, changing priority, use and
· Routine Tasks. Tasks such as shutting down the system and removing
files that are large, unowned, or core files are handled by and
· Run SAM on Remote Systems. Executing or configuring SAM on remote
systems is no longer needed, because all systems are managed through
HP Systems Insight Manager (HP SIM). For more information on HP SIM,
· Custom applications cannot be added using SAM. Any custom applica‐
tion that needs to be added in SAM must provide its own registration
files. The registration file has a specific format. You can view a
sample registration file from
cannot be run in the background even if the environment variable is set
from HP-UX 11i V3 release.
The Disks and File Systems area of SAM does not display or configure
all the types of devices when the legacy mode of mass storage stack is
was developed by HP.
SEE ALSOsamlog_viewer(1), evweb(1M), fsweb(1M), hpsmh(1M), kcweb(1M),
ncweb(1M), parmgr(1M), pdweb(1M), secweb(1M), smh(1M), smhstartcon‐
fig(1M), ugweb(1M), intro(7).
TO BE OBSOLETED sam(1M)