×
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.
The SEP must be started before the program starts... OR (if it's a constantly running job), find the job in RDi and start it there (I think it's a right-click on the job). You also need to set the SEP for the user id that the job is using.
So if you are submitting the job from the command line, you would likely be the user.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Wednesday, November 02, 2016 9:16 PM
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Newbie: debug a program running in batch
I'm on a v7r1 box and using RDi v9.5.0.3. I need to debug a program that runs in batch. I haven't had to use debug in quite awhile and the last time I had to debug a program running in batch predated my RDi experience.
I've got the SEP set on the program. I'm in the debug perspective. I have the source code up and have a breakpoint set on the first executable statement in the program.
When I call the program from the green screen, nothing happens in RDi debug. The program finishes normally.
What am I missing?
--
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:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
