× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The main issue with WDSC v4 is that we now have the benefit of hindsight 
to tell you not to bother.  It primarily existed to get the WebFacing and 
Java/Web tools in the hands of the people that needed them, especially for 
those that were implementing WAS 4.0 since the other tools at the time 
were not really capable of producing an application for that version of 
WAS.

WDSC v5 was the first version that really had the feature set in place. 
Unfortunately there were a few bugs here and there that made it difficult 
to use on a regular basis and also the performance was not that great on a 
number of the features.

WDSC v5.1 was primarily a "fit and finish" release.  Most of the nasty 
bugs have been addressed and performance has drastically improved.  That 
being said, those performance improvements are from the perspective of the 
previous releases.  To someone used to using SEU and PDM it will seem slow 
initially.  You will always be able to knock off a quick 1-line program 
change faster using 5250.  The benefits of WDSC are in the big picture 
especialy when you start combining all of the various tools from different 
sources that are capable of working so well together.

As for the OS, I would recommend XP Pro even though some others are not 
fond of it.  I like it and have good success with it, especially on the 
latest hardware such as a CPU with HyperThreading and Serial ATA hard 
disks.  If you do not like the new eye candy it can all be turned off and 
made to look like Win2K.

Mark


wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/30/2003 10:27:07 PM:

> 
> 
> 
> 
> 
> Thank you Mark for your reply.
> I am encouraged by your direction to delve deeper into WDSC.
> Perhaps because I am not skilled in JAVA I do not know how
> to do certain things, at least, I now know where to go and
> what I need to learn.
> I value your suggestions on W2K and now I understand that it
> is an issue that should be resolvable.
> 
> Maybe I should not have installed WDSC V4 but that is what IBM
> supplied and I was not aware of V5, thanks for telling me.
> 
> No one is forcing me to use WDSC, however WDSC is widely touted
> as the future direction and surely it is only prudent to try
> to keep abreast of things. May I say that I ask for help as a
> last resort and I would not post anything if I had no issues,
> is that not the reason for the existance of wdsci-l.
> 
> Regards
> Frank Kolmann
> 
> >date: Tue, 30 Dec 2003 19:32:18 -0500
> >from: "Mark Phippard" <MarkP@xxxxxxxxxxxxxxx>
> >subject: Re: [WDSCI-L] WDSC HELP needed. Installation and Education
> >
> >
> >Is someone forcing you to use WDSC?  If you want to use PDM and SEU 
then
> do
> >so.
> >
> >WDSC is using the native Windows tree and list controls.  Typing the 
first
> >few characters of an item will position the list to that item.
> >
> >Unless your PC is a bottleneck than searches should be faster from WDSC
> >than they are from PDM because your iSeries can process them faster 
from
> >WDSC than PDM can in a 5250 session.  In all likelihood, both will be 
so
> >fast as to be the same.
> >
> >MKS Implementer offers support for WDSC, and their Source Integrity
> product
> >would only be needed if you planned on writing Java/Web applications 
and
> >wanted to version control the source.  You could also use the free CVS
> >support that comes with WDSC.
> >
> >And finally the filters exist for performance.  Since the native 
iSeries
> >file system is a flat structure, library -> objects -> members you get
> very
> >large lists that cannot be lazily loaded.  This is not a Java issue it 
a
> >GUI and C/S issue.  There is no way to expand say a source file to show
> >members in a tree control and not load all of the members.  For some
> people
> >that would be a performance intensive operation.  So WDSC came up with 
the
> >concept of filters to let you define your subsets.  If you do not want 
to
> >use it you can define one or two library filters for your libraries, 
use
> >the table view and just drill down to your heart's content ala PDM. 
There
> >is even a convenient dialog to just jump to some specific locale 
without
> >creating a filter.
> >
> >I have never experienced the problems you have with Win2K, at least I
> >haven't noticed it.  I am not sure what you really mean by a 2-3 second
> >delay.  Regardless, get a decently modern CPU, 512 MB of RAM and Win2K 
or
> >XP and WDSC 5.1 performs fine.  Each release has gotten faster and that
> >should continue with the 6.0 release whenever it comes out.
> >
> >Mark
> 
> _______________________________________________
> 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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.