Difference between revisions of "WDSCi troubleshooting"

From MidrangeWiki
Jump to: navigation, search
m (shorten external link using wikisyntax; add section for categories)
m (Added 'Workspace in use' debugging)
Line 14: Line 14:
 
==Where is my workspace stored?==
 
==Where is my workspace stored?==
 
File > Switch workspace
 
File > Switch workspace
 +
 +
==I'm getting a 'Workspace in use' error==
 +
Use Windows Explorer and drill down into your workspace.  There's a directory called '''.metadata'''  Inside that directory is a file called '''.lock'''  Delete that file and restart WDSC.  If you can't delete that file, you may have some bits of Eclipse still running.  Either reboot your PC or use the Windows task manager to kill eclipse.exe  You may also have to kill the Java Virtual Machine, too.  It'll be called javaw.exe.  Unfortunately, you'll probably have more than one.  I'd kill the one using the most memory, but that's no guarantee to be the right one, so watch out!  In this case a reboot is a safer mechanism.
  
 
==I have a custom compile command.  How do I get the error list back into WDSC?==
 
==I have a custom compile command.  How do I get the error list back into WDSC?==

Revision as of 20:42, 15 June 2007

Tips on troubleshooting WDSCi:

First, search the archives

How do I clear the cache?

There are two caches to be cleared: Window > Preferences > Remote Systems > File Cache > Clear-"Clear cached files"

Window > Preferences > Remote Systems > iSeries > Cache > Clear-"clear the current cache"

NOTE! You must restart your workspace immediately after clearing the cache!

Where is my workspace stored?

File > Switch workspace

I'm getting a 'Workspace in use' error

Use Windows Explorer and drill down into your workspace. There's a directory called .metadata Inside that directory is a file called .lock Delete that file and restart WDSC. If you can't delete that file, you may have some bits of Eclipse still running. Either reboot your PC or use the Windows task manager to kill eclipse.exe You may also have to kill the Java Virtual Machine, too. It'll be called javaw.exe. Unfortunately, you'll probably have more than one. I'd kill the one using the most memory, but that's no guarantee to be the right one, so watch out! In this case a reboot is a safer mechanism.

I have a custom compile command. How do I get the error list back into WDSC?

Technote 1231854 from ibm.com

Categories