Remote RZ databases may be complete replicas of the central database or contain merely a subset of the information. The level of information in these remote copies is determined by an entry in a distribution list. When a server receives an update, it matches the pathname against a distribution list, and forwards the update to remote servers if the pathname matches. Thus, a server on LEPICS, the L3 IBM system in building 513 at CERN, may wish to receive information on all files in //CERN/L3, whereas a server on the ALEPH Wisconsin VAXcluster may only wish to receive information on files in //CERN/ALEPH/DST/WISC.
Up to 16 generic name patterns may be specified for each FATMEN server.
Should the generic name of the update match any of these patterns, the
update is forwarded to the remote server. The example below shows an entry
for a remote FATMEN server at node UKACRL (RAL in the UK). All entries for
simulated data (SIMD) will be sent to this node, plus all master and team
DST information for real data.
[GENFIL]
Example of a NAMES file entry for the FATMEN servers
:nick FATSERVERS
:list.fats1 fats2 fats3
:nick FATS1
:userid.FMDELPHI
:node.UKACRL
:DIR1.//cern/delphi/simd
:DIR2.//cern/delphi/alld/mdst
:DIR3.//cern/delphi/alld/tdst