# adabas 3.3.3.01 Message Queues

**URL:** <https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Basics-on-Linux-Unix-Windows, Adabas-on-Windows-UNIX, Adabas-on-Linux\
**Created:** [July 4, 2006, 6:50pm UTC](https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071 "2006-07-04T18:50:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Waldron](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@Mike\_Waldron](https://techcommunity.softwareag.com/u/Mike_Waldron)\
**Post date:** [July 4, 2006, 6:50pm UTC](https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071/1 "2006-07-04T18:50:13Z")

</div>

I have been trying to find out how ADABAS creates/removes message queues in HP-UX/ia64 11.23.

We use Applinx with about 500 users and when Applinx disconnects after a timeout, it leaves the message queue(s) for the user and they access 4 databases during a session.

1. The user id is changed to ######## and remains in the user queue so a 3009 can be issued if necessary. We wrote a program to clean these up every 2 hours.
2. Message queue entries change from …ada… to …ad0… and I do not know how to identify these.

Out message queues are set to 65,000 max, but with a policy of only re-booting once a month, this could exhaust the message queue resource.

any help is appreciated

---

<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:** [September 4, 2006, 2:02pm UTC](https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071/2 "2006-09-04T14:02:02Z")

</div>

There are two different things:

1. The user queue elements are removed by Adabas if you use the OPEN\_REQUIRED option. Then Adabas can remove the user queue elements after the non activity timeout, because this option takes care that the user gets the required response code 9 - only the reason is different: Open required instead of time limit exceeded.
2. A cleanup of the message queues is done only if all message queues reserved for Adabas are in use (number of message queues = value of NU parameter in v3.3, value of NCL parameter in v5.1). This means that it is normal that the number of message queues increases - as soon as the maximum number of message queues is exceeded, it is reduced again.

Regards,  
Wolfgang

---

<div class="post-metadata">

**Author:** ![Mike\_Waldron](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@Mike\_Waldron](https://techcommunity.softwareag.com/u/Mike_Waldron)\
**Post date:** [September 4, 2006, 5:06pm UTC](https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071/3 "2006-09-04T17:06:49Z")

</div>

Wolfgang,

Thanks.

Many installations have written programs to do ‘op’ across databases in order not to get ‘no open’ reasons when Open\_required is set.

Thank you for the response.

Mike Waldron

---

<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, 2:39pm UTC](https://techcommunity.softwareag.com/t/adabas-3-3-3-01-message-queues/58071/4 "2021-04-02T14:39:01Z")

</div>