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



It seems your service entry point server ran into some problem (it was 
waiting for the debug sever to give it notification to release the 
program, but some how the debug session could not be started up 
correctly).

Could you please see if there is a job called qb5phsrv in your qusrwrk 
subsystem which is running under your user profile?  Please terminate that 
job if there is any.

Which OS 400 version your are running?  Can you reproduce it everytime?

Thanks,

Xuan Chen,  Problem Determination Tools for iSeries
(905) 413-3769 T/L 969-3769
xuanchen@xxxxxxxxxx





"Justin Taylor" <JUSTIN@xxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/29/2007 12:32 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] SEP maxing out PC CPU






Well it appears that the problem of SEP maxing out your PC CPU still
exists in version 7.

I had the SEP set and had debugged the program a couple of times.  I
re-compiled the program and refreshed the SEP.  I called the program via
5250 and WDSc pegged out my CPU.  In version 6, I was able to X-out WDSc
and then restart it.  With version 7, it would not close and I was
forced to physically power off my machine.

I have restarted my PC and am trying to set the SEP again.  I am
receiving a "Host: CPF7102 Unable to add breakpoint or trace." from
WDSc.

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.