Re: Code Coverage -- WDSCI-L

Alan,
You are far better off with SEP and STRRSESVR.
If this is something you do regularly, you can use CODECOV.

So SEP doesn't work for regular debugging either? You can look at the log
entries or end and start the debug server.
You can do this from RDi from the context menu on the Objects under the
connection name. Select Remote Servers>Debug> Stop or Start
______________________________________________________________________________________

Edmund Reinhardt
905-413-3125
IBM Canada Ltd Rational Developer for i Access Client Solutions
Architect
[1]https://www.linkedin.com/in/edmundreinhardt/ [2]http://ibm.biz/rdi_hub [3]http://ibm.biz/IBMi_ACS

-----"WDSCI-L" <[4]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote: -----
To: [5]wdsci-l@xxxxxxxxxxxxxxxxxx
From: Alan Cassidy <cfuture@xxxxxxxxxxx>
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
Date: 01/06/2021 06:57PM
Subject: [EXTERNAL] Re: [WDSCI-L] Code Coverage

Edmund, Many thanks for taking the time to help.

For one thing, the message "CRRDGE3002E Connection with the debug engine
was lost" was the error I got when trying to run the program in the 5250
session, after setting up a service entry point with RDi and telling it
to do CC instead of debug.

At some point (before this latest round) I did use an STRRSESVR command.
I'll go back and look at your instructions.

I know I made ran CC successfully in October, there was still the file
left over in my IFS directory.

--Alan Cassidy

On 1/6/2021 1:05 PM, Edmund Reinhardt wrote:
> Hi Alan,
> It is a bit of a pain to get interactive launches set up in RDi (you
have
> to use STRRSESVR in an emulator to tie that emulator to RDi,
sometimes
> there are firewall issues block the IBM i from reaching your PC,
Verify
> Connection... on the Objects subsystem will identify those).
>
> But with CODECOV on the host, you can do all your analysis on the
green
> screen (even automated with CL commands etc.) and then only use RDI
to
> look at the results. That is what I was showing you the
instructions to
> do.
>
______________________________________________________________________________________
>
>
> Edmund Reinhardt
> 905-413-3125
> IBM Canada Ltd Rational Developer for i
Access Client Solutions
> Architect
>
[1][6]https://www.linkedin.com/in/edmundreinhardt/  [2][7]http://ibm.biz/rdi_hub  [3][8]http://ibm.biz/IBMi_ACS ;
>
>
>
>
>
> ----- Original message -----
> From: Alan Cassidy <[9]cfuture@xxxxxxxxxxx>
> Sent by: "WDSCI-L" <[10]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
> To: [11]wdsci-l@xxxxxxxxxxxxxxxxxx
> Cc:
> Subject: [EXTERNAL] Re: [WDSCI-L] Code Coverage
> Date: Tue, Jan 5, 2021 7:22 PM
>
> Thanks Edmund! I will try out your suggestion tomorrow morning. I
did
> get a cczip file in the IFS, expanded it in RSE, double-clicked
it, but
> now I have your suggestion. The program is interactive and has to
run
> from green screen.
>
> Today I tried doing it again but had a couple of program errors. I
tried
> it using the SEP. I kept getting errors.
>
> I successfully used CC in October after some trial and error. I
will
> report back.
>
> --Alan
>
> On 1/4/2021 11:56 PM, Edmund Reinhardt wrote:
> > Hi Alan,
> > I understand your question.
> > The CODECOV command generates CCZIP files into an IFS
directory.
> > You can view the results through RDi or there are some third
> parties that
> > also visualize it, like Freshe, ARCAD etc.
> > To view it through RDi you right click on the Code Coverage
> Results view
> > and Add Result Location...
> > Select Remote Systems and drill down to your IFS directory.
Then
> all of
> > your coverage results will be listed in RDi.
> > You can see it in the following image.
> > [1][4][12]https://imgur.com/zmnHZFw ;
> >
>
______________________________________________________________________________________
> >
> >
> > Edmund Reinhardt
> > 905-413-3125
> > IBM Canada Ltd Rational
Developer for
> i Access Client Solutions
> > Architect
> >
>
[2][5][13]https://www.linkedin.com/in/edmundreinhardt/   [3][6][14]http://ibm.biz/rdi_hub   [4][7][15]http://ibm.biz/IBMi_ACS ;
> >
> >
> >
> >
> >
> > ----- Original message -----
> > From: Alan Cassidy <[16]cfuture@xxxxxxxxxxx>
> > Sent by: "WDSCI-L"
<[17]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
> > To: [18]wdsci-l@xxxxxxxxxxxxxxxxxx
> > Cc:
> > Subject: [EXTERNAL] Re: [WDSCI-L] Code Coverage
> > Date: Mon, Jan 4, 2021 6:15 PM
> >
> > I think I should explain that I went to RDi, expanded on
IFS
> Files to
> > the directory I told the results to go to, and
double-clicked on
> the
> > cczip file.
> >
> > --aec
> >
> > On 1/4/2021 5:46 PM, Alan Cassidy wrote:
> > > Reviewed Guarino's and Susan's videos on RDi Code
Coverage.
> Seems I
> > > have to re-learn the thing every time I use it (not very
> often).
> > >
> > > I was able to use the 5250 screen to run the CODECOV
command
> for this
> > > program I need it for, and it generated me an IFS file.
But I
> did that
> > > all in the green screen. How do I pull up the results
again?
> So far I
> > > just got garbage.
> > >
> > > -alan
> > >
> > >
> > --
> > This is the Rational Developer for IBM i (WDSCI-L)
mailing
> list
> > To post a message email: [19]WDSCI-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> [5][8][20]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> > or email: [21]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the
archives
> > at [6][9][22]https://archive.midrange.com/wdsci-l   ;.
> >
> > Help support midrange.com by shopping at amazon.com with
our
> affiliate
> > link: [7][10][23]https://amazon.midrange.com ;
> >
> >
> >
> >
> > References
> >
> > Visible links
> > 1. [11][24]https://imgur.com/zmnHZFw ;
> > 2. [12][25]https://www.linkedin.com/in/edmundreinhardt/ ;
> > 3. [13][26]http://ibm.biz/rdi_hub ;
> > 4. [14][27]http://ibm.biz/IBMi_ACS ;
> > 5.
[15][28]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> > 6. [16][29]https://archive.midrange.com/wdsci-l ;
> > 7. [17][30]https://amazon.midrange.com/ ;
> --
> This is the Rational Developer for IBM i (WDSCI-L) mailing list
> To post a message email: [31]WDSCI-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
[18][32]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> or email: [33]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at [19][34]https://archive.midrange.com/wdsci-l  ;.
>
> Help support midrange.com by shopping at amazon.com with our
affiliate
> link: [20][35]https://amazon.midrange.com ;
>
>
>
>
> References
>
> Visible links
> 1. [36]https://www.linkedin.com/in/edmundreinhardt/ ;
> 2. [37]http://ibm.biz/rdi_hub ;
> 3. [38]http://ibm.biz/IBMi_ACS ;
> 4. [39]https://imgur.com/zmnHZFw ;
> 5. [40]https://www.linkedin.com/in/edmundreinhardt/ ;
> 6. [41]http://ibm.biz/rdi_hub ;
> 7. [42]http://ibm.biz/IBMi_ACS ;
> 8. [43]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> 9. [44]https://archive.midrange.com/wdsci-l ;
> 10. [45]https://amazon.midrange.com/ ;
> 11. [46]https://imgur.com/zmnHZFw ;
> 12. [47]https://www.linkedin.com/in/edmundreinhardt/ ;
> 13. [48]http://ibm.biz/rdi_hub ;
> 14. [49]http://ibm.biz/IBMi_ACS ;
> 15. [50]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> 16. [51]https://archive.midrange.com/wdsci-l ;
> 17. [52]https://amazon.midrange.com/ ;
> 18. [53]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
> 19. [54]https://archive.midrange.com/wdsci-l ;
> 20. [55]https://amazon.midrange.com/ ;
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: [56]WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [57]https://lists.midrange.com/mailman/listinfo/wdsci-l ;
or email: [58]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [59]https://archive.midrange.com/wdsci-l ;.

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

