Messages

---

A Reference to Pervasive.SQL Messages

This chapter describes the messages that can be returned to Pervasive.SQL users. The messages are listed in alphabetic order by category. Some of the messages listed in this chapter may be generated by utilities that are not part of your Pervasive.SQL distribution.

Messages are not the same as status codes (see Chapter 1-Status Codes.). Messages are returned to end users by utilities or specific components and generally begin with a prefix and a number. For example: MKDE-16: There is insufficient memory to load the MicroKernel Database Engine.

Some messages refer to status codes, as in the following example:

Error Accessing INDEX.DDF. Status = nn 

The status code is tied to a particular component, and it varies depending on the nature and source of the error. The value for nn or xx refers to a software-supplied number (for example, a status code, operation code, or number of records) and xxxx refers to a software-supplied name (for example, a filename, a data type or key type, or a command).

The messages are arranged according to the originating component. The table below lists the prefixes for each type of message.

 
Table 2-1 Message Groups

Prefix	Type of Code
(none)	Generic Messages
BREQUEST	MKDE Requester Messages
BREQUTIL	Requester Utility Messages
BROUTER	Message Router Messages
BSPXCOM	SPX Communications Module Messages
BTCPCOM	TCP/IP Communications Module Messages
BUTIL	Maintenance Utility Messages
MKDE	MicroKernel Database Engine Messages
NWBSRVCM	NetWare Server Communications Manager Messages