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



Hey Adam,

If this occurs again:
1.  Try using save as before clearing your file cache, that way you won't
loose your changes.
2.  Please turn info logging on, save again, then send me the .log file
offline at batthish@xxxxxxxxxx
This way I can follow up with some ammo for the appropriate developers.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/13/2006 10:24:07 AM:

Here is the scenario:

I am adding a procedure to a service program, so I was adding an EXPORT
line to the binder source.  Copied the production version to my
development library, added the line and saved, then ran CRTSRVPGM.  When
I
tried to compile the program using the new procedure, I was getting
'symbol not found'.  I eventually realized that the version of the binder

source on the System i did not have the line I had added, even though it
had shown up when opening the member in WDSC.

I know this has come up before, but the resolution for me was to go to
'Window->Preferences; Remote Systems->File Cache; Clear cache'.  After
that everything seems to be hunky-dory again.  So, if this happens to you

maybe this is something to try before reinstalling or recreating your
workspace.

I was unable to recreate the error - if anyone has any other details on
this I'd be really glad to hear them.

HTH,
Adam


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.