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

On the successful reply to a request an OK message is given with the following format:

OK[,<description>]<NL>
[<answer>]

The character string OK is the first token of the reply. There is an optional explanatory text on the same line. The meta character <NL> 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 Server command.

Error Message

ERR[,<description>]<NL>
[<errcode>,<errdescription><NL>
[<subcode>,<subdescription><NL>]
[<extended description><NL>]]

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

The number of the error (<errcode>) and a relevant text (<errdescription>) can be included on the next line (See also: Messages: SAP DB 7.2 and 7.3).

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

Any additional information comes in the <extended description>. Special cases in which the <extended description> has a structured format are described with the relevant DBM Server commands.

Internal error of the DBM Server:

ERR
-24979,ERR_XPNOTFOUND_CN00 : parameter not found

Error in 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