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.
<strong>Adabas</strong> Response <strong>Codes</strong><br />
136<br />
Subcode Occurrence<br />
Location<br />
102/202<br />
103/203<br />
104/204<br />
105/205<br />
106/206<br />
107/207<br />
108/208<br />
109/209<br />
110/210<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 />
mainframe<br />
systems<br />
Description<br />
Set in SVCCLU when a specifically<br />
designated remote nucleus is not<br />
available for a physical call. The<br />
202 subcode appears when this<br />
subcode is set on a remote node.<br />
Target ID disagreement between<br />
IDTE <strong>and</strong> PLXNUC. The 203<br />
subcode appears when this<br />
subcode is set on a remote node.<br />
Unable to find PLXMAP matching<br />
an existing PLXUSER. The 204<br />
subcode appears when this<br />
subcode is set on a remote node.<br />
Entire Net-Work unavailable, can't<br />
route existing user to remote<br />
nucleus. The 205 subcode appears<br />
when this subcode is set on a<br />
remote node.<br />
Entire Net-Work unavailable, can't<br />
route new user to remote nucleus.<br />
The 206 subcode appears when this<br />
subcode is set on a remote node.<br />
No nucleus available for remote<br />
user. The 207 subcode appears<br />
when this subcode is set on a<br />
remote node.<br />
Incorrect PLXMAP update received<br />
by LOCAL=YES nucleus. The 208<br />
subcode appears when this<br />
subcode is set on a remote node.<br />
An internal comm<strong>and</strong> used to<br />
synchronize across multiple nodes<br />
was received for an <strong>Adabas</strong> Parallel<br />
Services database. Such databases<br />
may execute on only one node.<br />
Depending on intersystem<br />
communications timing this may<br />
occur as a database is changed<br />
from <strong>Adabas</strong> Cluster Services to<br />
<strong>Adabas</strong> Parallel Services.<br />
Otherwise this is a logic error.<br />
Unable to assign specified nucleus<br />
to remote user. The physical<br />
comm<strong>and</strong> arrived via Entire<br />
Action<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 />
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 />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>
Change language