# response code = 47 when accesing ADABAS using COBOL

**URL:** <https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Mainframes, Adabas-Basics-on-Mainframes\
**Created:** [April 25, 2012, 1:24pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429 "2012-04-25T13:24:14Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![puneet\_puthran](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@puneet\_puthran](https://techcommunity.softwareag.com/u/puneet_puthran)\
**Post date:** [April 25, 2012, 1:24pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/1 "2012-04-25T13:24:14Z")

</div>

Hello,

I encountered a response code of 47 when trying to access ADABAS (in COBOL) and learnt that it is due to hold queue limit breach. Is there a way to find out the maximum value that is set for the queue in the current execution environment? I read the relevant document and understand the way it is calculated but would like to know the existing value that is present.

Thanks.  
Puneet

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 25, 2012, 1:41pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/2 "2012-04-25T13:41:07Z")

</div>

If you mean finding out from the client program (COBOL, NATURAL or whatever) - no.

You can use Adabas Online System (AOS) or the operator command “DRES” to display the  
parameter settings and high water marks.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 25, 2012, 5:45pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/3 "2012-04-25T17:45:26Z")

</div>

The limit for the user is returned in the ADD4 field of the OP-command.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 25, 2012, 6:04pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/4 "2012-04-25T18:04:27Z")

</div>

> [@Mogens](#):
>
> The limit for the user is returned in the ADD4 field of the OP-command.

Sorry to disagree, Mogens, ADD4 on an OP can be used to SET limits, not query them.

Adabas will return a version number in ADD4 as a response to an OP (on the mainframe,  
on LUW that’s returned in ISNQ)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 25, 2012, 10:39pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/5 "2012-04-25T22:39:14Z")

</div>

Sorry, you’re correct Wolfgang. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 26, 2012, 1:52am UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/6 "2012-04-26T01:52:13Z")

</div>

Hi Puneet,

I’m sure your friendly DBA would be more than happy to let you know the database’s NISNHQ parameter (limit of records on hold for a single user).

Armed with this information, you should modify your COBOL program to issue an ET command before you reach this limit, preferably at the end of a logical transaction or a multiple thereof.

Cheers,

Graeme

---

<div class="post-metadata">

**Author:** ![puneet\_puthran](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@puneet\_puthran](https://techcommunity.softwareag.com/u/puneet_puthran)\
**Post date:** [April 26, 2012, 5:40am UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/7 "2012-04-26T05:40:55Z")

</div>

Hello,

Thanks to everyone for the reply.

I was able get the NH and NU value by accessing the DBES panel and have set the ET limit accordingly. And was able to avoid the abend.

Thanks much,  
Puneet.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:01pm UTC](https://techcommunity.softwareag.com/t/response-code-47-when-accesing-adabas-using-cobol/100429/8 "2021-04-02T15:01:54Z")

</div>


