Re: Promoting WDSCi, RDp and/or RDi -- WDSCI-L

Just now, after upgrading to 9.0.1, i have a new issue.

I double click on a specific member in a sourcefile (the previous 15
members gave no problem... as far as i know), and i get a error dialog with
the message: Member "JT4FD" already in use. The name JT4FD is completely
arbitrary, no relation to the real name. The "4F" (carrot sign) has the
result of wrong conversion between ebcdic and ascii. The "4F" is nothing
new, at the bottom right i often see a message with a member name with "4F"
in it, but it didn't cause any trouble.

Anyway, after disconnetcing and connecting again the problem "disappears".

Seems that energy is only spent on new features, which look good on paper
(bullet points), but not on the overall "experience", and making rock
solid software (like OS/400 for example).

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.