# ASID (Address Space Identifier) and ADABAS

**URL:** <https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Mainframes, Adabas-Basics-on-Mainframes\
**Created:** [May 6, 2016, 5:40pm UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336 "2016-05-06T17:40:31Z")\
**Posts on this page:** 7\
**Page:** 1

<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:** [May 6, 2016, 5:40pm UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/1 "2016-05-06T17:40:31Z")

</div>

My questions:

1. Does ADABAS render an address space (ASID) non-reusable when it terminates?

If yes to question 1 above,

2.why does it do so? any reason …  
3. Is it possible to control it? and how? (other than IPL to reset)

Context: Recently on the question of running out of non-reusable ASID’s (RSVNONR) it may have been attributed to ADABAS. I want to know if it is true / possible etc. and if so … can we do anything to prevent it.

Regards Feroz

---

<div class="post-metadata">

**Author:** ![Wayne\_Campos1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/wayne_campos1/32/499_2.png) [@Wayne\_Campos1](https://techcommunity.softwareag.com/u/Wayne_Campos1)\
**Post date:** [May 7, 2016, 1:55am UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/2 "2016-05-07T01:55:40Z")

</div>

I think that z/OS marks the ASID as non-reusable, not Adabas. The explanation that I was given (correct or incorrect) is z/OS does this for a cross-memory target ASID.

In newer versions of z/OS there is a reuse ASID parameter. Adabas supports the parameter.

---

<div class="post-metadata">

**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\
**Post date:** [May 8, 2016, 5:26am UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/3 "2016-05-08T05:26:03Z")

</div>

That is correct. When we went to monthly IPLs instead of weekly ones, this became apparent to our mainframe platform folks.

You can do any of the following corrective actions to avoid exhaustion of your address space pool:

1. Size the pool of address spaces to not exhaust them between planned IPLs.

2. Don’t bring down ADABAS except for planned IPLs.

3. Have ADABAS always started with REUSASID=YES (e.g., /S adampm,REUSASID=YES).

We have gone with the third option.

---

<div class="post-metadata">

**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\
**Post date:** [May 8, 2016, 5:29am UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/4 "2016-05-08T05:29:13Z")

</div>

That is correct. When we went to monthly IPLs instead of weekly ones, this became apparent to our mainframe platform folks.

You can do any of the following corrective actions to avoid exhaustion of your address space pool:

1. Size the pool of address spaces to not exhaust them between planned IPLs.

2. Don’t bring down ADABAS except for planned IPLs.

3. Have ADABAS always started with REUSASID=YES (e.g., /S adampm,REUSASID=YES).

We have gone with the third option, though they have increased the ASID pool and we are working towards #2 as well.

---

<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:** [May 9, 2016, 10:30am UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/5 "2016-05-09T10:30:21Z")

</div>

you can as well read more details in the documentation here: [http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada833mfr/adamf/install\_os3/install-zos.htm#cross-memory](http://techcommunity.softwareag.com/ecosystem/documentation/adabas/ada833mfr/adamf/install_os3/install-zos.htm#cross-memory)

You need access to Empower 8)

---

<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:** [May 25, 2016, 1:31pm UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/6 "2016-05-25T13:31:52Z")

</div>

Thanks for all the valuable input Brian / Ursula.

---

<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:35pm UTC](https://techcommunity.softwareag.com/t/asid-address-space-identifier-and-adabas/188336/7 "2021-04-02T15:35:59Z")

</div>


