I have a problem when debugging a natural program calling many subroutines and subprograms - the debugger suddenly stops debugging and ignoring any step commands to continue. I still can inspect the value of variables but cannot continue debugging. There is no message. The debugger always stops at the same program.
I wrote a small program to call my problem subroutine and hey I can debug it without any problem.
Is there a limit of how many subprograms and subroutines you can debug?
Do I have to many debug windows open?
I am working on a windows platform using Natural 3.2.
On the mainframe I have had occasions where I need to increase CICS thread size when I am stepping thru debugger and the number of modules deep I need to go is excession. Extra parms are added to the transaction in CICS used to log onto our natural environment. Maybe there is something similar that can be done in your environment :?:
This may not be what you want to hear but limit the scope of your debugging.
Choose a portion, either at the beginning or the end, and debug that.
If the problem is still unresolved, bite off another chunk and debug it.
I think that you get the idea!
