Re: Version numbering on programs

I suppose a nightly batch job that does a DSPOBJD on all systems.  Then a 
central job compares create dates on *PGM, *SRVPGM objects might work. 
Careful with change dates on imbedded SQL.  Seems to like to save the 
access path right there in the *PGM thus affecting change dates.  Even 
been know to throw a little confusion to the change management vendors. 
"This object has been changed outside of (your change management package 
here)" type messages.

Rob Berendt