Re: RDP Debug when STRDBG active

Interesting that the CHGDBG fails when debug is set by an SEP. I don't have
time to play with it right now, but I'll take a look at the message for this
failure vs. the normal 'not in debug' message when I get a chance and see if
there's a way to make it work.

Dave Shaw
Mohawk Industries



----- Original Message ----
From: "Anderson, Kurt" <KAnderson@xxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Tue, March 5, 2013 12:23:50 PM
Subject: Re: [WDSCI-L] RDP Debug when STRDBG active

Seemed like a good idea. Unfortunately this doesn't seem to work.

The first statement in my CL was changed to CHGDBG. In RDP I created a SEP for
that program with a breakpoint on the CHGDBG statement. Unfortunately the
statement ran w/o the breakpoint stopping on it. (In RDP I see the little blue
square next to the line number after setting the breakpoint.)


Here is the debug code modified to use ChgDbg.
CHGDBG
MONMSG MSGID(CPF0000) EXEC(GOTO DEBUG)
GOTO CMDLBL(SKIPDEBUG)
Debug:
STRDBG PGM(TST_EDIT) UPDPROD(*NO)
SkipDebug:

The SEP brings up the CL and stops on the PGM line. I click resume (f8) and
doesn't stop on the breakpoint. When I start the program and do Step Over, I
see that it does execute CHGDBG, so I don't know why it's not breaking there.
CHGDBG fails so it continues to STRDBG.

Well, I guess I've put enough time into this for today. I have a program issue
to resolve...