Hence the break points...
I add a break point when it is going to stop into the service program, and then I step into the service program, and then add a break point there. That works for me every time...
Did that work for you?
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Tuesday, October 17, 2017 3:41 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug module/job
I had it stopped in debug when I added my service program. I did not step thru every line of code until I got to my service program, that could be hundreds (or thousands) of lines of code.
-----Original Message-----
From: Ken Killian [mailto:kkillian@xxxxxxxxxxxx]
Sent: Tuesday, October 17, 2017 1:22 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debug module/job
I forgot to mention that you have to have it stopped in debug, to add other program/service-programs. At least that is how I do it, when debugging a specific job...
Sort of the same way on the old Green Screen Debugger.
To add break-points on the newly added program, I have to double-click on the source, and add the break-point. And sadly, I have to step into the code once for it to work. I am probably missing some little thing. But, that is how I get it to work.
-Ken Killian-
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.
midrange.com
