× 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.



Dear Violaine,

FYI my PC config is Win XP Pro SP2 1.73GHz 797 MHz, 1.24 GB ram running
WDSc AE V5.1.2.6.
 
Thanks & regards,
 
Leonard Thum
thumls@xxxxxxxxxxxxxxx



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Leonard
Sent: Tuesday, April 25, 2006 4:12 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Delays while Editing
Importance: High

Dear Violaine,

I have problem editing my CLLE source( approx. 102 lines).

I tried for many times for 3 days to make it available offline thru RSE;
each time I get a not responding( javaw.exe process running chewing up
my pc 95% of CPU). Each time I will have to end task and restart WDSc.

Then I tried to edit thru LPEX and no luck, stop at opening up the
program source screen(I can see the loading bar and waited for more than
half an hour) and decided to end the WDSc again.

I cleared my cache then retried; does not help. I had also disable the
syntax check.


This is my .log file. Let me know if you need more information.
________________________________________________________________________
____

!SESSION Apr 25, 2006 14:24:42.546
---------------------------------------------
java.fullversion=J2RE 1.3.1 IBM J9 build 20031201 (JIT enabled)
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
Files\IBM\WebSphere Studio\Application
Developer\v5.1.2\.\eclipse\eclipse.exe -data C:\Leonard\MY IBM
SSC\Workspace -feature com.ibm.wdsclientadv -install file:C:/Program
Files/IBM/WebSphere Studio/Application Developer/v5.1.2/eclipse/
!ENTRY com.ibm.etools.systems.core 4 0 Apr 25, 2006 14:24:42.546
!MESSAGE ISeriesMemberTransfer: error getting member from server
!STACK 0
java.net.SocketException: socket closed (code=0)
        at java.lang.Throwable.<init>(Throwable.java)
        at java.lang.Throwable.<init>(Throwable.java)
        at java.net.SocketException.<init>(SocketException.java:46)
        at java.net.SocketInputStream.socketRead(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:113)
        at
com.ibm.as400.access.DataStream.readFromStream(DataStream.java:48)
        at
com.ibm.as400.access.DDMDataStream.construct(DDMDataStream.java:94)
        at
com.ibm.as400.access.AS400ThreadedServer.run(AS400ThreadedServer.java)
        at java.lang.Thread.run(Thread.java:795)
!ENTRY com.ibm.etools.systems.core 4 0 Apr 25, 2006 14:24:42.843
!MESSAGE EVFC9104E: SUB#0:Kulas1
!ENTRY com.ibm.etools.iseries.perspective 4 0 Apr 25, 2006 14:30:53.375
!MESSAGE The TCP/IP network connection to Kulas1 was dropped.
________________________________________________________________________
____




 
Thanks & regards,
 
Leonard Thum
thumls@xxxxxxxxxxxxxxx



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Violaine Batthish
Sent: Thursday, April 20, 2006 6:23 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Delays while Editing

Hi Justin,

You don't mention what source type you are editing.
There have been several fixes in 6.0 and 6.0.1 for performance issues in
the ILE RPG parser, so you should obtain the lastest fixes.

Its also good to note the following:
1. automatic syntax checking for SQL in ILE RPG need to connect to the
host, so if you have a slow connection, then this can affect
performance.
2. Automatic syntax checking for CL, genrally also requires a connection
to
the host, and isn't as fast as the other syntax checkers (which is why
its
off by default).  I am working on improvements here.
3.  If you have very large source with sequence numbers with an
increment
of 1, then you may see slower performance when editing.  To gain the
best
performance in this case, try resequencing your source
4.  If you have turned informational logging on (as part of a support
request), you should turn it off.  While this puts extra information in
the
log for us, depending on the parser, this can slow everything right
down.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry




 

             "Justin Taylor"

             <JUSTIN@lorencook

             .com>
To 
             Sent by:                  <wdsci-l@xxxxxxxxxxxx>

             wdsci-l-bounces@m
cc 
             idrange.com

 
Subject 
                                       [WDSCI-L] Delays while Editing

             18/04/2006 02:46

             PM

 

 

             Please respond to

                 Websphere

                Development

             Studio Client for

                  iSeries

             <wdsci-l@midrange

                   .com>

 

 





I upgraded to WDSC 6 some months ago.  Just recently, I have started to
experience delays while editing.  WDSC will be performing fine and then
it will start pausing.  I will change a line of code, then hit ENTER and
there will be a 5+ second delay during which the program appears to be
not responding.  At the same time a "javaw.exe" process is at 99% CPU
utilization.  Network utilization is less than .5%.  I shutdown my
computer and I am still experiencing the problem.

I am running version 6.0.1 with the latest updates on a 2.8ghz Pentium
with 1gb RAM.





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-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.