× 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.



It would be helpful to know what happens between these steps, "It appears that the first call to PGMA is "caught" by the debugger" and "but subsequent calls to PGMA in the same CL". SEPs cannot monitor for any changes that occur to the program object. So if you happen to recompile the code after setting the SEP you have to refresh the SEP entry to get the debugger to start up again. Also, the debugger used to not allow you to set the SEP after you have activated the program once in a job.

I only mention this because at RDi 9.5.1.0 APAR SE65785, I have yet to see behavior like this. I also have RDi installed as a local user copy and not in the Program Files, so that might make a difference as well.


Thanks, Matt


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Thursday, November 03, 2016 11:53 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Newbie: debug a program running in batch

I wonder how much of the issue can be attributed to Eclipse vs. IBM.

So, I guess my cheat sheet for debugging in RDi is:
1) Exit RDi
2) Delete workspace
3) Start RDi
4) Set the SEP(s), ensuring correct object library and user ID
5) On the i, start a brand new job, ensuring correct library list (or qualify your program call)

Even with all that, I find I'm still having problems. It appears that the first call to PGMA is "caught" by the debugger (I have a breakpoint set at the first executable statement), but subsequent calls to PGMA in the same CL program stream are not. I just now confirmed this by debugging in the green screen, which works properly. I've wasted most of my day getting to this point. Not happy.

- Dan

On Thu, Nov 3, 2016 at 1:16 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I've somewhat reluctant to report RDi problems to IBM. Their goto
answer is "delete your workspace and try again", which IMO is a cheap
cop-out on their part. Report the same problem a few days later, and
again "delete your workspace and try again".

--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.