Gasboy SiteOmat Maintenance Manual - Manual (Page 193)

189 SiteOmat Setup and Maintenance Manual – MDE 4817G
8-4.2.2. Date/Time Stamp and Thread ID
All log file entries begin with a date and time stamp, and the id of the process thread that generated
the log.
A thread is a unit of code execution that performs a specific task. Thread runs in parallel, each
thread has an ID. SiteOmat uses threads for various operations. For example communication with
peripheral devices such as pumps and TLS each done in its own thread. In log files the thread id
that issues the log line is printed. Using this ID it is possible to track execution of a specific thread
or logic. When examining the logs, it is common to follow the logs of a particular thread through
the logs, and ignore other threads.
8-4.2.3. Locating Object ID
Log files often contain references to objects in the database, e.g. equipment objects such as a pump
or an OPOS.
As discussed earlier, the id of an object alone is not enough to identify it. Since an id is only unique
within a particular table, it is also necessary to know what type of object we are talking about.
The device types in the log files are usually symbolic, rather than numeric. The list of device types
is listed in the section describing the devices table in the DATA database.
The log files always contain explicit or adequate contextual information to identify the type of
object that an id refers to.
8-4.3. Critical log file
When SiteOmat starts, a log file called critical.log under /usr/local/Orpak/log is started.
Every time SiteOmat start, it generates inside the file the following:
-------
FCC Critical Logger started
Presented: O:(opos) T(tag) or V:(vit) T(tag) or M:(mitag) T(tag)
Preset-> APS: (tag) atg=(mean)|(ext_tid)|(coupon)|(shift) P(pump) N(nozzle)
L(limit) T(type)
Non-preset-> ANPS: (tag) atg=(mean)|(ext_tid)|(coupon)|(shift) P(pump) N(nozzle)
L0 T(none)
TX (tag) P(pump) N(nozzle) Q(quantity) S(sale)
Log: critical.log started
This describes the 4 types of log lines:
Presented – shows where the tag/mean was presented for authorization, and shows the device name
in parentheses.
Preset – shows pre-pay authorization for specified data with specified limits.
Non-preset – shows similar data for post-pay transactions.
TX – shows completed transaction data.