Re: RDI 9.6.0.8 Code Coverage Does not work...

Steve,

SEP Debug does not work for my co-worker. WE have tried the following:
1.) Start Work space with -clean
2.) create brand new workspace
3.) End the user's jobs in QUSRWRK

Trying to add the SEP, we get this message:

"Server: CPF7102 Unable to add breakpoint or trace"

Shucks! How do we resolve?

Should I have him open an IBM PMR case, and attach the workspace & Error-Log? Would that help?


Ken Killian



-----Original Message-----
From: Ken Killian
Sent: Monday, October 5, 2020 2:52 PM
To: 'Rational Developer for IBM i' <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: RE: RDI 9.6.0.8 Code Coverage Does not work...

Steve,

Thanks! I passed this on to my co-worker. I suggest that he try it on smaller simple program for his first pass at Code Coverage.

I forgot about that batch/Interactive option. His original program, I ran into level checks on the service program. That could be the root cause, but not sure. I discovered that I could NOT do code coverage on his program either.

Will confirm later if it works for him.

Thanks again.

Ken Killian

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Ferrell via WDSCI-L
Sent: Monday, October 5, 2020 2:35 PM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDI 9.6.0.8 Code Coverage Does not work...

Hi Ken,

If your team mates can debug, they should be able to use Code Coverage.

So have them run debug first. If that works, have them change to Code Coverage Mode to run.

Have them run from a *PGM object, doing the Code Coverage (Prompt) -> Batch.

Ensure they have the [x] Update production files checked (if applicable) and ensure they have created their source for *DEBUG.

It may help to see if you can Debug/Code Coverage their programs first.

If not, have them look at the Error List.

The first place to look is to see if there are some programs failing to run in a *MSGW state on your system. It may be they had program erros that caused the Debug server to end in Message Wait State. Any queued after that will appear to not run, but will run once the batch queue is cleared.

Hope this helps.

Steve Ferrell
w. www.helpsystems.com