</wdsci-l-bounces@xxxxxxxxxxxxxxxxxx></cfuture@xxxxxxxxxxx>

References

Visible links
1. https://www.linkedin.com/in/edmundreinhardt/
2. http://ibm.biz/rdi_hub
3. http://ibm.biz/IBMi_ACS
4. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
5. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
6. https://www.linkedin.com/in/edmundreinhardt/
7. http://ibm.biz/rdi_hub
8. http://ibm.biz/IBMi_ACS
9. mailto:cfuture@xxxxxxxxxxx
10. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
11. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
12. https://imgur.com/zmnHZFw
13. https://www.linkedin.com/in/edmundreinhardt/
14. http://ibm.biz/rdi_hub
15. http://ibm.biz/IBMi_ACS
16. mailto:cfuture@xxxxxxxxxxx
17. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
18. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
19. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
20. https://lists.midrange.com/mailman/listinfo/wdsci-l
21. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
22. https://archive.midrange.com/wdsci-l
23. https://amazon.midrange.com/
24. https://imgur.com/zmnHZFw
25. https://www.linkedin.com/in/edmundreinhardt/
26. http://ibm.biz/rdi_hub
27. http://ibm.biz/IBMi_ACS
28. https://lists.midrange.com/mailman/listinfo/wdsci-l
29. https://archive.midrange.com/wdsci-l
30. https://amazon.midrange.com/
31. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
32. https://lists.midrange.com/mailman/listinfo/wdsci-l
33. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
34. https://archive.midrange.com/wdsci-l
35. https://amazon.midrange.com/
36. https://www.linkedin.com/in/edmundreinhardt/
37. http://ibm.biz/rdi_hub
38. http://ibm.biz/IBMi_ACS
39. https://imgur.com/zmnHZFw
40. https://www.linkedin.com/in/edmundreinhardt/
41. http://ibm.biz/rdi_hub
42. http://ibm.biz/IBMi_ACS
43. https://lists.midrange.com/mailman/listinfo/wdsci-l
44. https://archive.midrange.com/wdsci-l
45. https://amazon.midrange.com/
46. https://imgur.com/zmnHZFw
47. https://www.linkedin.com/in/edmundreinhardt/
48. http://ibm.biz/rdi_hub
49. http://ibm.biz/IBMi_ACS
50. https://lists.midrange.com/mailman/listinfo/wdsci-l
51. https://archive.midrange.com/wdsci-l
52. https://amazon.midrange.com/
53. https://lists.midrange.com/mailman/listinfo/wdsci-l
54. https://archive.midrange.com/wdsci-l
55. https://amazon.midrange.com/
56. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
57. https://lists.midrange.com/mailman/listinfo/wdsci-l
58. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
59. https://archive.midrange.com/wdsci-l
60. https://amazon.midrange.com/