Skip to main content

DS to debug dialogs

  • October 9, 2014
  • 5 replies
  • 0 views
A
  • Anonymous

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

5 replies

Chris Glazier
Forum|alt.badge.img+2

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

Hi Fran,

I just tried this here by modifying the Customer example program to call DS instead of DSGRUN an it worked just fine and the screenset debugger was displayed.

Could you please try this same test to see if this is an overall system problem or if it is related to your application?

The customer example can be found under C:\\Program Files (x86)\\Micro Focus\\Net Express 5.1\\Examples\\Dialog System\\CUSTOMER

Perhaps you have some older Net Express run-time files located within your path?

Thanks,

A
  • Anonymous
  • October 10, 2014

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

Hi Chris,

Just tried with your customer example using 'DS' and I get the same error as before.  What should I be looking for in the path env?  I hope there is a relatively simple way to fix this, because I really need to debug a dialog!  Thanks!

A
  • Anonymous
  • October 10, 2014

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

Should this be a new ticket?

A
  • Anonymous
  • October 10, 2014

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

Interestingly, when I am editing the screen itself, I can get it to 'debug' the dialog (File, Debug), however of course at this point,  it is not attached to any program.

Chris Glazier
Forum|alt.badge.img+2

We just upgraded to netexpress 5.110.0022 and now it appears I can no longer debug my dialog.  Use to be when it was called I could substitute DSGRUN with DS and it debug the dialogs behind the screens. Now (and I tried several screens), I get

"Execution of the program DSOO had been interrupted.  This program is not animatable, but you can view the call/perform stac..  The cause of the interupt was:114.  Attempt to access item beyond bounds of memory (Signal 11).

I hope this is something I need to change somewhere and not a problem with the new version.


#DSGRUN
#dialog
#DS
#114

Fran,

Please open a new ticket for this and we will research through the incident.

You should check your PATH and COBDIR settings to see what they include.

Is Visual COBOL also installed on this same system?

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement