RE: JD Edwards problem in Debugger.

[berestet@xxxxxxxxxx]

Hi  Danny,
I wonder how you start your Distributed Debugger session. This might sched
some light as to why you are getting this problem.

Thanks,
Vadim Berestetsky
Distributed Debugger Development




                                                                                
                                                                      
                      Daniel.Hayes@xxxxxx                                       
                                                                      
                      uster.com                  To:       "CODE/400 Discussion 
& Support" <code400-l@xxxxxxxxxxxx>                                   
                      Sent by:                   cc:                            
                                                                      
                      code400-l-bounces@x        Subject:  RE: JD Edwards 
problem in Debugger.                                                        
                      idrange.com                                               
                                                                      
                                                                                
                                                                      
                                                                                
                                                                      
                      02/20/2003 09:05 AM                                       
                                                                      
                      Please respond to                                         
                                                                      
                      CODE/400 Discussion                                       
                                                                      
                      & Support                                                 
                                                                      
                                                                                
                                                                      
                                                                                
                                                                      





Bob,

Thanks, but that is not the issue.

I know that one quite well.

If it were that one, it would never get to the point (two programs deep)
where I
am having the problem.

Danny




code400-l-bounces@xxxxxxxxxxxx on 02/20/2003 07:53:35 AM

Please respond to "CODE/400 Discussion & Support" <code400-l@xxxxxxxxxxxx>

To:   "CODE/400 Discussion & Support" <code400-l@xxxxxxxxxxxx>
cc:    (bcc: Daniel Hayes/IT/Corporate/Blockbuster)

Subject:  RE: JD Edwards problem in Debugger.



Daniel

I believe you are running into a JDE security issue.  JDE provides their
own green-screen source debug to work around this.  I believe the
command is JDEDBG.  I do know that you can use IBM's STRISDB debugger;
it will fail on the first attempt, but you can tell it to try again and
it will function properly the second time around.  I have not played
with the CODE debugger enough to offer any suggestions for work-arounds.
Sorry.

Bob Cagle
IT Manager
Lynk, Inc.
Phone: 913-492-9202 ext 41
Fax: 913-894-1556
BCagle@xxxxxxxxxxx


-----Original Message-----
From: Daniel.Hayes@xxxxxxxxxxxxxxx [mailto:Daniel.Hayes@xxxxxxxxxxxxxxx]

Sent: Wednesday, February 19, 2003 5:16 PM
To: CODE/400 Discussion & Support
Subject: JD Edwards problem in Debugger.



I keep getting this error when I try to run a CL program taht call the
program I
want to debug.

<Spawned (child) process 432951/QUSER/JB55511 is stopped. (G C)>

This message shows up on my Green Screen, if I give it a 'G',  I get a
Program
Terminated popup on my Debugging session.

This is a JD Edwards 'Dream-Writer' program.


_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l


_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l







_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l