Pervasive.SQL Event Logging

---

With the release of Pervasive.SQL 7 and greater, the MicroKernel message log has been replaced by a new centralized event log. All Pervasive.SQL 7 and later components write status and error messages to the same log file. In addition, if two or more Pervasive-based applications are running on the same machine, they share a single event log.

The event log, called PVSW.LOG (or event.log on Linux), is located in the Windows root directory of each machine that is running a Pervasive-based application (on Linux, it is located in the bin subdirectory of the psql installation directory). This location cannot be changed or customized. In the following table, C: represents the drive letter where your operating system is installed.

 
Table 3-3 Platform Event Log Locations

Platform	Event log location
Windows 98/ME	C:\WINDOWS
Windows NT/2000/XP	C:\WINNT
NetWare	SYS:SYSTEM
Unix	~psql/bin

Syntax

The event log consists of ASCII text messages in a format similar to the following syntax description:

 
Table 3-4 Event Log Fields 

Field	Length (in Bytes)	Contents
Date	10	Automatic date-stamp in mm/dd/yyyy format.
Time	8	Automatic time-stamp in hh:mm:ss format.
Component	15	File name of component returning the error (prefix only, no extension).
Process	8	Instance ID of the component, which is either the process ID of the component or the thread group ID in NetWare.
Process Name	Up to 15	Path and name of the component, truncated to the last 15 characters.
Computer Name	Up to 15	Name assigned to the machine hosting the process, truncated to the first 15 characters.
Type	1	A single character: I for Information, W for Warning, or E for Error.
Category	Up to 10	A component-specific text field. Components are not required to provide a value in this field.
Msg ID	Up to 8	A numeric message identifier that corresponds to a message string within a resource file associated with the calling component.
Message	Up to 1,024	The message text which may be either a string retrieved from a resource associated with the calling component or a text string passed directly from the calling component.

An entry may be followed by binary data in standard ASCII hexadecimal format. There is no limit to the length of the binary data.

Sample Entry

The following shows an example of the type of data contained in the event log.

Date	Time	Component	Process	Process Name
11-04-1997	14:01:05	NTMKDE	000000DD	W3DBSMGR.EXE

Computer Name	Type Category	Msg ID	Message
LABSERVER	I		MicroKernel is using default settings.