Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
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 />
Response 48<br />
Origin<br />
Mainframe <strong>and</strong> open systems<br />
Explanation An error occurred during the processing of a comm<strong>and</strong> such as OP or N1. Refer to the<br />
hexadecimal subcode that appears in the low-order (rightmost) two bytes of the ACB's<br />
Additions 2 field or in the ACBX's Error Subcode (ACBXERRC) field.<br />
78<br />
Subcode<br />
1<br />
2<br />
3<br />
5<br />
6<br />
8<br />
9<br />
10<br />
11<br />
13<br />
14<br />
15<br />
16<br />
17<br />
18<br />
19<br />
Meaning<br />
File(s) not available at open time. This is the default message displayed with this<br />
response code if another subcode is not provided.<br />
A specified file is locked against the requested use.<br />
A specified file is currently in conflicting use.<br />
A utility cannot start because an online save operation is in progress.<br />
A utility requiring exclusive database control cannot start because an online save<br />
operation is in progress.<br />
A utility that requires exclusive database control cannot start because the user<br />
queue is not empty.<br />
The user ID specified in the open (OP) comm<strong>and</strong> is already in use by another user.<br />
An EXU/EXF/UTI lock was requested in the open comm<strong>and</strong>, but the file is currently<br />
in the file list of a user in UPD/EXU/EXF/UTI status.<br />
An EXF/UTI lock was requested in the open comm<strong>and</strong>, but the file is currently in<br />
the file list of a user in ACC status.<br />
A nonprivileged user issued an open (OP) comm<strong>and</strong> to a nucleus in UTIONLY<br />
(utilities only) status.<br />
Online file save attempting to run on an advance-locked file.<br />
UPD/ACC open attempted against advance-locked file.<br />
A file requested for an online utility (<strong>Adabas</strong> Online System or ADADBS) or an E1<br />
program refresh is currently being used.<br />
ACODE or WCODE was specified in the record buffer on the comm<strong>and</strong> but the<br />
nucleus was not activated with UES support.<br />
A specified file is locked against the requested use <strong>and</strong> is advance-locked. The data<br />
in the file is not accessible. This can happen if a utility aborts or an autorestart fails.<br />
On mainframe systems, this means that a second comm<strong>and</strong> was issued by a user<br />
who is participating in a two-phase commit (preliminary ET completed; final ET<br />
outst<strong>and</strong>ing) or whose transaction has been heuristically terminated.<br />
On open systems, this means that the index of the specified file is not accessible.<br />
This can happen if a utility aborts or if the index has been disabled by ADAREC<br />
REGENERATE or an autorestart.<br />
The file number is zero or is greater than the maximum number of files allowed<br />
for the database (based on the MAXFILES parameter setting when the database<br />
was defined using the ADADEF utility).<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language