Comments on: Time Stamp Issues http://itknowledgeexchange.techtarget.com/itanswers/time-stamp-issues/ Wed, 19 Jun 2013 13:10:49 +0000 hourly 1 By: jeffjag http://itknowledgeexchange.techtarget.com/itanswers/time-stamp-issues/#comment-38197 jeffjag Thu, 29 Dec 2005 08:57:47 +0000 #comment-38197 The “Change date/time” on the object description (DSPOBJD)is the timestamp for any change to the object. If you do a CPYF to a new file or a CRTDUPOBJ to a new file, it will result in the current date and time for the new object.

When you change the text of a file, the object timestamp changes, but the member timestamp will not (DSPFD *MBRLIST). The member timestamp changes when the member changes.

For a source file (CRTSRCPF), each record has a date stamp in a field named SRCDAT. When a source file is copied, the default is to retain the record date stamps. This can be changed using the CPYF or CPYSRCF and specifying values in the SRCOPT and SRCSEQ keywords.

If you know how to program in MI (the OS/400 “assembly language”), you can probably change the date and time of the object to any value, but there is no OS/400 command to do that.

]]>