RE: What's the scoop on the current state of WDSCi affa irs within IBM?

Programming issues, I think!

cheers
Colin.W
 
Extension   5800
Direct dial   0870 429 5800


-----Original Message-----
From: michael@xxxxxxxxxxxxxxxxxx [mailto:michael@xxxxxxxxxxxxxxxxxx] 
Sent: 10 September 2004 16:54
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] What's the scoop on the current state of WDSCi affa
irs within IBM?


So...are these JVM issues? OS (Windows) issues? Is this one of those "live
with it" issues? In other words, if you want the good stuff you have to put
up with the bad stuff?

> -------- Original Message --------
> Subject: RE: [WDSCI-L] What's the scoop on the current state of WDSCi
> affa  irs within IBM?
> From: "Colin Williams" <colin.williams@xxxxxxxxxxxx>
> Date: Fri, September 10, 2004 11:46 am
> To: "'Websphere Development Studio Client for iSeries'" 
> <wdsci-l@xxxxxxxxxxxx>
> 
> Dan,
> 
> Sounds like you've got problems with your install, or possibly not 
> enough memory.
> 
> Ive said it here before, that the only thing that regularly crashes 
> WDSC on my PC (2Ghz P4 with 1Gb of Ram), is if I use the LPEX editor 
> to edit RPG or CL. It will do things like lock up the whole PC for 5 
> or 10 minutes, or just crash WDSC and give the JVM error window.
> 
> For this reason, and the fact that even with 1Gb of Ram it is still 
> slow, I don't use it.
> 
> I do my RPG and CL editing in CODE/400, which has its own issues. 
> CODE/400 will occaisionally crash on me for no reason, literally just 
> disappear, with no error message. But I have autosave on, and have 
> only ever lost 1 or 2 lines of code, which I can live with.
> 
> I only use WDSC for editing and debugging java, which uses a different 
> editor, and running Websphere test environment, and accessing Turnover 
> CM.
> 
> >From the messages I've seen on the list so far it doesn't seem like 
> >the
> latest version of the LPEX editor is anymore stable than the previous 
> versions. Ill give it a go when we get the latest version, and drop 
> back to CODE/400 if I get any issues.
> 
> Don't give up on CODE/400, its actually very easy to use once you get 
> used to its funny ways.
> 
> cheers
> Colin.W
>  
> Extension   5800
> Direct dial   0870 429 5800
> 
> 
> -----Original Message-----
> From: Dan Bale [mailto:dbale@xxxxxxxxxxxxx]
> Sent: 10 September 2004 16:12
> 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 e-mail has been sent by a company of Bertram Group Ltd, whose 
> registered office is 1 Broadland Business Park, Norwich, NR7 0WF.
> This message, and any attachments, are intended solely for the addressee
and may contain privileged or confidential information.  If you are not the
intended recipient, any disclosure, copying, distribution or any action
taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful.  If you believe that you have received this email in error, please
contact the sender immediately. Opinions, conclusions and statements of
intent in this e-mail are those of the sender and will not bind a Bertram
Group Ltd company unless confirmed in writing by a director independently of
this message. 
> Although we have taken steps to ensure that this email and any attachments
are free from any virus, we advise that in keeping with good computing
practice the recipient should ensure they are actually virus free.
> 
> _______________________________________________
> 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.

This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.