Re: Debug does not end program using Terminate.

Jason,

That is how the most of us doing the S.E.P. way.

I got several of my co-workers do to it that way.

We had to debug Stored-Procedure and Web-Services. And the RDI debug caught it every time!

The little caveat, you have provide 3 bits of information:

1.) What IBM I Box
2.) Library/Program
3.) The user profile that is running the program.

Once you get use it, I find it a lot simpler.

PS. If you started Green-Screen Debug first. And then try to catch it in RDI, but you already have debug for the same program on Green Screen. Then RDI will not catch it! Because Green screen already had a lock on it for debug!

Just something I have discovered. I usually play it safe and sign-off my Green Screen or issue the Endbbug command by habit. Before setting up SEP on RDI!

Enjoy! :)


-Ken Killian-

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jason Olson
Sent: Friday, February 22, 2019 3:45 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug does not end program using Terminate.

OK so I think I found a way to handle this without too much trouble.

The first thing you do is add a SEP for the program you want to debug.

Then on the 5250 session call the program like normal. You then switch into debug and can debug as normal.

If you need to stop due to an error in the code, you Alt + Tab back to the
5250 session you are running, then Shift + Esc, and then option 2. That flops you out of what you were running, and also ends debug.

I guess it's not the perfect solution, but at least you can stop what's running so that it just does not keep pouring over records making mistakes the whole way.


Thanks,

Jason E. Olson