17.12.2012 Views

Adabas Response Codes - Software AG Documentation

Adabas Response Codes - Software AG Documentation

Adabas Response Codes - Software AG Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Adabas</strong> <strong>Response</strong> <strong>Codes</strong><br />

Explanation The meaning of this response code varies, depending on whether you are using <strong>Adabas</strong><br />

on mainframe systems or <strong>Adabas</strong> on open systems.<br />

42<br />

Mainframe Systems<br />

A collation descriptor exit or hyperexit error occurred. The following table describes<br />

the possible subcodes for this response code and their meanings:<br />

Subcode Meaning<br />

1 Either a collation descriptor exit (subcode CDXn where n is<br />

the one-byte binary collation descriptor exit number) or a<br />

hyperdescriptor exit ("hyperexit") was not specified<br />

ADARUN.<br />

5 The hyperexit stub was called for an extended MU/PE file.<br />

6 Improper use of the parameter list was detected by the<br />

Hyperexit Stub. The most likely reason is that a hyperexit<br />

using the <strong>Adabas</strong> 8 parameter structures is linked to the<br />

Hyperexit Stub.<br />

7 The Hyperexit Stub could not resolve the HEXOLD external<br />

reference.<br />

8 Improper use of the parameter list was detected. The second<br />

word of the parameter list was modified.<br />

9 A hyperexit did not return an output parameter area address.<br />

10 A hyperexit rejected the call by setting a nonzero return<br />

code in the output parameter header.<br />

Open Systems<br />

A hyperexit is not available to the nucleus. The following information is returned in the<br />

Additions 2 field of the control block:<br />

The first two bytes contain the number of the hyperexit,;<br />

The third and fourth bytes contain the name of the hyperdescriptor.<br />

Table of Contents

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!