The file /etc/call_info controls how the sending and checking scripts work. This appendix lists all the possible options that can be specified.

See the various Cross updating scenarios for examples of the options.

SITES	This should be set to a list of the sites this system talks to.
LOGFILE	You will NOT normally need to change this option. This is the logfile that contains all the clinical work that is sent between machines. See Scenario two for an example of when you would need to change it.
FLAGS	These are 'options' that are passed over to UUCP when the job is submitted. You must always have -C in there, the only other change you may need here is to add (or remove) the 'r' option e.g. -Cr. The 'r' option tells uucp to NOT to try to send straight away, the work will be queued and next time the m/c's talk (or uudemon.hour runs) the work will be transferred. If you want the m/c's to try when x_send runs then remove the 'r' from here.
EXTRA	You may want to transfer specific files each time the system talk e.g. contact numbers, phone list, rota's etc. You can specify them here. The files MUST reside in the main data directory. They will ALWAYS be sent if specified here, if you only want them sent if they have changed (or live in a sub-folder) then see the SUBFILES option.
VETSYS	The location of Premvet Data on THIS machine. Use 'vet -V' if you are unsure of where this is (usually /u/vetdata)
DIRECTORIES	Which sub-directories to check for changed files e.g. animal attachments. If not specified it will default to sheets and graphic. If you do specify any thing here you must include at least 'sheets' in addition to what you enter if you want the normal attachments to transfer.
MIRROR	When running in a mirrored situation (See Scenario 3) this is where the remote sites data lives on THIS server.
REMOTE	When performing syncronisation over the network to a stand by server (superseded - see DIST).
DIST	When performing syncronisation over the network to a stand by server (See Scenario 5) this is the name of the backup server.
MAILTO	The mail address of the user to notify if there have been any cross updating related errors. If it is not specified it will be mailed to 'root' on the local machine. You can set this to ANY valid mail address - it does NOT need to be a user on this server.
PDSASEND	Applies to Mirror situations (See Scenario 3) and should contain a list of sites that you want additional files sent to. This is used by the sending program.
PDSAEXTRA	This applies only to mirror sites (See Scenario 3) and is a list of the 'extra' sites you want the checking program to look at for incoming work.
SUBFILES	Similar to the EXTRA option, this contains a list of files you want to send to the remote sites. The difference between this and EXTRA is: the file(s) will only be sent if they have changed recently, or the file resides in a sub-directory e.g. to send over the file text/phone.txt and text/rota.txt add SUBFILES="text/phone.txt text/rota.txt"
SOURCE	Where do the Premvet Programs live on THIS server. You will not need to change this option - if it is not specified it will default to /u/source.
XLOG	The system keeps 'log' of all actions the sending and changing programs carry out. This is normally /usr/utilities/XLOG, if you are using multiple configuration files (See Scenario 6) you can have a log file per config.
DUMP	Specific to Scenario 7, this allows you to alter where work is sent/checked from to avoid a clash of work from other copies of cross updating running on the same server.
CONFIG_FILE	Specific to Scenario 7, this allows you to have cron running the sending and checking programs once but the utilities will run multiple copies of cross updating on the same server.
FORWARD	In Scenario 4 we have a remote site being responsible for sending work via the mirrored server. This option is set ON THE MIRROR to the name of the remote system - the mirror will automatically forward files from the remote to the other sites.