Gasboy CFN III Manager Manual V3.6 - Manual (Page 229)

MDE-4871 CFN III Manager’s Manual for Windows® XP Embedded - Version 3.6 · August 2010 Page 21-3
What Conditions can be Specified for Cron Automatic Cron Commands
Restart Cron Entry
A cron entry that begins with an exclamation mark (!) will be executed in the event of a system
crash. The format of a restart cron entry is:
! [-]command
The exclamation mark is all that is required to specify this condition. Remember to leave a
space between the exclamation mark and the command. There must be only one restart cron
entry. If there is more than one restart cron entry, only the first one will be executed.
The optional hyphen (-) before the command name suppresses output to the printer. This
allows the command to execute when someone is logged on to the command terminal. Will
display RESTART in the When column of P CR output.
Uses of the Restart Cron Entry
System crashes are unlikely and must be reported to your field service representative. You can
use restart cron to save diagnostic information after a crash. Then you can restart the site
without taking the chance of losing information that could help your service technician
diagnose the cause of the crash.
[P:]* TYPE CRASH.CMD
↵
* to be executed by cron after a crash
disable history
log message -- Saving Crash Log --
* the following commands save diagnostic information
* in a disk file
enable dump;a CRASH.LOG
print date
print tip
print diagnostics 1
print history 80-
* the following command restores reconstructed
* tables from BACKUP.DTA
* use only if you keep current backups
* of system data
restore reconstructed except sales transactions from BACKUP.DTA
print monitor
* the following command restarts the site
* after a severe crash
* use RUN without options to restart site only
* if crash was not severe
run
echo ------------
disable dump
log message -- Restarting Site --
enable history
[P:]*
Below is an example of a restart command file to use with cron. This command-file example
appends the diagnostic reports to the end of a file called CRASH.LOG, which can be inspected
or printed later.
Since circumstances surrounding crashes and reboots vary, be careful in designing command
files intended to execute after these events, so that the benefit of having operations resume
automatically is balanced against the risk of not checking out the system before allowing
customers to get fuel.