IBM Hub/Switch Switch User Manual


 
Chapter 6 HPSS Configuration
HPSS Installation Guide September 2002 267
Release 4.5, Revision 2
Server Subtype The subtype of the
selected server. Most
servers do not have
subtypes.
This field is filled in with
the server subtype
selected by the user as
part of the window’s
selection. It is not
changeable.
Server subtype
selected by the user
(e.g. tape); none for
servers that do not
have subtypes.
Server CDS Name The name of a Cell
Directory Service (CDS)
directory in which a server
creates additional CDS
objects and registers its
endpoint information.
Every server must have a
different directory.
Any legal CDS directory
name <128 bytes is
permitted. The directory
must exist when this
particular server is started.
Based on
$HPSS_CDS_PREF
IX and a
modification of the
descriptive name
from the Server
Name field. All
characters in the
descriptive name
except letters,
numerals, and
periods are changed
to underscore to
insure that the name
is valid for DCE.
Advice:
(1) Different names must be used for each server. If this is not observed, servers
will have trouble contacting each other, or will talk to different servers than
anticipated.
(2) The directories must be writable by the process that uses them.
(3) It is useful to have a convention for naming these directories. For example, all
directories might be subdirectories of a common directory such as /.:/hpss. The
directories might be named by the role that the corresponding server plays in the
CDS—e.g., /.:/hpss/disk_ss1 and /.:/hpss/tape_ss1 might be the names used by
two instances of the Storage Server.
(4) If there are multiple Startup Daemons, Movers, and Log Clients running, use
names that reflect the hosts they are running on. For example, a Startup Daemon
running on a host named timelord might be named /.:/hpss/hpssd_timelord.
(5) HPSS does not make any assumptions about which names are used.
(6) SSM creates the specified CDS directory and the associated CDS Security
Object when the server is configured from this window. The parent directory (e.g.
/.:/hpss) must already exist, otherwise the creates will fail. See the discussion
following this table for the particular ACLs.
Table 6-3 Basic Server Configuration Variables (Continued)
Display Field Name Description Acceptable Values
Default
Value