Hi, Jerry:

If your company is not using some kind of "change management" product or an open source version control tool (like CVS or SVN, etc.), then at least you could do something like this...

*Best practices* suggest to include a "change log" of comments in the block of comments at the beginning of the source member, such as:

* Change Activity Log:
* mm/dd/yy who description
* --/--/-- --- -----------------------------------------------------------------
* 01/23/92 eca original (requirement #922)
* 07/21/93 jfm fix problem with date handling (problem #1527)
* 04/03/98 rec prevent overflow on totals (issue #1483)

It should not matter how much detail is included, but it is a good practice to add a "problem tracking number" to the description that ties back to your help-desk or problem tracking software (or BugZilla, etc.) if you use such a system, or the "originating document" number (e.g. when only a paper-based system is used to track requirements, problems, enhancement requests, etc.).

(It does not matter whether these comments are maintained in ascending or descending sequence by date, so long as they are in there.)

What is important is that your "shop standards" should require something like this, in the block of comments at the start of the source member.

Then, you could answer this question by just examining the source for that program.

Hope that helps,

Mark S. Waterbury

> On 3/16/2012 1:35 PM, Jerry C. Adams wrote:
My boss is asking me if there is any way to determine when a program was
originally created. DSPOBJD's creation date is the last date on which it
was compiled. It doesn't seem reasonable to me that the compiler/system
would keep track of the original date from the previous program object that
it was replacing, but thought I would ask.

Jerry C. Adams
IBM i Programmer/Analyst

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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 on our policy page. If you have questions about this, please contact [javascript protected email address].