On the RPGLE program not having source information, I’ve worked with 2 CM packages that IF CRTBNDRPG was used to create the program they updated the program object description with the modules source information post compile. So even if someone used a binding directory to bind multiple modules in CRTBNDRPG the program had the named modules source information.
On rare occasion this can cause confusion when another module is updated, the program recreated to bind in the updated module via BNDDIR and the source info is unchanged as the named module is unchanged.

One of these packages also had the option to reset the create date post CRTDUPOBJ to match the date on the source system so everything would line up if you compared them.

They both had commands that could update just about ANY object description field and I bet there’s others out there, maybe from TAATOOLS and the like.
Be pretty easy to write a CL that called CRTDUPOBJ then used the API or a command to set the create date in the target to match the source object.

***This e-mail and its attached documents are confidential and intended solely for the use of the addressee(s). ARCAD Software can in no way be held responsible for any damage resulting from an incident involving security, integrity, virus or transmission delay. As the integrity of this message cannot be guaranteed on Internet, the ARCAD Software company cannot be held responsible for its contents. Any unauthorized use or dissemination is prohibited.***

This mailing list archive is Copyright 1997-2016 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact