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




I would suggest that doing a run is a better test of whether or not CC will
work than step ...

Mike

Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199




From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: 2020/10/07 11:46 AM
Subject: [EXTERNAL] Re: [WDSCI-L] RDI 9.6.0.8 code Coverage lock on
program: QTESEPEH
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>



Mike,

Yes, we used F5=Step-into until the SEP debug completed.

I am re-install RDI, and after that I will do check of the Debug PTFS.

The jobs were running, but stuck on QTESEPEH in the program stack.

Thanks! I re-try after the re-install. Which tool approximately 10-minutes.
Because I already had the image downloaded! Cool!


Ken Killian


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mike
Hockings
Sent: Wednesday, October 7, 2020 11:40 AM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDI 9.6.0.8 code Coverage lock on program: QTESEPEH


I assume that following step 3 you clicked Run and the program ran to
completion?

On a first SEP debug/cc session on a workspace I get a popup that I had to
respond to to let the debug/cc continue. Is this dialog maybe still
waiting? If in Windows it could be under something else

If you open the launch configuration on the SEP then is the *SOURCE/*LIST
setting for the CC the same as what was set for the compile and is the
"Update production files" enabled?

Is your IBM i up to date for debug PTFs?

If the job is still in the system then what is it waiting on, a message a
lock or ...?

MIke


Mike Hockings, M.Eng., P.Eng.
DevOps for Enterprise
IBM Developer for z Systems and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx voice 1-905-413-3199 T/L
313-3199 ITN 23133199




From: Ken Killian <kkillian@xxxxxxxxxxxx>
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: 2020/10/07 10:41 AM
Subject: [EXTERNAL] [WDSCI-L] RDI 9.6.0.8 code Coverage lock on
program:
QTESEPEH
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>



Hi,

Using RDI 9.6.0.8 and code coverage is NOT WORKING. The submitted job is
locked up at program: QTESEPEH and just waits forever.

What I am doing wrong?

Here is what I did:
1.) Add SEP for DEBUG dummy test-program: test_cc
2.) Sbmjob cmd(call test_CC)
3.) Program pops up in RDI debug! Excellent!
4.) Toggle to code coverage in the IBM i service entry points.
5.) Sbmjob cmd(call test_CC)
6.) Batch job get locked up at program: QTESEPEH

Here is the test_CC program:
**free
dcl-s idx int(10);
select;
when idx = 0;
idx += 1;
other;
idx = 99;
endsl;
*inlr = *on;
return;

Have been waiting now for over 15-minutes! This is ABSURD! How do I get
code-coverage to work? It works in Debug, but no longer in code coverage.
And I have created yet another brand new workspace. I do not understand why
it no longer works.

Ken Killian


--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
$


or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l
$

.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
$





--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
$

or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l
$
.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
$

--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l

or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l
.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com





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.