Re: Ending the Comm Daemon -- CODE400-L

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

Subject: Re: Ending the Comm Daemon
From: haklui@xxxxxxxxxx
Date: Fri, 25 Oct 2002 09:46:35 -0400
List-archive: <http://archive.midrange.com/code400-l/>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

If the communications daemon keeps coming back, probably there is still
application running somehow, trying to send request to a server.
Normally, this can be ended by following these steps:

1.End the Designer
2. codeedit /CM EXIT
3.Shutdown all servers
3. Close the Communications daemon.

If the above steps have no effect, then as Reeve has pointed out, end all
EVFC* processes from the Windows task manager.


Best regards,
    Hak
_______________________
Hak Lui
AS/400 AD, IBM Canada Ltd.
e-mail: haklui@ca.ibm.com

As an Amazon Associate we earn from qualifying purchases.

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.