On 6/2/2010 2:59 AM, David FOXWELL wrote:
Yesterday we held an IT department meeting, where it was announced that following the installation of OS V6R1, we've now acquired a new machine and we'll be migrating at the end of the month. I thought I'd learnt from this list that a decision would have to made concerning the choice of development environment, ie, RDi (or whatever it would be called) and/or ADTS. So I asked the question what that decision was. The reply was vague and implied that we'd managed to "get round" that problem. I felt pretty stupid. So, the bulk of us will stay on ADTS with a couple using WDSc V6.1.

That's criminal.

There are some developers who are never going to give up SEU. Good for
them that your company will accommodate their desires, as odd as they
may be.

WDSC 6.0 was released May 2004, and only knows about RPG at V5R3.
WDSC 7.0 was released Jan 2006, and only knows about RPG at V5R4.
RDi 7.1 was released Jan 2008, and knows about RPG at 6.1.
RDi 7.5 was released Oct 2008, and knows about RPG at 6.1.

Your management have committed you to using a tool that's been obsolete
for 4 years, that has bugs that have been fixed for 4 years, that IBM
will not support and that will not even be able to syntax check the RPG
code you will be writing for v6.1.

You shouldn't feel stupid in the least; you asked the right question and
you got an answer that's pretty much insane. Good luck.
--buck

ps I submitted this scenario to Scott Adams for his Dilbert cartoon. No
attribution - you're safe. http://dilbert.com/blog/entry/whos_your_fodder/

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.