Whenever a screen is started up it will check to see if there is any work to be integrated and if so will start adding the work to the appropriate cards. There is also an option on the main Cross updating menu 'Integrate log file'. If there is work this menu option will be present and can be used.

Each animal is represented by a dot '.' so you will see rows of ...................... appearing on the screen.

As integration takes place the client's record will be locked to enable the update to take place. If either a global lock e.g. Vatbook or client lock occurs the update program will wait indefinitely until the lock is cleared.

This in indicated on the screen by ........ changing to **********

If you see this do NOT just kill the screen - this will leave the log file partially processed and you will have to make manual edits.

However, this does tie up the screen (all other screens are un-affected) and depend on the user selecting an option. You can configure the system so that when x_check run and there is work present the logfile(s) are processed there and then.

With this method where the system will automatically integrate the data WITHOUT you having to do anything. This is NOT switched on by default, as we have found the users generally like to see the integration message to assure them that the cross updating has worked.

Tip: If you have members of staff who don't understand the dot's and just close the terminal window, leaving you with lock files to clear up then switch on background integration.

Background Integration is switched on via an option on the xmenu utilities menu.

Integration and lock files

Whenever cross updating takes place the system will create a lock file to stop the integration program running more than once. Normally, the lock file will be removed when integration is finished. However, if the lock file is not deleted for some reason it will prevent valid future integrations from taking place.

Therefore, the cross updating module attempts to determine whether an existing lock file is valid before it cancels an integration.

If the process that created the lock file is still running then it is assumed that integration is active. A mail message will be sent to whoever is specified in call_info (normally root) and the program will exit, leaving the lock file in place.

If the process is not running then the file being integrated (UUCP.log) will be renamed along with the 'how far have we got' file (v6uucp.log) and the lock file removed. This will allow new work to be processed leaving a copy of the current log. Should this occur, mail will be generated giving you the name(s) of the two files. You should remove the already processed work for the UUCP.log file.

See the FAQ Editing log files for the procedure to correct this.