This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
[ Picked text/plain from multipart/alternative ]
On Sept 1 Reeve Fritchman reported that:
>I've had a couple of defined servers (TTG, TTGBNA, VOLT, etc.) for CODE
>running under WDSC 4.0 with the recent SP on Win2000 for months.  They
>worked yesterday at 1900.
>Today I show up and try to use my default server, TTG.  "Not
> found"...interesting.  So I check the communications console and find my
>servers are now OS400A, OS400B, and so on.  They work (i.e. I can get
>through to the server)...
>I'd like to use my friendly names but renaming the servers hasn't worked:
>EVFCSVRD.exe blows up when I rename and click for the PTF check.  If I
>check to PTF's, EVFCSVRD.exe closes normally but the OS400* names are back
>when I open the comm. console again.  I've deleted the OS400* servers,
>rebooted, added them back, rebooted, sacrificed a chicken, all to no avail.

Late yesterday the same thing happened on my ThinkPad running WDSc 4.0 + FP2
on WinXP + SP1.  It had been working fine, just as Reeve's, in fact the MRU
file list referred to the correct server names and trying to reference an
entry on the MRU files list fails because of the server name change.  I'm in
one chicken, plus Reeve's one... No Joy.  There's an egg shortage looming.
I get the same error on the ptf check, even though I've run it successfully
many times in the recent past.

Any ideas?  I'm only using Code at this point, no designer, no projects, no
WDS.  In fact I just use an icon to Code off my toolbar, not going through
Eclipse.  Both iSeries are on v5r1 and had the requisite ptf's applied to
make the comm console happy.


Tom Westdorp

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2022 by 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.