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 />
Action<br />
Response 245<br />
Origin<br />
Explanation<br />
Action<br />
Response 246<br />
Origin<br />
Subcode Explanation <strong>and</strong> Recommended Action<br />
16<br />
Open Systems<br />
The unsolicited syncpoint request was rejected.<br />
An invalid FCB extent has been detected for a file.<br />
Mainframe Systems<br />
Review the <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>’s TMSYNCMGR parameter <strong>and</strong> the<br />
<strong>Transaction</strong>Control, Client-side<strong>Transaction</strong><strong>Manager</strong>, <strong>and</strong><br />
HostSystem<strong>Transaction</strong><strong>Manager</strong> client runtime controls for the failing job.<br />
Open Systems<br />
Contact your nearest support center.<br />
Mainframe <strong>and</strong> open systems<br />
On mainframe systems, this response code is issued for communication problems between<br />
add-on products that use the system coordinator (COR) interface to <strong>Adabas</strong>; that is, <strong>Adabas</strong><br />
Fastpath, <strong>Adabas</strong> Vista, <strong>Adabas</strong> SAF Security, <strong>and</strong> <strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong>.<br />
Subcode Meaning<br />
1<br />
2<br />
Internal error.<br />
A required module could not be loaded. This is probably an installation error.<br />
On open systems, pending utility entries exist in the UCB.<br />
On mainframe systems, for subcode 1, contact your <strong>Software</strong> <strong>AG</strong> technical support<br />
representative. For subcode 2, consult the installation instructions for the add-on product.<br />
On open systems, delete the entries with RESET = UCB before executing RECOVER, but<br />
ensure that the utilities which own the UCB entries are no longer running.<br />
Open systems only<br />
Explanation Utility communication block (UCB) overflow.<br />
Action<br />
160<br />
Execute the RESET function of ADADBM to remove unused entries from the utility<br />
communication block if the utilities that own them are no longer running.<br />
<strong>Adabas</strong> <strong>Transaction</strong> <strong>Manager</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>