|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Hi Vadim, I have compiled the program with the debug options before moving it to production. My problem is that I'm pretty new to code/400 and I've only used the debugger from code/400. I'm trying to just call the Distributed Debugger and have it point to the proper comm server and program. I'm not sure what to enter on the "attach" window (in all necessary tabs). I put a question out here last week about my help no longer displaying (I have no idea why I lost it!!), so when I try to get help on the window, all I get is "page cannot be displayed" for URL http://localhost:49213/cgi-bin/vahwebx.exe/vahelp/va400/Extract/0/debugger/u i/ubdbprcs.html I've created a comm server for production, which I assume is necessary, but the "host" fields on the window (all tabs) only shows localhost. Is this correct? Am I stupid? (ha ha. DON'T answer that one!) Thanks Chris -----Original Message----- From: berestet@ca.ibm.com [mailto:berestet@ca.ibm.com] Sent: Monday, September 17, 2001 1:08 PM To: code400-l@midrange.com Subject: Re: Using the debugger on a system other than the one where the sourc e resides?..... Hi Chris, Actually, you have two options here, but in both cases your objects on a production box will need to have debug data: 1) Compile objects with *LISTING debug view and move them to your development box. Then you can use CODE/400 debugger to debug your program using *LISTING view. 2) Compile objects with *SOURCE debug view and move them to your development box. Copy source somewhere on your workstation. When you try to debug your program on a development machine, you will be prompted for the source location. At this point you can specify such location. Hope this helps, Vadim Berestetsky Distributed Debugger, IBM Toronto Lab Phone (416) 448-4403; T/L 778-4403 Internet: berestet@ca.ibm.com Chris Proctor <cproctor@gartsports.com>@midrange.com on 09/17/2001 01:53:48 PM Please respond to code400-l@midrange.com Sent by: code400-l-admin@midrange.com To: "CODE400-L (E-mail)" <CODE400-L@midrange.com> cc: Subject: Using the debugger on a system other than the one where the sourc e resides?..... This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Hi all, I'm hoping someone has an answer for this one..... We have a development box where all the source resides. Once the application is tested, it is moved to our production box. My dilemma is, I would like to use the debugger in CODE/400 to debug a program on production. The reason for this is because the development box database does not get refreshed very often. I know.......BIG SURPRISE, right? ha ha. Can I use the debugger against the compiled object that was moved to product, and if so, how? Thanks for any suggestions (short of copy the files to development! ;-) ). Thanks, Chris Proctor Manager of Systems Integration Gart Sports Denver _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-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
