# do not terminate session

**URL:** <https://techcommunity.softwareag.com/t/do-not-terminate-session/202934>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Linux, Natural-Installation-and-Setup-on-Open-Systems, Natural-on-Windows-Unix\
**Created:** [February 25, 2019, 6:59pm UTC](https://techcommunity.softwareag.com/t/do-not-terminate-session/202934 "2019-02-25T18:59:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\
**Post date:** [February 25, 2019, 6:59pm UTC](https://techcommunity.softwareag.com/t/do-not-terminate-session/202934/1 "2019-02-25T18:59:21Z")

</div>

I’m looking for a Natural parameter or setting to ignore a TERMINATE statement during testing. The TERMINATE statement is intended for end-users in a Production environment. When I’m testing the application, I want to return to the NEXT prompt when exiting the application instead of ending the session.

I was certain that I had used this before, likely in a Natural for Unix environment, but I can’t find it in any of the Natural for Windows documentation.

Is this just wishful thinking?

---

<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:** [February 26, 2019, 1:46pm UTC](https://techcommunity.softwareag.com/t/do-not-terminate-session/202934/2 "2019-02-26T13:46:17Z")

</div>

If you can determine which environment you’re running in using USR routines (e.g., finding out the DBID/FNR of the FNAT), you could conditionally issue TERMINATE if you’re in production or STOP if you’re not.

I know of no way to override what TERMINATE does with your session.

---

<div class="post-metadata">

**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\
**Post date:** [February 26, 2019, 4:33pm UTC](https://techcommunity.softwareag.com/t/do-not-terminate-session/202934/3 "2019-02-26T16:33:01Z")

</div>

> [@](#):
>
> you could conditionally issue TERMINATE if you’re in production or STOP if you’re not

Or I could remember to use %%. But you get into the habit of pressing PF3 until you’re out, and then its too late. And why change the code if there is this cool feature?

I have a strong recollection of “Wow, this is neat!” Perhaps I’m confusing it with a similar feature, also whose details I can’t recall.

Anyone at Darmstadt HQ know what I’m talking about?

---

<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:42pm UTC](https://techcommunity.softwareag.com/t/do-not-terminate-session/202934/4 "2021-04-02T15:42:22Z")

</div>