Chapter 3 System Preparation
168 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
Default = {
; Client Host Name
water water.clearlake.ibm.com = {
134.253.14.227
}
}
}
3.7.1.3 Multinode Table Stanza
The HPSS PFTP Client normally forks children to provide multiple network paths between the
PFTP Client and the Mover(s). In some instances, it may be preferable to have these processes
(pseudo children) running on independent nodes. In this case, it is necessary to setup a
multinoded daemon on the independent node/host and have the PFTP client initiate the data
transferprocess(es) with these child processes. TheMultinode Table stanza is used to specify what
remote hosts are to perform the “pseudo” PFTP Client child processes functions.
The Multinode Table = { … } stanza contains one or more substanzas specifying the names of the
host initiating the PFTP session.
Each section contains one or more names/IP addresses of remote hosts executing a Multimode
Daemon(multinoded). The remote host must have appropriateentries for the inetd superdaemon
(/etc/inetd.conf and /etc/services) to initiate the multinoded.
The sections may be either a simple section or a valued section. A simple substanza is a single
name/DotNotation IP Address to be used for both “Control” connection and “Data” connection.
The valued substanza is used to specify the name/Dot Notation IP Address for the “Control”
connection (specifier) and the name/Dot Notation IP Address for the “Data” connection (value.)

Table 3-4 Multinode Table Stanza Fields

Configuration Type Description
Stanza (Compound) Multinode Table = {
Reserved Stanza specifier.
Must be terminated with a matching “}”
SubStanza
(Compound) <Local Hostname(s)>
E.g.my_host my_host.my.domain = {
Contains the local hostname(s) this SubStanza represents.
MUST be terminated with a matching “}”
Section <remote_host>
or
<remote_host> = <Dot Notation Interface>
E.g.his_name or his_name = 100.102.103.45
Containsthe hostname in either string format or Dot Notation IP
Address of the host to act as a “Pseudo” PFTP Child. If a
secondaryname is specified after the “=”, the first interface is to
be used for the “control” connection and the second
specification is the interface to be used for the “data”
connection(s) to the Mover(s). If only one value is provided, it
represents both the “control” and “data” connections.