PreviousAdvanced Operations Guide (v10) Next

Pervasive PSQL Event Logging

Chapter contents

All Pervasive PSQL components write status and error messages to the same log file. If two or more Pervasive-based applications are running on the same machine, they share a single event log.

The event log is called PVSW.LOG on Windows platforms and event.log on Linux platforms. )

Table 3-1 Platform Event Log Locations
Platform
Default Location for Event Log
Windows
application_data_directory\PSQL\logs
Linux
~psql/bin

Syntax

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

Table 3-2 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 the process ID of the component.
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.


Chapter contents
Book contents

Prev topic: Relational Architectural Overview
Next topic: Error Code Clarification