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 19<br />
Origin<br />
Explanation<br />
Action<br />
Response 20<br />
Origin<br />
Explanation<br />
Action<br />
Response 21<br />
Origin<br />
Mainframe <strong>and</strong> open systems.<br />
An attempt was made to update a file which is either already open for read access or can only<br />
be opened for read access. The leftmost two bytes of ACB's Additions 2 field or the ACBX's<br />
File Number (ACBXFNR) field may contain the file number.<br />
Do not attempt to update a file with read-only access.<br />
Mainframe <strong>and</strong> open systems.<br />
One of the following invalid values was used for a comm<strong>and</strong> ID value:<br />
■ Binary zeros<br />
■ Blanks<br />
■ The high-order byte contains the hexadecimal value "FF", but there is no automatic comm<strong>and</strong><br />
ID generation<br />
■ The three high-order bytes contain the ASCII string "SYN".<br />
Correct the comm<strong>and</strong> ID <strong>and</strong> avoid using any of these invalid comm<strong>and</strong> ID values.<br />
Mainframe <strong>and</strong> open systems<br />
Explanation An invalid comm<strong>and</strong> ID value was detected. One of the following explanations or subcodes<br />
is provided:<br />
62<br />
Subcode<br />
1<br />
3<br />
4<br />
5<br />
6<br />
7<br />
Meaning<br />
The comm<strong>and</strong> ID value was not found in the sequential comm<strong>and</strong> table. Either<br />
this is not an initial call <strong>and</strong> there was no previous initial call, or the initial call<br />
was issued for another file.<br />
The comm<strong>and</strong> ID value specified with the GET NEXT option of an L1/L4<br />
comm<strong>and</strong> was not found or the comm<strong>and</strong> ID value was not found <strong>and</strong> the L3/L6<br />
call was not an initial call.<br />
The comm<strong>and</strong> ID value specified for the L3/L6 comm<strong>and</strong> was assigned to another<br />
Lx comm<strong>and</strong> or the comm<strong>and</strong> ID specified for an L9 comm<strong>and</strong> was assigned to<br />
another Lx comm<strong>and</strong>.<br />
The format buffer with the comm<strong>and</strong> ID used by an Lx comm<strong>and</strong> was created<br />
by an L9 comm<strong>and</strong> <strong>and</strong> is incompatible.<br />
The format buffer with the comm<strong>and</strong> ID used by an L9 comm<strong>and</strong> was created<br />
by an Lx comm<strong>and</strong> <strong>and</strong> is incompatible.<br />
The comm<strong>and</strong> ID value specified for the S8 comm<strong>and</strong> was not found.<br />
The comm<strong>and</strong> ID value specified was assigned to an internal format buffer for<br />
a different file.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>