When a DBM command or a script with DBM commands is executed in the Database Manager, you receive a reply from the Database Manager.
The communication is in ASCII format. Only in special cases, such as binary file access, do the request and reply also contain binary data. This makes the replies easy to read on the client side. It also largely avoids dependencies on the hardware architecture.
If the DBM command has been successful, an OK message is given in the following format:
The character string OK is the first token of the reply. There is an optional explanatory text on the same line.
The reply data is given on the following line. The structure of the reply data depends on the particular DBM command.
An error always starts with the character string ERR. The same line may also contain an optional description.
On the first continuation line, the number of the error (<errcode>) and a relevant text (<err_description>) can be included.
See also: Messages
If the system has the error number and relevant text of a subcomponent (for example, runtime environment or operating system), these are output as <sub_code> and <sub_description>.
Any additional information follows in the <extended_description>. Special cases in which the <extended description> has a structured format are described with the respective DBM commands. You will find an explanation of individual reply fields there.
Database Manager Internal Error:
-24979,ERR_XPNOTFOUND_CN00 : parameter not found
Error in the Runtime Environment:
-24994,ERR_RTE_CN00 : runtime environment error
3,cannot access PARAM file 
Error in Analysis of Default Parameter Files:
-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