I haven't started using CC yet.
However, knowing our system and how we go about testing, I would rather UpdProd(*No) to be the default and that it could be changed by the user. I foresee using CC more often when testing than over something in production (not that I don't see doing that as well).

I'm aware that we have a horrible test environment.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Monday, July 14, 2014 1:57 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Cc: Morris Kwan
Subject: Re: [WDSCI-L] Fw: RDi 9.1 Code Coverage DEBUG UPDPROD


I apologize, I asked that backwards.

I was going to make UPDPROD(*YES) the default for all code coverage.
Would this every be a problem?



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i



Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/






From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Clientfor System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 14/07/2014 12:39 PM
Subject: Re: [WDSCI-L] Fw: RDi 9.1 Code Coverage DEBUG UPDPROD
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



From my perspective and knowing our environment I would say all the time.

We use a separate LPAR for development so at the most we end up
corruptioning user sand box testing. We refresh our production data to
our production level libraries on a regular basis. We also have the STRDBG command default set as UPDPROD(*YES) right now on the DEVE LPAR.
I and most all other developers set the RDi IBM i Debug option checked on.


Thanks, Matt


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Monday, July 14, 2014 10:12 AM
To: Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries
Cc: Morris Kwan
Subject: Re: [WDSCI-L] Fw: RDi 9.1 Code Coverage DEBUG UPDPROD


I understand the desire to use UPDPROD(*NO) while debugging in order to prevent data corruption while debugging programs. Under what circumstances would UPDPROD(*YES) be useful when analyzing code coverage?



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i






Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx

RDi YouTube: 8200
Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON
L6G 1C7
Find me on: LinkedIn:
Canada
http://ca.linkedin.com/in/edmundreinhardt/








From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Clientfor System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 14/07/2014 12:09 PM
Subject: Re: [WDSCI-L] Fw: RDi 9.1 Code Coverage DEBUG UPDPROD
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



I would prefer to have the tool use the current command default, either as default option over all or as the default on each code coverage set up. The latter option then gives me the ability to set it to
UPDPROD(*NO)


Thanks, Matt


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, July 14, 2014 9:46 AM
To: Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries
Subject: Re: [WDSCI-L] Fw: RDi 9.1 Code Coverage DEBUG UPDPROD

I think you should pick up the existing option "Run / Debug" --> "IBM i Debug" in 9.0.1

I assume it is still there in 9.1?

Charles


On Mon, Jul 14, 2014 at 11:28 AM, Edmund Reinhardt < edmund.reinhardt@xxxxxxxxxx> wrote:


Hi Matt,
Thanks for catching this, I have spoken to the developer and this will
be
fixed for next release.
I assume that we should always use UPDPROD(*YES) rather than exposing
this
as an option.
Unfortunately there is no work around available in the RDi 9.1



From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Date: 11/07/2014 06:35 PM
Subject: [WDSCI-L] RDi 9.1 Code Coverage DEBUG UPDPROD
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



For some reason Code Coverage uses STRDBG UPDPROD(*NO).



I know this because I get "Member XXXXXXXX cannot be opened while
UPDPROD(*NO)." then the coverage job ends.



I see no where I can set this debug option to UPDPROD(*YES). My
debug
option under Preferences -> Run/Debug -> IBM i Debug has the option
"Update production files" set on.



We have overridden the system command default to be UPDPROD(*YES) and
its still at that value.



Did I miss an option in Code Coverage? Or does this require an RFE.



It makes this difficult to run Code Coverage without moving ALL
production level data objects to a test library. Sub programs that
are not in test are called attempting to open production data and
failing.





Thanks, Matt

--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a

message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.