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 />
98<br />
99<br />
130<br />
249<br />
Open Systems<br />
■ Natural is being used, in such a way that two <strong>Adabas</strong> sessions are maintained<br />
for each client;<br />
■ The client control <strong>Transaction</strong> Model is set to MESS<strong>AG</strong>E;<br />
■ Natural parameters are set such that Natural might not generate OP comm<strong>and</strong>s<br />
for all database sessions.<br />
You can make sure that Natural generates OP comm<strong>and</strong>s by using a non-blank ETID,<br />
or by means of Natural’s DBOPEN parameter.<br />
The condition can also occur if all of the following are true:<br />
■ Natural is being used, in such a way that two <strong>Adabas</strong> sessions are maintained<br />
for each client;<br />
■ The <strong>Adabas</strong> System Coordinator has timed out Natural’s “system” session.<br />
In this case, a new Natural LOGON might clear the condition. Otherwise terminate<br />
the session <strong>and</strong> start a new session.<br />
If the error persists, contact your <strong>Software</strong> <strong>AG</strong> support representative.<br />
This subcode is issued by <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
The client session was executing in serial mode, <strong>and</strong> requested that changes be<br />
committed. Some of the changes were committed, <strong>and</strong> some were backed out.<br />
Examine the results of the transaction. If necessary, correct the result by manual<br />
intervention.<br />
This subcode is issued by <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
The client session incurred a security response code; ATM backed out the user’s<br />
changes.<br />
If security permissions are not adequate, correct them <strong>and</strong> rerun the transaction.<br />
In a cluster, the UQE of the user was deleted between the time the user's comm<strong>and</strong><br />
was routed to one nucleus in the cluster <strong>and</strong> the time that nucleus selected the<br />
comm<strong>and</strong> for processing.<br />
In <strong>Adabas</strong> Vista, all transaction activity by the client has been backed out for one<br />
of the following reasons:<br />
■ The client is using multiple (different) ETIDs which have collided against a<br />
particular database.<br />
Action: Review the client’s use of ETIDs with respect to the current translation rules<br />
<strong>and</strong>/or partitioned files.<br />
This response is caused by one of the following:<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 />
57