13.12.2012 Views

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

Adabas Transaction Manager Messages and Codes - Software AG ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Adabas</strong> Response <strong>Codes</strong><br />

60<br />

Subcode<br />

6<br />

7<br />

8<br />

9<br />

10<br />

11<br />

12<br />

13<br />

14<br />

15<br />

16<br />

17<br />

18<br />

21<br />

22<br />

Meaning<br />

On mainframe systems, an E1 (delete record) comm<strong>and</strong> was given without<br />

specifying a valid file number.<br />

On open systems, the file to be created already exists.<br />

The program tried to perform an LF comm<strong>and</strong> on system file 1 or 2.<br />

On mainframe systems, the program tried to access a file that was not listed in<br />

the file list of an open (OP) executed with the R option.<br />

On open systems, \an ET user with a restricted file list <strong>and</strong> ACC = file number<br />

attempted to issue a UPD comm<strong>and</strong>, or a user with a restricted file list attempted<br />

to touch a file that is not in the file list<br />

The file that the program attempted to access is completely locked. This is usually<br />

because the maximum number of logical file extents that can fit into the FCB have<br />

been used.<br />

Action: Reorder, then unlock the file. Continue operation.<br />

The program attempted to access a file which is locked with exclusive EXU status.<br />

An LF comm<strong>and</strong> (read FDT) was run on a file that is not loaded; neither the FCB<br />

nor the FDT exists.<br />

File has been locked with LOCKF.<br />

A file is password-protected <strong>and</strong> the password was specified, but the<br />

corresponding security file is missing (not loaded).<br />

A comm<strong>and</strong> was issued against a LOB file. Comm<strong>and</strong>s involving LB fields should<br />

be directed against the associated base file, not the LOB file.<br />

A file is being loaded so its information is temporarily unavailable.<br />

On mainframe systems, an attempt was made to perform an update (e.g. A1, E1,<br />

N1/2) against a file loaded with the attribute RPLUPDATEONLY=YES.<br />

On open systems, the file was locked by ADAOPR.<br />

An attempt was made to perform an update (e.g. A1, E1, N1/2) against a file loaded<br />

with the attribute READONLY=YES.<br />

File has been locked with ALOCKF.<br />

On mainframe systems, there was not enough space for encoding elements (ECSE).<br />

On open systems, a two-byte file number was used against a lower version<br />

database that does not support large file numbers.<br />

On mainframe systems, the required ECS objects needed for conversion between<br />

user <strong>and</strong> system data representation could not be loaded.<br />

On open systems, the file control block (FCB) is invalid (corrupted).<br />

<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!