Re: Source/object mis-match

[Scott Klement <klemscot@xxxxxxxxxxxx>]

Use the DSPOBJD API to list the objects to a file.   Each object
will have a source lib/file member in it.  Except for ILE *PGM and
*SRVPGM objects.

For the ILE objects, call the QBNLPGMI (for *PGM) or QBNRSPGM (for
*SRVPGM) APIs to find out what modules were used to compile the program,
and what source lib/file/member was used there.

In each of these situations, you can retrieve the date that the source
file was changed.  (Actually, I've only done that for ILE objects, but I
assume there's a way for the OPM stuff as well)  So you could then call
the QUSRMBRD API to find out when the source was changed -- you could use
this to determine whether they were last changed at the same time, and
therefore figure out if they match, if that's an issue for you.

Depending on how deluxe you want this to be, it could turn into a
large project indeed :)


On Tue, 5 Feb 2002, Richard Reeve wrote:
> I have been tasked to identify source/object mis-matches for a given
> library.  Other than compiling each object in to a temporary library
> and comparing object sizes how might I go about identifying
> mismatches?