object names from executable image files

I'm trying to figure out what programs are in use on my system and what
programs can be retired. I was able to use log files from the past 18
months (must include end-of-year and other infrequent jobs), match
those to command procedures, parse the logs and coms for file specs,
and come up with a fairly complete list of programs used in batch, all
in a command procedure. I will then match the used list against all
batch programs to come up with a list of retirement candidates.

Now I'm trying to do the same for the interactive side, but I'm
stumped. Many executables are composed of multiple object files (the
batch side doesn't do this), and the compile and link listings were
discarded some time ago. I'd rather not compile and link just to parse
the listings, as some of the source files have changed from what went
into the executables (management has strange ideas how configuration
management should work). I tried analyze/image, looked at debug, and
came up with nothing. The routine lib$find_image_symbol looked
promising until I *didn't* read anything about wildcards in the symbol
name.

So, given an executable image file, how would one figure out what
objects went into creating that file?

Oh, did I mention that the source files are COBOL? And both "call
literal" and "call data name" are used?

Currently running VMS 7.3 and COBOL 2.7, though most of the executables
were compiled and linked under earlier versions.

I'm thinking that I'll have to settle for the current source files,
parse them for my list, and be very careful ... but maybe the lords of
cov will have an elegant solution.

.

Relevant Pages

  • Lahey Windows compilation problem
    ... the current working directory is on the C drive and source files are in ... I can compile and run programs. ... working directory is on a network drive, and sources are in the same ... I can create and run executables on the network drive with g95 without ...
    (comp.lang.fortran)
  • Re: Does VS.Net cache source files?
    ... the original source files were the ones that got corrupted. ... Only binaries if u use Windows 2003 where ShadowCopy makes copy of your executables. ... Michael Nemtsev:: blog: http://spaces.msn.com/laflour ...
    (microsoft.public.dotnet.general)
  • Re: Build 4 executables
    ... source files, while the other 3 have links to the source files (of the first ... But I need it to output 4 different executables everytime I build. ... The configuration manager lets me create any number ...
    (microsoft.public.dotnet.languages.vb)
Loading