× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Are you sure there is no compression? It may be that DMPOBJ decompresses the object for you. We can not be sure unless we get the answer from one of the developers of the OS.

Jonathan Mason wrote:

Intrigued by Simon's suggestion to use DMPOBJ to view the compiled source
for a program or module I tried it and was surprised at the results.

Many years ago on a System/36 I needed to recover some program source and
through investigation found that the source was compressed on the disk, with
multiple occurrences of the same character being reduced to a four byte
sequence along the lines of 72 *'s became something like x'00FE48C3'.

My surprise was that when looking at the dumped object listing there's no
compression in the object at all:

04A260   F040C340 40404040 40404040 40404040   40404040 4040C986 40404040
40404040  *0 C                   If        *
04A280   97F1C9A3 8594C9C4 404C6E40 7D5CC1D3   D37D4040 40404040 40404040
40404040  *p1ItemID <> '*ALL'              *
04A2A0   40404040 40404040 40404040 40404040   40404040 40404040 40404040
40404040  *                                *
04A2C0   4040C2F0 F3404040 40404040 F0F6F1F0   F0F24040 404040F0 F2F1F5F0
F0404000  *  B03       061002     021500   *
04A2E0   40404040 40F1F4F8 F140C340 40404040   40404040 40404040 40404040
4040C986  *     1481 C                   If*

I've always been aware that including debug information in the program
increases the object size, but would have thought that some level of
compression would have been included.  What does the list think?

Jonathan


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: 02 October 2006 23:05
To: Midrange Systems Technical Discussion
Subject: Re: Print Debug Listing


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                                   \ /

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.