Reply Format

Reply Format


Normally communication is in ASCII format. Only in special cases, such as binary data access, do the request and reply also contain binary data.

This ensures that the replies on the client side can be easily read. It also largely avoids dependence on the hardware architecture.

Successful Reply

If the request is successful, an OK message is given in the following format:

OK[,]
[]

The character string OK is the first token of the reply. There is an optional explanatory text on the same line. The meta character stands for a line feed.

The reply data is provided after the line feed. The structure of the reply data depends on the concrete DBM command.

Error Message

ERR[,]
[,
[,]
[]]

An error always starts with the character string ERR. The same line may also contain a description.

On the first continuation line, the number of the error () and a relevant text () can be included

If the system has the error number and relevant text of a subcomponent (for example, runtime environment or operating system), these are transferred as and .

Possible additional information follows in the . Special cases in which the has a structured format are described with the relevant DBM commands.

Example

Internal Error of the Database Manager:

ERR
-24979,ERR_XPNOTFOUND_CN00 : parameter not found

Error in the Runtime Environment:

ERR
-24994,ERR_RTE_CN00 : runtime environment error
3,cannot access PARAM file [32]

Error when analyzing the description file (see also: Configuring Database Instances):

ERR
-24978,ERR_XPSYNTAX_CN00 : xparam syntax error
16,XPERR_IVSEQ_CN21 : error in IF-ELSIF-ELSE sequence
D:\d628\usr\env\cserv.pcf(60) : ELSE

End of Content Area

No comments:

topics