Decomp2 will decompile compat mode code (16bit) into 16bit assembler code, thats as far as it can go. Unless it was VERY smart and could look at external calls and deduce from their names what the original language was (eg calls to COB** might indicate COBOL, calls to istrcpy might indicate C )? Even then you cannot get label names or variable names. If the code had been compiled with debug turned on you MIGHT get more info, MIGHT?

If you direct its output to a dead printer or an ascii file, you could text the output up in qedit and look for stuff, but its VERY tedious - BTDT.
If you did the same with 2 versions of the program , go to the shell and do
diff -b FILE1 FILE2

 you will get the differences, but I suspect even that will still leave you none the wiser.
The best I have done with DECOMP and PATCH in the past is locate literals and change them,or  a couple of other things we wont go into.
jp
________________________________________
From: HP-3000 Systems Discussion [[log in to unmask]] On Behalf Of Dave Waroff [[log in to unmask]]
Sent: Saturday, 2 February 2008 6:49 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Cobol object code compare

>I saw something once on one of the old contributed tapes that
de-compiled into
>some type of assembler source (very hard to follow)  but not cobol
source.

SPL?

>If you fcopy the executable in ;char;hex and then copy/paste to
notepad, you can search for

I'd use diff to spot the changes.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *