×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm with you thru #3, I do that regularly. I tried #4, but it just didn't work.
-----Original Message-----
From: Ken Killian [mailto:kkillian@xxxxxxxxxxxx]
Sent: Tuesday, October 17, 2017 12:32 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
Hi,
So, set up a debug job for your specific job. And then add a break-point for that module.
Inside debug, set up the debug for job:
1.) >Run>debug configuration
2.) on the "IBM i: debug job" add your job, which I assume is either currently running, as "Never-ending" job, or that you have on hold. Or optionally set up your 5250 session to debug.
Put in the job/user/number in the dialog
3.) And you should be good to go! I do that all the time...
4.) Don't forget to add programs to debug.
* While in Debug open the Program/Module view
* add the Program to also to debug. Which could be Program and/or service program. Select the correct radio button, when adding the program/service program.
Sort of hard to explain in an email, but that give you the basic idea....
Might want to explore these possible labs, if you are newbie:
http://ibm.biz/rdi_labs
http://ibm.biz/rdi_hub
-Ken Killian-
midrange.com
