# Program Version Error NAT0932 and subroutines

**URL:** <https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Mainframes\
**Created:** [June 9, 2010, 4:36pm UTC](https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801 "2010-06-09T16:36:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Meurig\_Jones](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Meurig\_Jones](https://techcommunity.softwareag.com/u/Meurig_Jones)\
**Post date:** [June 9, 2010, 4:36pm UTC](https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801/1 "2010-06-09T16:36:12Z")

</div>

Hi

I am trying to understand the mechanics behind this error in relation to subroutines.

In test I can promote and stow a subroutine used by a program running in batch that sleeps when not busy without generating a NAT0932.

Is this luck or is ADABAS Natural Buffer Pool maintenance designed to prevent this occurring by deleting the module when stowed?

If the subroutine was being executed at point of stow would this make a difference?

Thanks

---

<div class="post-metadata">

**Author:** ![Douglas\_Kelly](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/douglas_kelly/32/102_2.png) [@Douglas\_Kelly](https://techcommunity.softwareag.com/u/Douglas_Kelly)\
**Post date:** [June 9, 2010, 10:27pm UTC](https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801/2 "2010-06-09T22:27:29Z")

</div>

You need to explain more about your environment: are you using Global Buffer Pool? If you are stowing online, does your online use the same GBP as the batch? Are you sending your updated module from a to b (test to prod?), where b is where the NAT0932 occurs? Or are you pulling the module into b from a (that is, are you initiating a SYSMAIN from a or from b?) Are a and b on different GBP’s?

In general, assuming you have different GBP’s between environments, you want to be on the target environment (e.g. prod) and use SYSMAIN to pull the module from the source environment (e.g. test). This allows the GBP to be aware of the update and act accordingly. If you do it the other way, the target GBP doesn’t know that the module has been updated on the database and that it is different from the version it has in the BP. If space constraints and non-usage dictate that the module be unloaded, the BP doesn’t know that the module is changed until it re-reads it from the database.

---

<div class="post-metadata">

**Author:** ![Meurig\_Jones](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Meurig\_Jones](https://techcommunity.softwareag.com/u/Meurig_Jones)\
**Post date:** [June 11, 2010, 2:30pm UTC](https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801/3 "2010-06-11T14:30:15Z")

</div>

Thanks for your reply.

Some detail I don’t know yet - we use a change control function that hides critical detail from us.

---

<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:58pm UTC](https://techcommunity.softwareag.com/t/program-version-error-nat0932-and-subroutines/93801/4 "2021-04-02T14:58:35Z")

</div>


