Re: Promoting WDSCi, RDp and/or RDi

RTC - Rational Team Concert - uses, I believe, iProjects as its underlying structure. It gives you the ability to combine several iProjects into one work item, something like that.

RTC is usable as a software change management app - and it connects nicely to RSE. So does Softlanding's Turnover, which we use here. I assume Implementer, Arcad, and Aldon do, as well.

Because we use an SCM, iProjects just aren't needed. And iProjects on their own, that has never felt really useful to me, anyhow - restriction to a single library has bugged me from the start.

YMMV

Vern

On 12/30/2013 3:55 AM, Paul Bailey wrote:

I use the same method, and try to encourage that with my colleagues. I would like to use the iProjects system, particularly for the disconnected source features and ability to use our existing git source control system to control the RPG too, but you lose so many features compared to the RSE filter method that it is just not worth the effort.

I'd raise an RFE to get iProject functionality somewhere near RSE functionality, but it would either be a single vague RFE or too many smaller specific RFEs and the work involved just seems overwhelming.


-Paul



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of darren@xxxxxxxxx
Sent: 26 December 2013 19:10
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Promoting WDSCi, RDp and/or RDi

I tried the "Projects" way, and it has some issues. I found a better way.
I use connections for environments, like Development-All, ERP-Production, and ERP-Test as examples. Each "connection" has a library list associated with it. I then use filter pools defined as "Active", "On-Hold", and "Closed" to indicate project status and give me somewhere to keep completed projects. Within the "Active" filter pool, I create filters where I specify each member directly, but I make the library *USRLIBL. Through the magic of filters and pools, each of these filters and pools is linked in each connection through the magic of how RSE works, so I can see my source at production and at development. I use the "Object Table" in unlocked mode, so that I see the list of source members for the project I'm working on and work with members that way.

As projects change status, the filters can be right-clicked and moved to a different filter pool/status such as "Closed."




From: whatt sson <whattssonn@xxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 12/23/2013 11:09 AM
Subject: Re: [WDSCI-L] Promoting WDSCi, RDp and/or RDi
Sent by: wdsci-l-bounces@xxxxxxxxxxxx



I have not used it, i'm planning to, but instead of editing file members directly (the old PDM approach) i think it maybe works better if using "projects". I.e., sources are edited locally, and then pushed to the server periodically. This is the preferred way anyway.

But this requires that collegues also adopt the "projects" way.


On Thu, Dec 19, 2013 at 12:16 PM, Paul Bailey <PaulBailey@xxxxxxxxxx>
wrote:

I've been using WDSCi/RDi/RDp (from now on, just RDi) for many years,
and I have been the primary (if not sole) driver in getting my
colleagues to use it.

In discussions with my colleagues I point out the features that make
things easier, the tools that could make their programming lives just
a little better. This is a tough argument because SEU/PDM still does
things that can't be done in RDi, but I usually have a 50% success
rate in the number of colleagues adopting RDi. The facts that SEU is
now static even

if

RPG is not, and the general usage of an Eclipse tool will help
advance/expand their careers and skillsets are also strong arguments.
The learning curve is a downside, but I try to skirt around that.

I'm under time constraints all the time. It takes an hour or more to
install and/or upgrade RDi and that time is often precious and needed
elsewhere, so at the moment I am the only user in my company using the
latest version (9.0.1). Two of my colleagues are still using v8.5 and

today

*both* of them came across the bug where source was saved in RDi but

didn't

turn up on the IBM i (no errors, the source just didn't get
transferred.) There were tantrums, rants and toys were thrown out of
prams (slight exaggeration, but you get the idea?) and now both are
refusing to use the tool until it is updated. Their faith in the tool,
and in my advice, has been damaged.

I guess I am just venting my frustration here and I apologise for
bending your ears (screens?) but I am just wondering how successful
others are at getting their colleagues to use the tool. What are your
best arguments

for

all the SEU-fanboi nay-saying, and how do you recover from
faith-damaging errors such as the one my colleagues suffered today?


-Paul.


PS Can I get some commission from IBM for being the only person in
four different companies over the past 10-15 years that has championed RDi?




Important, this email transmission and any files with it are strictly
confidential to the intended recipient and may be legally privileged.
Any views or opinions presented are solely those of the author and do
not necessarily represent those of BHSF. If you are not the intended

recipient,

you must not copy, disclose or distribute its contents in any way. If
you have received this e-mail in error, please notify the sender and
delete

the

e-mail from your system.

We have taken steps to ensure this email and attachments are free from

any

virus but do not accept any responsibility once this e-mail has been
transmitted. You should scan any attachments for viruses. No contract
may be concluded on behalf of BHSF Limited by e-mail.

Registered Office: BHSF Limited, Gamgee House, 2 Darnley Road,

Birmingham,

B16 8TE. www.bhsf.co.uk Registered in England number 35500. BHSF
Limited is authorised by the Prudential Regulation Authority and
regulated by the Financial Conduct Authority and Prudential Regulation Authority.
--
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.

Scanned by MailDefender - managed email security from intY - www.maildefender.net

Important, this email transmission and any files with it are strictly confidential to the intended recipient and may be legally privileged. Any views or opinions presented are solely those of the author and do not necessarily represent those of BHSF. If you are not the intended recipient, you must not copy, disclose or distribute its contents in any way. If you have received this e-mail in error, please notify the sender and delete the e-mail from your system.

We have taken steps to ensure this email and attachments are free from any virus but do not accept any responsibility once this e-mail has been transmitted. You should scan any attachments for viruses. No contract may be concluded on behalf of BHSF Limited by e-mail.

Registered Office: BHSF Limited, Gamgee House, 2 Darnley Road, Birmingham, B16 8TE. www.bhsf.co.uk Registered in England number 35500. BHSF Limited is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and Prudential Regulation Authority.