RE: Problems with the IBM Distributed Debugger

[jstein@xxxxxxxxxx]

Hi Ed,

One of the debugger gang suggested that the cause may be that there are
prestarted jobs Q5BWHSRV still hanging around when you issued the STRDBGSVR
command.

Try the following steps:
1. Use command
     ENDPJ SBS(QSYSWRK) PGM(QSYS/Q5BWHSRV) OPTION(*IMMED)
   to kill the prestarted job.
2. Then use command
     WRKACTJOB
     Shift F2
   to make sure there is no job Q5BWHSRV in subsystem QSYSWRK.
3. Now use command STRDBGSVR to start the debug server.

Let us know if this solves the trouble.  Thanks.
____________________________________________________
John Steinbacher, PhD.                   IBM Toronto Lab
Manager, iSeries AD Tools & Strategy      jstein@ca.ibm.com
1150 Eglinton Avenue East, Toronto Ontario, Canada, M3C 1H7

---------------------- Forwarded by John Steinbacher/Toronto/IBM on
01/19/2001 10:50 AM ---------------------------

"Barry W. Hoffman" <bwhoffman@natsem.com>@midrange.com on 01/19/2001
08:22:27 AM

Please respond to CODE400-L@midrange.com

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


To:   "'CODE400-L@midrange.com'" <CODE400-L@midrange.com>
cc:
Subject:  RE: Problems with the IBM Distributed Debugger


Hi Ed,
I know how you feel.  I haven't had a working debugger ever since they
switched from the Code400 Debugger (v3.2.1?) to the IBM Distributed
Debugger (v3.2.2?) (at least a year and a half) until just last week after
applying SP1 to wdt400 v4.5.1 it magically started working!  We are on v4r4
of OS400, too.  So my suggestion would be to upgrade to wdt400 v4.5.1 and
apply SP1.  That's the only thing that's worked for me.


Note: There are some PTFs for v4r4 listed on
http://www-4.ibm.com/software/ad/varpg/support/code400.htm
that should be applied if you haven't done so.


Barry Hoffman





 -----Original Message-----
From:   Buckingham, Ed [mailto:Buckingham@AE.com]
Sent:   Thursday, January 18, 2001 8:44 AM
To:     'CODE400'
Subject:        Problems with the IBM Distributed Debugger


The copmany I work for has recently upgraded to v4r4 of the OS on the
AS400.
Since that time we have not been able to start the debug server using the
STRDBGSVR command.  When I enter the command, I immediately get a
completion
message that my job completed normally.  If I look at my job log for the
command it shows me the following message, "Start Prestart Jobs command is
not allowed now."



 Cause . . . . . :   The Start Prestart Jobs (STRPJ) command is not valid
at


   this time for reason 1.  See reason 1 shown below:


     1 - The prestart jobs for program Q5BWHSRV in library QSYS in
subsystem


   QSYSWRK are already active.





 When I try to start a debugger session I still get the standard message
that my connection was refused and that I need to run the STRDBGSVR
command.
Has anyone had any problems with V4R4 related to the debugger?  Is there a
PTF that needs to be applied?  Any suggestions would be helpful.  Thanks!


Ed Buckingham
IS Help Desk Consultant
Phone (724) 779-5683
buckingham@ae.com


+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.

| Questions should be directed to the list owner/operator: larry@paque.net
+---



+---
| This is the CODE/400 Mailing List!
| To submit a new message, send your mail to CODE400-L@midrange.com.
| To subscribe to this list send email to CODE400-L-SUB@midrange.com.
| To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: larry@paque.net
+---