|
On more thought,
I would also suggest doing a Verify Connection to make sure that the
latest debug PTFs are installed.
______________________________________________________________________________________
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
----- Original message -----
From: Edmund Reinhardt/Toronto/IBM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: Re: [EXTERNAL] Re: [WDSCI-L] Code Coverage
Date: Thu, Jan 7, 2021 9:23 AM
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
[4]https://www.linkedin.com/in/edmundreinhardt/ [5]http://ibm.biz/rdi_hub [6]http://ibm.biz/IBMi_ACS
-----"WDSCI-L" <[7]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> wrote: -----
To: [8]wdsci-l@xxxxxxxxxxxxxxxxxx
From: Alan Cassidy
Sent by: "WDSCI-L"
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][9]https://www.linkedin.com/in/edmundreinhardt/ [2][10]http://ibm.biz/rdi_hub [3][11]http://ibm.biz/IBMi_ACS
>
>
>
>
>
> ----- Original message -----
> From: Alan Cassidy <[12]cfuture@xxxxxxxxxxx>
> Sent by: "WDSCI-L" <[13]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
> To: [14]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][15]https://imgur.com/zmnHZFw
> >
>
______________________________________________________________________________________
> >
> >
> > Edmund Reinhardt
> > 905-413-3125
> > IBM Canada Ltd Rational
Developer for
> i Access Client Solutions
> > Architect
> >
>
[2][5][16]https://www.linkedin.com/in/edmundreinhardt/ [3][6][17]http://ibm.biz/rdi_hub [4][7][18]http://ibm.biz/IBMi_ACS
> >
> >
> >
> >
> >
> > ----- Original message -----
> > From: Alan Cassidy <[19]cfuture@xxxxxxxxxxx>
> > Sent by: "WDSCI-L"
<[20]wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
> > To: [21]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: [22]WDSCI-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> [5][8][23]https://lists.midrange.com/mailman/listinfo/wdsci-l
> > or email: [24]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the
archives
> > at [6][9][25]https://archive.midrange.com/wdsci-l ;.
> >
> > Help support midrange.com by shopping at amazon.com with
our
> affiliate
> > link: [7][10][26]https://amazon.midrange.com
> >
> >
> >
> >
> > References
> >
> > Visible links
> > 1. [11][27]https://imgur.com/zmnHZFw
> > 2. [12][28]https://www.linkedin.com/in/edmundreinhardt/
> > 3. [13][29]http://ibm.biz/rdi_hub
> > 4. [14][30]http://ibm.biz/IBMi_ACS
> > 5.
[15][31]https://lists.midrange.com/mailman/listinfo/wdsci-l
> > 6. [16][32]https://archive.midrange.com/wdsci-l
> > 7. [17][33]https://amazon.midrange.com/
> --
> This is the Rational Developer for IBM i (WDSCI-L) mailing
list
> To post a message email: [34]WDSCI-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
[18][35]https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: [36]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at [19][37]https://archive.midrange.com/wdsci-l ;.
>
> Help support midrange.com by shopping at amazon.com with our
affiliate
> link: [20][38]https://amazon.midrange.com
>
>
>
>
> References
>
> Visible links
> 1. [39]https://www.linkedin.com/in/edmundreinhardt/
> 2. [40]http://ibm.biz/rdi_hub
> 3. [41]http://ibm.biz/IBMi_ACS
> 4. [42]https://imgur.com/zmnHZFw
> 5. [43]https://www.linkedin.com/in/edmundreinhardt/
> 6. [44]http://ibm.biz/rdi_hub
> 7. [45]http://ibm.biz/IBMi_ACS
> 8. [46]https://lists.midrange.com/mailman/listinfo/wdsci-l
> 9. [47]https://archive.midrange.com/wdsci-l
> 10. [48]https://amazon.midrange.com/
> 11. [49]https://imgur.com/zmnHZFw
> 12. [50]https://www.linkedin.com/in/edmundreinhardt/
> 13. [51]http://ibm.biz/rdi_hub
> 14. [52]http://ibm.biz/IBMi_ACS
> 15. [53]https://lists.midrange.com/mailman/listinfo/wdsci-l
> 16. [54]https://archive.midrange.com/wdsci-l
> 17. [55]https://amazon.midrange.com/
> 18. [56]https://lists.midrange.com/mailman/listinfo/wdsci-l
> 19. [57]https://archive.midrange.com/wdsci-l
> 20. [58]https://amazon.midrange.com/
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: [59]WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [60]https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [61]WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [62]https://archive.midrange.com/wdsci-l ;.
Help support midrange.com by shopping at amazon.com with our affiliate
link: [63]https://amazon.midrange.com
References
Visible links
1. https://www.linkedin.com/in/edmundreinhardt/
2. http://ibm.biz/rdi_hub
3. http://ibm.biz/IBMi_ACS
4. https://www.linkedin.com/in/edmundreinhardt/
5. http://ibm.biz/rdi_hub
6. http://ibm.biz/IBMi_ACS
7. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
8. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
9. https://www.linkedin.com/in/edmundreinhardt/
10. http://ibm.biz/rdi_hub
11. http://ibm.biz/IBMi_ACS
12. mailto:cfuture@xxxxxxxxxxx
13. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
14. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
15. https://imgur.com/zmnHZFw
16. https://www.linkedin.com/in/edmundreinhardt/
17. http://ibm.biz/rdi_hub
18. http://ibm.biz/IBMi_ACS
19. mailto:cfuture@xxxxxxxxxxx
20. mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx
21. mailto:wdsci-l@xxxxxxxxxxxxxxxxxx
22. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
23. https://lists.midrange.com/mailman/listinfo/wdsci-l
24. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
25. https://archive.midrange.com/wdsci-l
26. https://amazon.midrange.com/
27. https://imgur.com/zmnHZFw
28. https://www.linkedin.com/in/edmundreinhardt/
29. http://ibm.biz/rdi_hub
30. http://ibm.biz/IBMi_ACS
31. https://lists.midrange.com/mailman/listinfo/wdsci-l
32. https://archive.midrange.com/wdsci-l
33. https://amazon.midrange.com/
34. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
35. https://lists.midrange.com/mailman/listinfo/wdsci-l
36. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
37. https://archive.midrange.com/wdsci-l
38. https://amazon.midrange.com/
39. https://www.linkedin.com/in/edmundreinhardt/
40. http://ibm.biz/rdi_hub
41. http://ibm.biz/IBMi_ACS
42. https://imgur.com/zmnHZFw
43. https://www.linkedin.com/in/edmundreinhardt/
44. http://ibm.biz/rdi_hub
45. http://ibm.biz/IBMi_ACS
46. https://lists.midrange.com/mailman/listinfo/wdsci-l
47. https://archive.midrange.com/wdsci-l
48. https://amazon.midrange.com/
49. https://imgur.com/zmnHZFw
50. https://www.linkedin.com/in/edmundreinhardt/
51. http://ibm.biz/rdi_hub
52. http://ibm.biz/IBMi_ACS
53. https://lists.midrange.com/mailman/listinfo/wdsci-l
54. https://archive.midrange.com/wdsci-l
55. https://amazon.midrange.com/
56. https://lists.midrange.com/mailman/listinfo/wdsci-l
57. https://archive.midrange.com/wdsci-l
58. https://amazon.midrange.com/
59. mailto:WDSCI-L@xxxxxxxxxxxxxxxxxx
60. https://lists.midrange.com/mailman/listinfo/wdsci-l
61. mailto:WDSCI-L-request@xxxxxxxxxxxxxxxxxx
62. https://archive.midrange.com/wdsci-l
63. https://amazon.midrange.com/
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
