Error codes during file processing (DMS errors)

If errors occur during file processing and calls to other C runtime routines then error codes are output in the form yxxx in the messages. When they refer to file processing, these are also referred to as DMS errors.

The following inserts are affected:

• &DMSE

• &ERRNO

• &UERRNO

The DMS errors have the following meanings:

y	The first character y denotes the function in which the error occurred. y may have the following values:
	A C D E F G L M O R S W X	Error in loading shared memories into the address space Error in close call Error in signing off from a shared memory area Error in remove call Error in fstat/stat call Error in allocating shared memory Error in lseek call Error in mkdir call Error in open call Error in read call Error in system call Error in write call Error in create call
xxx	The three characters xxx represent, in printable form, the error number which is stored by the operating system in the external variable 'errno'. If necessary, the error number is padded out to the length of three digits with leading zeros. The meanings of the individual error umbers are described in the manuals for the systems and in the errno.h header file.

For example, the error code O002 means that on an attempt to open a file (O=open), the file was not present (2=errno ENOENT).

In addition, the following errors codes can occur:

CONS GPOS	The contents of the file are inconsistent. GPOS means that it was not possible to get the position in the start parameter file stream with fgetpos().
LERR OERR REND RERR WERR LOCK MARK	lseek could not be positioned at the desired point. An attempt was made to open a directory as a normal file. End-of-file reached on reading from a file. Insufficient bytes could be read. Insufficient bytes could be written. The file cannot be written because it is locked. The expected file marks could not be found. The file has probably been destroyed.
USED VERS	The file cannot be written because it is currently being used. The expected version number could not be found. The file may have been destroyed.