Gasboy PC CFN site controller - Manual (Page 14)

PC/CFN Basics Terms to Know
Page 10 MDE-4489 Gasboy® PC/CFN User’s Guide·July 2005
Terms to Know
DB Maintenance
PC/CFN has a database maintenance utility that provides periodic maintenance of your
database which minimizes problems, corrects problems that exist, and generally increases
database performance. This happens in two ways: automatically or on demand.
• Automatic database maintenance occurs after polling (Comm package), or after
processing (Fuel package).
• On demand maintenance is selected from the Utilities>DB Maintenance. (The
rundbmaint.exe file that is run as a result of selecting this button, can also be run from
Windows Explorer, or the Run prompt, in case you need to run maintenance without
running the software.)
The database maintenance process is transparent to you as a user, but what occurs internally is,
a verification check is performed. If no errors are detected, the maintenance process does not
continue. If errors or problems are detected, the process continues to repair the database.
Regardless, after nine verification steps, database maintenance is performed on the 10th
occurrence.
Note: If your site encounters frequent problems, you may wish to have this frequency lowered
to every 2nd occurrence or some other setting. Settings for the database can be adjusted
in the dbmaint.ini file which resides in your Windows system directory. Contact Gasboy
technical service before changing this file.
A log of maintenance activity is available in the file dbmaint.log, which is stored in the
\maintenance directory of your PC/CFN application.
Extra Commands
Extra Commands can be up to ten fuel management system commands, that are executed upon
polling. There are two types, namely global and site-specific:
• Global commands are entered on the Fuel System Types form and are executed at all sites
included automatic polling.
• Site-specific commands are entered on the Fuel Sites form and are executed only at that
site upon polling. Refer to your fuel management system manual, for appropriate
commands. Commands do not require user input.
Fuel Site Transactions
Each time a user attempts to obtain fuel at a fuel site, a transaction is generated. Even if the
user encounters errors while doing this a transaction may be generated. Transactions may also
be generated for such events as a fuel delivery, or dipstick reading. Typically, transactions are
accumulated at your fuel management system at the site. You use a PC package, such as PC/
Fuel or PC/Comm to poll or collect the transactions from the fuel management system.Copy
them onto the PC, and process them according to the procedures of your organization.
Polled raw transactions are written to the PC database and stored as part of the RAWTRANS
or RAWTRANS.DAT file. Transactions that occurred outside of your fuel sites or transactions
from sites that could not be successfully polled by the PC may be entered manually through
the PC package.