|
I had this problem awhile back and found it to be WDSC waiting for the previous debug to complete. I am guessing it had something to do with the max allowed jobs from that job queue or something. Check WRKACTJOB for other jobs with a MSGW status that resemble something coming from WDSC. HTH, Aaron Bartell -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin Taylor Sent: Monday, February 05, 2007 2:14 PM To: wdsci-l@xxxxxxxxxxxx Subject: [WDSCI-L] SEP maxing out PC CPU I am having an intermittent problem of WDSc maxing out my PC CPU when I am using iSeries Service Entry Points to debug RPG programs. It has happened twice already today, the first time I tried it and then much later. The chronology goes like this: Execute CALL from 5250 command line. WDSc switches to Debug perspective. Job info appears in the Debug view. That is where it freezes. It never makes it to the first line of code. I tried to wait it out but it did not move. I am able to exit WDSc. Thanks -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
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.
midrange.com
