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.
Subcode Occurrence<br />
Location<br />
29<br />
50<br />
51<br />
52<br />
53<br />
54<br />
55<br />
58<br />
101/201<br />
UNIX<br />
platforms only<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
mainframe<br />
systems<br />
Description<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
IPC resources exist, but the<br />
database server was not active.<br />
At comm<strong>and</strong> completion RSP148<br />
was set but without a subcode. This<br />
subcode is set to indicate the<br />
comm<strong>and</strong> was processed by the<br />
target.<br />
The comm<strong>and</strong> router found no<br />
suitable target. The target was<br />
determined not to be an <strong>Adabas</strong><br />
Cluster Services or <strong>Adabas</strong> Parallel<br />
Services database.<br />
The comm<strong>and</strong> router found no<br />
suitable target. The target was<br />
determined to be an <strong>Adabas</strong><br />
Cluster Services or <strong>Adabas</strong> Parallel<br />
Services database.<br />
The comm<strong>and</strong> router found a<br />
suitable target but the target<br />
became inactive while queuing the<br />
comm<strong>and</strong>.<br />
When the caller attempted to<br />
retrieve the results of a completed<br />
comm<strong>and</strong> the target was no longer<br />
active.<br />
The target became inactive while<br />
the caller was attempting to<br />
retrieve the results of a completed<br />
comm<strong>and</strong>.<br />
An error occurred while POSTing<br />
the <strong>Adabas</strong> nucleus ECB after<br />
queuing a comm<strong>and</strong>.<br />
Set in SVCCLU when a specifically<br />
designated local nucleus is not<br />
available for a physical call. The<br />
201 subcode appears when this<br />
subcode is set on a remote node.<br />
Action<br />
<strong>Adabas</strong> Response <strong>Codes</strong><br />
Issue the comm<strong>and</strong> showipc<br />
-kd , restart the<br />
nucleus, <strong>and</strong> reissue the<br />
comm<strong>and</strong>.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
This may be seen if the nucleus<br />
is terminating. Otherwise<br />
contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
Contact your <strong>Software</strong> <strong>AG</strong><br />
support representative for<br />
assistance.<br />
135
Change language