The names file configuration is exactly the same on VMS, MVS and Unix systems as on VM nodes. The processing of the names file is performed by a FORTRAN program, FATSEND, which uses the CERN program library routine NAMEFD and the updates are transferred using the CSPACK routines.
For each remote server, a subdirectory should be created. (If the subdirectories are note created, they will be created as required by the server). In the case of the example names file shown below, we would have the subdirectories .TOD0SG01 , .TOD0SF01 and so on (VAX/VMS systems). The FATMEN server copies all updates into each of these subdirectories and the program FATSEND copies the updates to the specified remote nodes, using either TCP/IP or DECnet, and deletes those files that are successfully copied. DECnet transfers are only possible between VAX/VMS systems.
On MVS systems, the protocol BITNET is also valid for transmission of updates to remote VM systems. This is done using the TSO transmit command.
An example names file is shown below.
:nick.FATSERVERS
:list FMSGI FMVAX
:nick.FMSGI :userid.fmd0
:node.d0sg01
:protocl.tcpip
:dir1//fnal/d0/*
:receive.yes
:queue:USR$ROOT37:[FMD0.TODO]
:nick.FMVAX :userid.fmd0
:node.d0sf01
:protocl.tcpip
:dir1//fnal/d0/*
In this example, servers connecting the the machine D0SG01
will transmit updates in both directions, rather than the
default, which is to send updates only.
This option is useful for the transmission of updates
to a machine that does not accept incoming connections,
as is the case with VAX systems running the UCX TCP/IP software,
the Cray at CERN and MVS systems.
If the tag :queue is specified, the updates are placed in
the specified directory. If not, they are placed in the subdirectory
todo of the account that is used to performed the transfer.
If a subdirectory TOVM exists, the FATMEN server will attempt to send all updates via Interlink to CERNVM. This option is only intended for use at CERN.