|
date: Tue, 10 Jan 2006 11:55:05 -0500 from: Xuan Chen <xuanchen@xxxxxxxxxx> subject: Re: [WDSCI-L] Getting Debugger to work Hi Doug, For the WDSC Integrated Debugger: Could you please check if there is a QUSRWRK subsystem in your iSeries? If yes, is the job QB5ROUTER running in that subsystem? If not, is the job QB5ROUTER running in QSYSWRK subsystem instead? If you find your job is running in QSYSWRK subsystem, could you please end debug server. Create the QUSRWRK system, and re-start the debug server. We've awared of this problem, and the fix will be available in the next fix pack of WDSC. For now, you need to submit the debug server job to QUSRWRK subsystem. If it still does not work for you, I will take a further look at it. For the Distributed Debugger: Just wondering if your PC is under a firewall or if you use NAT (Network Address Translation) in your environment? Thanks, Xuan Chen, Problem Determination Tools for iSeries (905) 413-3769 T/L 969-3769 xuanchen@xxxxxxxxxx ------------------------------------ [Edwards, Douglas] Xuan, A complete answer to your questions: Concerning Integrated Debugger: There is a QUSRWRK sbs, and the QB5ROUTER is running in it. FYI - This job does appear when I look at it from RSE. Concerning Distributed Debugger: As far as I know, my PC does not run any firewall software, not even the Windows version. Our network is protected by a firewall, but I am behind that, and there is no firewall between me and the iSeries. Concerning NAT, my PC is not using it, although we do use it on our network. I have perhaps a pertinent question - should there be 2 of these jobs/ports running? I know the Distributed debugger uses port 3001. But when I start the debug server, it sends back a message that it is started on 3825. Is this correct? Doug
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.