# problem with natural debugger -  how to disable the NODEB=ON

**URL:** <https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-Utilities\
**Created:** [January 15, 2018, 12:09am UTC](https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731 "2018-01-15T00:09:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rajesh\_killadi](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@Rajesh\_killadi](https://techcommunity.softwareag.com/u/Rajesh_killadi)\
**Post date:** [January 15, 2018, 12:09am UTC](https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731/1 "2018-01-15T00:09:23Z")

</div>

Hi All,

I’m trying to debug an online screen in production region and when I try to put a break point, for some lines it is giving NODBG=ON SET (as shown in screen) and it is not setting the Breakpoint up. Could you please help me how I can resolve this problem ?

23:04:35 \*\*\*\*\* NATURAL TEST UTILITIES \*\*\*\*\* 2018-01-14  
Test Mode ON - List Object Source - Object ZZZ016P1

Co Line Source Message   
\_\_ 2030 IF #MAPA-START-DATE GT #MAPA-END-DATE |  
\_\_ 2040 REINPUT ‘START DATE GREATER THAN THE END DATE’ |  
\_\_ 2050 MARK \*#MAPA-START-DATE ALARM |  
\_\_ 2060 END-IF |

Line 2150 in object ZZZ016P1 compiled with NOC option NODBG=ON.  
Command ===\>   
Enter-PF1—PF2—PF3—PF4—PF5—PF6—PF7—PF8—PF9—PF10–PF11–PF12—

Thanks  
Regards  
Raesh Killiadi

---

<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:** [January 15, 2018, 1:44am UTC](https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731/2 "2018-01-15T01:44:59Z")

</div>

Your program has been compiled with the Natural Optimizer Compiler (NOC). Statement 2150 has been optimized, so it cannot be traced by the Debugger.

You have a few options.

- Recompile the Production program with NOC turned off. This is rather invasive, as it means the program will be slower until compiled again with NOC.

- Copy Production data to a test environment where your program can be compiled with NOC off. This will require DBA assistance.

- Copy your program into a test library in Production and compile without NOC. Have that library appear in a higher level in the Steplib chain so that it is executed instead of the Production/NOC version.

---

<div class="post-metadata">

**Author:** ![Rajesh\_killadi](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@Rajesh\_killadi](https://techcommunity.softwareag.com/u/Rajesh_killadi)\
**Post date:** [January 15, 2018, 7:02pm UTC](https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731/3 "2018-01-15T19:02:19Z")

</div>

thanks for your help @ralph zbrog

---

<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:39pm UTC](https://techcommunity.softwareag.com/t/problem-with-natural-debugger-how-to-disable-the-nodeb-on/197731/4 "2021-04-02T15:39:56Z")

</div>