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



Morgan,

Try to run "dlogoff" on your DOS prompt to logoff all the servers.  The try
to invoke the debugger again to see if you could get the Logon dialog.

Regards,

Xuan Chen, Debug for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@ca.ibm.com



"Morgan Najjar" <morgan@appx.com>@midrange.com on 01/21/2002 09:37:13 AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   <code400-l@midrange.com>
cc:
Subject:  Distributed Debugger No Login Prompt



Hello again,

Well, I had the distributed debugger working on a Win 98 machine, but it
was pretty slow.  I loaded WDT on a faster Win 2000 machine and
everything runs much better, except of course, the program I need most,
the distributed debugger.

After I fill in the "Load Program" dialog and click on "Load", I see the
"starting" crawl indicator, but it never proceeds to the login dialog.

I've ended and re-started the debug server.

Any ideas appreciated.

Thanks

Morgan

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.