Chapter 3 System Preparation
162 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
settings for the size of the send and receive pool buffer size, which have had an effect on
throughput. It is recommended that the available interface specific documentation be referenced
for more detailed information.
Theanticipated load should also be taken into account when determining the appropriate network
option settings. Options that provide optimal performance for one or a small number of transfers
may not be the best settings for the final multi-user workload.
3.7.1 HPSS.conf Configuration File
The HPSS.confconfiguration file contains tuning options to be used by HPSS clients and servers.
The HPSS.conf file may also contain options used by non-HPSS applications. Application
developers are asked to please observe the “Reserved for Future Use” components specified in
Section 3.7.7.
The HPSS.conf configuration file is located in the directory named by either:
• The HPSS_PATH_ETCenvironment variable,
• the directory/var/hpss/etc, or
• the directory/usr/local/etc
in that order (except for when accessed by the Authentication Managers -Realms to DCE Cell
Mappingsstanza). Ifthe file is not present or no matching entry is found, the Parallel FTP Client,
Client API, and Mover will use system defaults.

General HPSS.conf Rules:

• Lines are comprised of comments,blank lines,simple specifiers,specifiers andvalues - “abc =
def”, orcompound specifiers and terminators - “def = { …}.”
• Only four levels of specification are allowed: Stanzas, SubStanzas, Sections, and
SubSections.
• SubStanzas may only exist in Compound Stanzas. Sections may only exist in Compound
SubStanzas, and SubSections may only exist in Compound Sections.
• No line may exceed 128 characters, including the “= {“.
• Comments may be included by entering either a semicolon (“;“) or a pound sign (“#”) as
the first non-white character in a line. Use of either of these characters other than as the
first character will not be interpreted as a comment (It will be interpreted as part of the
specifier or value!).
• Indentation is optional but is encouraged (assists in diagnosis).
• Closing braces (“}“) must be used to terminate opening braces (“{“).
• Spaces before or after the equal sign (“=”) are optional.