IBM HPSS User Manual
![IBM](https://files.manualsbrain.com/attachments/f70d337d03c66895b7a6fbe0e6de3554f47d7dd3/common/fit/150/50/fb4e568062ca4d0154259807170f4c71f2c7aafa861a4d9a0eb3af958af4/brand_logo.png)
PFTP Client Interfaces Stanza Example:
; PFTP Client Interfaces = {
# PFTP Client Host Name(s)
; water.clearlake.ibm.com water = {
# Next Specification is the PFTP Daemon Host
# water has 3 specific interfaces that can talk
# to the HPSS Movers associated with the PFTP
# Daemon Host "water", as well as various
# interfaces of the form 192.2.nnn.nnn
; water.clearlake.ibm.com water = {
# Interfaces on the host specified as the Client Machine
; 192.94.47.227
; 192.175.14.35
; 192.222.197.1
; eth*
; }
# water has ONLY 1 interface that can talk to the HPSS
# Movers associated with the PFTP Daemon Host "sneezy"
; sneezy sneezy.clearlake.ibm.com = {
; 192.94.47.227
; }
# Use the default water interface, 192.100.101.1, to talk
# to any other PFTP Daemons.
; Default = {
; 192.100.101.1
; }
; }
; sneezy sneezy.clearlake.ibm.com = {
; larry larry.clearlake.ibm.com = {
; 192.94.47.226
; }
; sneezy sneezy.clearlake.ibm.com = {
; 192.94.47.226
; }
; }
# For all other Client Hosts - This allows a single HPSS.conf
# file to be available using a common files system. This is
# ONLY useful for cluster systems that specify "Common"
# interfaces for multiple # nodes of the cluster (I/O Nodes)
; Default = {
# Client Host Name
; water water.clearlake.ibm.com = {
; 134.253.14.227
; }
; }
; }
D.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 transfer process(es) with
these child processes. The Multinode Table stanza is used to specify what remote hosts are to
perform the “pseudo” PFTP Client child processes functions.
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 transfer process(es) with
these child processes. The Multinode Table stanza is used to specify what remote hosts are to
perform the “pseudo” PFTP Client child processes functions.
Table 14. Multinode Table Stanza Fields
HPSS Installation Guide
July 2008
Release 6.2 (Revision 2.0)
266