RE: Additional statement numbers in iSeris source with5.1.2.3

Don,

Not a problem replying here.

After reading your earlier post about 5.1.2.3 being primarily a memory leak fix 
I also figured it wasn't the cause.  I did make two other changes the same day 
but I don't remember in which order they occurred.  I think they happened in 
the order I have them listed.

- While working with IBM support on an unrelated WDSc issue on a co-workers 
machine I learned that I was actually working in Site Developer not WDSc all 
this time.  This explained a question about why my release and build levels 
never changed after applying updates.  I created a new shortcut from the start 
-> programs menu option so now I'm actually running WDSc.

- We have disk space issues here so everyone's workspace is in a different 
place depending on how their system is configured.  Can't get it changed, long 
story.  I thought I'd try using the IFS on our development machine as my 
workspace.  Previously my workspace was on drive C.  I created the folder 
'\rcheva1\WDSc Workspace' and entered that location when prompted at WDSc 
startup for a workspace location.  This probably ties into your questions about 
the server going down although I don't know how at the moment.  There were no 
issues with the system that I'm aware of.

Let me know if you need anything else.

Rick

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Don Yantzi
Sent: Thursday, December 16, 2004 9:20 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Additional statement numbers in iSeris source
with5.1.2.3


Hi Rick,

I got your log file and am replying here for the archives (hope you don't
mind.)  It looks like one of the metadata files has gotten corrupted (one
of the ones that maintains local history for file modifications.)  Can
you:

1.  Close any open editors and shutdown the workbench
2.  Delete the following folder (you might want to just copy it some place
else for now, actually can you zip this up and send it to me?):
        I:/rcheva1/WDSc
Workspace/.metadata/.plugins/org.eclipse.core.resources/.history
3.  Start the workbench back up and give it a try

Do you have your workspace on a local or network drive?  The first error
in the .log file is one where the workbench is trying to write to the
.index file in the above folder and it fails.  If it is a network drive do
you recall the network dropping at all yesterday at approximately Dec 15,
2004 16:03:24.562  :-)    Or the disk might be full?

I am pretty sure this is not related to applying the 5.1.2.3 update, but
is just a coincidence.  I'll keep digging around to see if I can find
anything else that might suggest why this happened and why it didn't
recover.

Thanks.

Don Yantzi
Technical Release Lead
WebSphere Development Studio &
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal:  IBMCA(yantzi)  -  Internet: yantzi@xxxxxxxxxx


Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain legally 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.