NOTE: Call the program again, and now debug works okay again. I can see monitor variables again.
Don't know what happen, I guess I will attribute this some unknown "Fluke"
I didn't even refresh my SEP, because I did not recompile the program or anything.
Case-Closed. <Joy Joy>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Friday, December 19, 2014 9:49 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.1.1 Debug: CRRDG3137E Failed to monitor the given expression.
Buck,
I neglected to mention that I did use SEP... I added the SEP, and then call the program on my Green-Screen....
Said to say, these sort of issue NEVER happen on Green Screen debug... Just saying... <smirk>
But, I am a HUGE fan of RDI, I do not wish to go back to SEU <Yuck!>
I was in the same program, never ended debug or anything, and going through as it was processing records, and all of sudden my current Monitor variables stop working... No recompile or restart, still in my SAME Debug program...
<frown>
Just wanted to clarify...
<smile>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Friday, December 19, 2014 9:39 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.1.1 Debug: CRRDG3137E Failed to monitor the given expression.
On 12/19/2014 9:05 AM, Ken Killian wrote:
I was looping through a program in debug mode on our test box, and all of sudden, I cannot a monitor variable...
Message: CRRDG3137E Failed to monitor the given expression.
-snip-
Any ideas? Has anyone else ran into this...
Ken, I hate to reply because so many of my replies are the same :-( I haven't seen this one. It's almost certainly a difference in the way we work. RDi is designed to let people work differently from one another, so this is a good thing!
When I debug, I pretty much clear all my breakpoints and monitors from previous debug sessions. Say I'm working on stored procedures for the web guys. I might have 5 editor tabs open and I'm getting a stubborn issue with a UDTF and a stored procedure, both written in RPGLE. I'll fire up the SEP debugger and clear all breakpoints and monitors and then run the SQL that invokes the executables. I'll add breakpoints and monitors as needed.
Very, very rarely, a trouble ticket comes in and I need to switch gears and work on something else that's urgent, say cash receipts :-). I'll open the C/R programs in the editor, start SEP debugging on them and add some more breakpoints and monitors as needed. Now I have maybe 10 breakpoints and 10 monitors across the two applications.
When I go back to the web stuff, I'll delete the breakpoints and monitors for the C/R application, because I pretty much don't need them anymore. That's a lot of words to ask: Do you have a LOT of monitors?
Another difference: I never debug a currently running program. I start the SEP and then call the program.
--
--buck
'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
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.
--
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
