Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
Adabas Transaction Manager Messages and Codes - Software AG ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Subcode Meaning<br />
25<br />
26<br />
28<br />
29<br />
31<br />
32<br />
33<br />
34<br />
35<br />
36<br />
37<br />
38<br />
39<br />
40<br />
41<br />
A comm<strong>and</strong> was sent from an Event Replicator Server to an <strong>Adabas</strong> nucleus, but<br />
the <strong>Adabas</strong> nucleus is not running with ADARUN REPLICATION=YES.<br />
An attempt was made by an <strong>Adabas</strong> nucleus to connect to an Event Replicator<br />
Server when the target of the message is actually another <strong>Adabas</strong> nucleus, not an<br />
Event Replicator Server.<br />
A replicated utility may not be executed for a replicated file when the <strong>Adabas</strong><br />
nucleus is running in single-user mode.<br />
An error occurred during a connection attempt by an Event Replicator Server<br />
database. Ensure that you are trying to connect to another <strong>Adabas</strong> nucleus <strong>and</strong> not<br />
an Event Replicator Server <strong>and</strong> try again.<br />
API file delete not permitted: not API loaded.<br />
An attempt was made to update a replicated file in single-user-mode. Replicated<br />
files can be updated only in multi-mode; replication is not supported in single-mode.<br />
However, a nucleus with replication support can be started in single-mode for<br />
maintenance purposes.<br />
A shared hold status request (with comm<strong>and</strong> option 3 set to "C", "Q", or "S") is not<br />
allowed for a comm<strong>and</strong> with prefetch (comm<strong>and</strong> option 1 set to "P").<br />
On open systems, the comm<strong>and</strong> option "S" is not allowed for an S9 comm<strong>and</strong> with<br />
a non-blank Additions 4 field.<br />
On open systems, the comm<strong>and</strong> was rejected by user exit 11.<br />
The comm<strong>and</strong> cannot be executed with the nucleus parameter NT=1.<br />
The descending option "D" is not allowed for the comm<strong>and</strong>.<br />
On mainframe systems, a shared hold status request (comm<strong>and</strong> option 3 is set to<br />
"C", "Q", or "S") is not allowed for a non-ET user.<br />
On open systems, a shared hold status request (comm<strong>and</strong> option 3 is set to 'C', 'Q',<br />
or 'S') is not allowed for a non-ET user.<br />
A shared hold status request for a sequential read comm<strong>and</strong> (comm<strong>and</strong> option 3 is<br />
set to "Q") is not allowed for an L4 comm<strong>and</strong> without the N-option, nor is it allowed<br />
for an S4 comm<strong>and</strong> without a comm<strong>and</strong> ID (CID) or with an ISN buffer length other<br />
than 4 bytes.<br />
A shared hold status request for a sequential read comm<strong>and</strong> (comm<strong>and</strong> option 3 is<br />
set to "Q") is not allowed for a comm<strong>and</strong> with a multifetch (comm<strong>and</strong> option 1 is<br />
set to "M" or "O"). Also, a shared hold status request (with comm<strong>and</strong> option 3 set<br />
to "C", "Q", or "S") is not allowed for a read comm<strong>and</strong> with prefetch (comm<strong>and</strong><br />
option 1 is set to "P").<br />
A keep-in-shared-hold-status request (with comm<strong>and</strong> option 3 set to "H") is not<br />
allowed for an ET or BT comm<strong>and</strong> with multifetch or prefetch (comm<strong>and</strong> option 1<br />
is set to "M" or "P").<br />
A request to read the next portion of a LOB value (comm<strong>and</strong> option 2 is set to "L")<br />
is not allowed for an L1/L4 comm<strong>and</strong> with multifetch (comm<strong>and</strong> option 1 is set to<br />
"M" or "O") or prefetch (comm<strong>and</strong> option 1 is set to "P").<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
<strong>Adabas</strong> Response <strong>Codes</strong><br />
65