Expert: Concise Systems/Laird Scranton - 1/24/2009

Question
QUESTION: Dear Sir :
   I try to match a compiled object to a source member with the method of recompiling source member to a temp library and comparing the object size. But my company upgrade our AS/400 OS from V5R2 to V5R4 last year. I found that in different OS version, the same source member will produce different size object. So, I can't identify the source member is the correct version. I must identify about 5000 object's source version in short time. IS there any suggestion to do it ?

ANSWER: If you use the DSPOBJD command, you can create a file containing information about all of your programs, including the name of the source file, library and member from which it was compiled. To do this, key:

DSPOBJD OBJ(*ALL) OBJYPE(*PGM) OUTPUT(*OUTFILE) OUTFILE(name of new file to hold DSPOBJD info)

Among others, this file will include the fields:

ODSRCF  -  Name of source file
ODSRCL  -  Name of source library
ODSRCM  -  Name of source member

Hope that helps!

- Laird

---------- FOLLOW-UP ----------

QUESTION: Dear Laird :
    Thanks for your kindly help. I have done the step you provide in the mail before your reply. The challenge I faced is that my company consolidated all source member to a single library, but they don't recompile the source member at the same time. I use DSPOBJD command & RTVMBRD to match the source change date & time. The result is I got about 5000 *PGM type with unmatch date or time. I found the same name source member in the source library. But I must verify the same name source member is the right version of the running object. Do you have other suggestion?  

Answer
The best I can suggest is that, for any given program, assume that the source with the most recent change date is the current source. I realize that this is not an absolute way to know which is the correct source version - it only points you to the likely source member.

- Laird