Re: Program stops for SEP, but debug doesn't start in RDi

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 12/02/2016 01:00:02 PM:

From: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Date: 12/02/2016 07:15 AM
Subject: Re: [WDSCI-L] Program stops for SEP, but debug doesn't start in
RDi
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



I think everyone gets their own debug server. Here, they shut down the
subsystems every night to do backups, so every morning I have to restart
it. It shows up in WRKUSRJOB as QB5ROUTER and QB5PHSRV. I have had

issues

where something crashed in debug, and the debug server becomes

disconnected

with RDi, and the only way to get it back is to end RDI, and these two
jobs.

Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx

I don't believe that's true. I believe the basic debug server is shared by
everyone. Our System Administrator added the STRDBGSVR command to the
start up job. That way we avoided a lot of authority issues and it's
always running.

The next thing I would try would be to do a 'Verify Connection' (by
right-clicking on the Objects Subsystem in any connection). This will
check whether everything needed on the IBM i is installed and also if the
callback daemon works.

Then try starting RDI with the -clean switch--see
http://wiki.midrange.com/index.php/WDSCi_troubleshooting, then search for
-clean in the web page. The instructions are a little outdated, but they
convey the necessary information to do a clean start.

Michael Quigley
Computer Services
The Way International
www.TheWay.org