|
There's a RTVILESRC download available at www.as400journal.com/tips.htm as well as a RTVDDSSRC utility. Jonathan -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan Sent: 03 October 2006 20:09 To: Midrange Systems Technical Discussion Subject: Re: Print Debug Listing Thanks Simon and Vern. Somebody should write a utility to retrieve a program from a debug listing. Anyone know if anyone has done that? On 10/3/06, Vernon Hamberg <vhamberg@xxxxxxxxxxx> wrote:
An alternative is to STRDBG on the program in question. If you have the source or listing debug view, you can copy everything by rolling through the screens. Use Edit-copy for the first screen, the Edit-copy append (it's on the Edit menu) for each successive page. You might want to set the trim window to stay after each copy operation. Then take the result and paste it into WDSC LPEX editor or TextPad and clean up any junk you need to - like included items from copy members and file descriptions, etc. Again, maybe not the fastest, but it works. HTH Vern At 05:04 PM 10/2/2006, you wrote:On 03/10/2006, at 4:02 AM, Michael Ryan wrote:Anyone know how to print a debug listing? I want to RTVRPGSRC in a way - looks like some source code was lost. I know I can do it with APIs, but if there's a quick way to print the debug listing, it would save time.It's not pretty but if the program was compiled with DBGVIEW(*LIST) then DMPOBJ will show you the debug listing. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ -------------------------------------------------------------------- -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.