Sponsored Content
Operating Systems HP-UX HP-UX 11.11 SAM no longer displaying configurable parameters Post 32942 by sjmolloy on Wednesday 11th of December 2002 05:34:00 AM
Old 12-11-2002
Bug Resolution

Sorry for delay in replying.
Finally got this sorted.
It was the patch level on SAM!!!
We had to remove some patches.
Also, manner in which security rules are enforced on us is being reviewed.
Thanks for all the help.
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SAM file

I am having a problem on an HP box, where I am being told that there are too many open files. I am also being told I need to change a SAM file. Could some help me understand what a SAM files is and what it is used for. Thanks. (2 Replies)
Discussion started by: kristian
2 Replies

2. HP-UX

help on sam

hi, any idea how to get more info on the usage, unix equivalent of sam in hp-ux? thanks (7 Replies)
Discussion started by: yls177
7 Replies

3. UNIX for Advanced & Expert Users

HP-UX Restricted SAM

I am having trouble getting restricted SAM to work by allocating Privileges to a "group". I can make it work by allocaing to the userid's, but would preferre to use the "group" option. Running B.11.11 Tried the following.... 1) Created a user group in /etc/group first 2) Used the... (1 Reply)
Discussion started by: Andrek
1 Replies

4. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

5. UNIX for Dummies Questions & Answers

Trouble displaying parameters passed into a for loop

#!/bin/bash function check_num_args() { if ; then echo "Please provide a file name" else treat_as_file $* fi } function treat_as_file() { numFiles=$# for((i=1;i<=$numFiles;i++));do echo $i ... (3 Replies)
Discussion started by: kikilahooch
3 Replies

6. Programming

C++ problem displaying parameters using dOxygen

I have written some C++ code with documentation code for dOxygen as below. However the parameters are not showing up. /// \file /// /// #ifndef __VECT2_HH__ #define __VECT2_HH__ #include <iostream> #include <assert.h> #include <cmath> #include "common.hh" ... (0 Replies)
Discussion started by: kristinu
0 Replies

7. HP-UX

HPUX 11.23 - Sam and Smh.

I've just been on an HP Training Course for HPUXv11.31 and found out about the gui / web for SMH. I never did a course on HP11v23. On our two servers here in the UK that run 11.23 I'm pretty sure that when I typed in "sam" on the command line it went to a sort of smh. (There was a message saying... (2 Replies)
Discussion started by: markp1965
2 Replies
sam(1M) 																   sam(1M)

NAME
sam - HP System Administration Manager (HP SAM) SYNOPSIS
[ login | ] DESCRIPTION
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 Manager (HP SAM) in the HP-UX 11i V3 release. For more information, see smh(1M). 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. Deprecation Notice The command is deprecated in HP-UX 11i V3 release. HP recommends you use the command. Options 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 privileges 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 limited privileged user access to SMH functionality. You must be a privi- leged user to use this option. See the section below for more information. Restricted SMH 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 privileged 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 security 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 simply executes and sees only those areas the user is privileged to access. 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 available 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). SAM Logging 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. o Trusted systems is planned for obsolescence post HP-UX 11i V3 release. o 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. o Tape Drives. Add or remove device entries by editing the file or use and commands from the HP-UX command prompt. o Terminals and Modems. Use and commands from the HP-UX command prompt. o Uninterruptable Power Supplies. o Performance Management. Monitor the performance of HP-UX using the commands and o Process Management. To manage processes for such functions as stopping, continuing, changing priority, use and o Routine Tasks. Tasks such as shutting down the system and removing files that are large, unowned, or core files are handled by and o 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, see o Custom applications cannot be added using SAM. Any custom application 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 WARNINGS
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 disabled. AUTHOR
was developed by HP. SEE ALSO
samlog_viewer(1), evweb(1M), fsweb(1M), hpsmh(1M), kcweb(1M), ncweb(1M), parmgr(1M), pdweb(1M), secweb(1M), smh(1M), smhstartconfig(1M), ugweb(1M), intro(7). at TO BE OBSOLETED sam(1M)
All times are GMT -4. The time now is 12:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy