Configuring servers on VM systems

This is performed by adding entries to the NAMES file of the servers in question. For each remote server one can define up to 16 generic name patterns, each of which may include wild-cards. For more details see the example below. Updates may be sent to remote IBM machines, VAXes connected via Interlink and Unix machines using the CSPACK software.

Note that the default for VM systems is to send the updates using the SENDFILE exec. This can be overridden for individual entries either by sending the updates to a gateway machine, as described later, or by specifying an alternate exec, as for the entry FMVAX.

:nick.FATSERVERS
               :list FMSACLAY FATCAT FMIN2P3 FMRAL FMVAX

:nick.FMVAX
               :userid.fmsmc
               :node.vxcrna
               :DIR1.//cern/smc/dst/*
               :exec.fat2vax

:nick.FMSACLAY
               :userid.fmsmc
               :node.frsac12
               :DIR1.//cern/smc/dst/*
 
:nick.FMIN2P3
               :userid.fmsmc
               :node.frcpn11
               :DIR1.//cern/smc/dst/*
 
:nick.FMRAL
               :userid.fmsmc
               :node.ukacrl
               :DIR1.//cern/smc/dst/*
 
:nick.FATCAT
               :userid.fmfatcat
               :node.cernvm
               :DIR1.//cern/smc/dst/*

In the preceeding example, all updates referring to generic names beginning //CERN/SMC are sent to the server defined by the name FATCAT, whereas only updates referring to names beginning //CERN/SMC/DST are sent to the servers at SACLAY, IN2P3 and RAL. Note the the FMFATCAT account is in fact a gateway into the Unix-world (using the program in PATCH FATCAT in the FATMEN PAM file and that FMVAX is an account of a VAX linked to the IBM via Interlink, but this is completely transparent to the server.

On systems other than CERNVM, updates that are to be sent to non-VM systems should pass via a gateway service machine.

:nick.FATDESY  :userid.R01H1
               :node.dhhdesy3
               :DIR1.//cern/h1/*
               :protocol.mvsjob
               :gateway.fmgate at cernvm

:nick.FATVAX   :userid.fmh1
               :node.vxdesy
               :dir1.//cern/h1/*
               :protocol.tcpip
               :gateway.fmgate at cernvm
               :receive.yes

In the above example, updates destined for FATDESY and FATVAX are not send directly, but pass via an intermediate service machine. wakes up at predefined intervals and transfers any files to the specified remote nodes. In the case of the entry FATVAX, files are also retrieved from the remote system.

Transferring updates to VAX/VMS systems via Interlink

This method should only be used at CERN. For other systems, a gateway service machine should be used. See the description below for setting up a gateway service machine.

Files sent from IBM VM/CMS systems via the Interlink VM-DECnet gateway will arrive in the default directory for the FAL DECnet object, typically

SYS\$SPECIFIC:\lsb FAL\$SERVER \rsb

By default, the files will be named FATMEN.RDRFILE. At CERN a small modification has been made to the Interlink software so that the files arrive as VAXUSER.FILENAME_FILETYPE, thus files sent to FMOPAL would be called

FMOPAL.FATMEN_RDRFILE

These files can be copied to the correct directory using the command file FATRL.COM, included in the PATCH DCL of the FATMEN pamfile.