IBM Hub/Switch Installation Manual page 529

when it starts, and hpss.def is used to override the settings in s2_defaults.def. Some of the
user-preference features which can be set in a defaults file are:
1. Whether or not popup items on windows cause a beep tone.
2. The volume of the beep which is issued when the user tries to type beyond the end of a
field.
3. The text entry foreground and background colors.
4. The blink rate for blinking fields.
Again, consult the comments for more information. For a complete list of default options,
consult s2_defaults.def, or see the documentation on the set-default command in Chapter 4 of
the Sammi Version 4.0 Runtime Reference.
The HPSS administrator may, if desired, modify hpss.def to change the site defaults.
Alternatively, new defaults files may be created for individual users or groups of users. This
would also involve the user authorization file and login command files (see below). The names
of new defaults files must end in ".def", and must reside in /opt/hpss/sammi/hpss_ssm
directory.
Any changes to defaults beyond the most innocuous user-preference items should be done
with great care.
• Each user that logs into SSM has a Sammi command file executed automatically. The
command file for each user is specified in /opt/hpss/sammi/hpss_ssm/
user_authorization.dat, as the fifth field in each user entry. The default is hpss.cmds,
which is in the <Sammi installation directory>/bin directory. All command files are
expected to be in that directory, but they can be placed elsewhere by specifying the full path
name of the file in user_authorization.dat.
The default command file loads the SSM "defaults" file (described above). If desired, the HPSS
administrator can modify hpss.cmds, or create new command files for individual users or
groups of users. A new command file might be created, for example, to load an alternate
defaults file for a special group of users. Or a "redefine-keys" command might be added to
load an alternate keyboard definition file for a particular user (see below).
If a new command file is created, user_authorization.dat will need to be edited to assign the
file to selected SSM users.
Sammi command files must contain nothing but valid Sammi commands, as documented in
the Sammi Version 4.0 Runtime Reference.
• The file SAMMI contains X defaults data important to the correct execution of Sammi. SSM
users need a copy of this file in their home directories on all hosts where they will run
Sammi (which may not be the same as the hosts where they display the windows).
Normally, the hpssuser utility copies a SAMMI file to the home directory of each new SSM
user which it creates, but that applies only to the host where hpssuser is executed. The
template copy of SAMMI is in /opt/hpss/config/templates/SAMMI.template.
The SAMMI file is customizable to some extent, and each SSM user is free to modify his own
copy. These modifications should be kept to a minimum, however, or there may be severely
adverse effects on the appearance of the SSM windows.
HPSS Installation Guide
Release 4.5, Revision 2
Appendix F
September 2002
Additional SSM Information
529