|
I feel and use WDSCi the same as Kelly. Right down to the CL. (Are you listening yet, IBM?) I have a 1.8ghz P4 w/1gb of ram. My performance is pretty good although, you can tell when something else has the JVM preoccupied. I get the occasional crashes. I've learned to hit CTL-S very frequently. Although, I am a musician working allot on a Windows based Audio package, so I hit CTL-S in my sleep. Once you've lost an irreplaceable performance due to XP taking a virtual dump, you learn to save often. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com Kelly Cookson <KCookson@DOTFOOD To: "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> S.com> cc: Sent by: Subject: RE: [WDSCI-L] What's the scoop on the current state of WDSCi affa irs wdsci-l-bounces@m within IBM? idrange.com 09/10/2004 11:27 AM Please respond to Websphere Development Studio Client for iSeries I may occasionally voice a complaint or two, but that's mostly for feedback to the IBM people lurking the list. I would definitely recommend installing 5.1 (get rid of 5.0). What I would say, though, is use a mix of WDSCi and traditional ADTS tools (SEU, PDM, etc) that is effecient for you. I personally love LPEX and Code Designer compared to SEU and SDA. I would strongly protest if my shop forbade us to use these tools. The CL LPEX editor is kind of an exception (are you listening IBM?). I am go-ether-way when it comes to RSE and the debugger. I use a combination of RSE and PDM. whichever seems most convenient. I often use ISDB, though as we move to ILE, I may start using the WDSCi debugger more. WDSCi is a good addition to the toolkit, just not a replacement for the existing tools. Use a mix. That's my two cents. Thanks, Kelly -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Dan Bale Sent: Friday, September 10, 2004 10:12 AM To: WDSCI-L@xxxxxxxxxxxx Subject: [WDSCI-L] What's the scoop on the current state of WDSCi affairs within IBM? Don't really want to stir up a hornet's nest here, but... I understand that you'll always hear more about the negative things going on with a product than positive things, but I can't help but get past this image that WDSCi is far from being ready for prime time based on the problems described in this list. Some of the problems reported here that stick in my brain are lost source members after hours of modification (sends shivers down my spine; I think they'd have to call paramedics if that happened to me), frequent WDSCi crashes (requiring reboots), performance being as slow as molasses on a cold Minnesota day in February (despite some users reporting some really souped up PCs). These issues do nothing to build confidence in a product. I know the IBM team participates on this list, and for that I am extremely grateful. I would be interested in knowing if there's been any talk of a redesign from scratch effort or something else drastic to address these glaring problems. Kinda like how PC Support was replaced by a completely rewritten Client Access years ago. It is also my understanding that WDSCi was originally developed in Rochester and now that has been transferred to Toronto (do I understand that correctly?), and maybe we are experiencing the reasons for that move. I installed WDSCi 5.0, which is an older version, but is the latest version I can find around here. Our iSeries is on V5R2, so don't know if a newer WDSCi should have been included in that. Since I have only a PC with 128MB of memory and 700MHz Pentium, I thought I might at least try CODE400, but I'm not happy with some of the behaviors (i.e., member line numbers resequenced at .01 increments, source statement change dates set to zero). I haven't been able to get the "Complete the installation of CODE and VisualAge RPG" shortcut to go away, even though I've run it twice now, so I am unsure as to whether I can use either with confidence. Clicking on the "Development Studio Client for iSeries" shortcut ("C:\Program Files\IBM\WebSphere Studio\wdsc.exe" -feature com.ibm.wdsclient) brings up an Eclipse dialog box that starts with: JVM terminated. Exit code=1 followed by 12 lines of ... parameters or somesuch. Of course, there's no way to copy/paste this information. Perhaps someone with Java experience would understand what is being communicated here, but that's not me, nor anyone else in my company. db _______________________________________________ This is the Websphere Development Studio Client for 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 Websphere Development Studio Client for 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 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
