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

, ,
1

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

2

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.
1 Like
3

thanks for your help @ralph zbrog