|
Ken - Are you journalling these source files? (to see what happened) An authority change will update the member "change date". A change to the member text description will update member "change date". PDM scan will not update change date. Do you have software to chg indentation, comments, document begin/end statements, etc? jim ----- Original Message ----- From: "Graap, Ken" <keg@xxxxxxxxxxxxx> To: "'Midrange'" <midrange-l@xxxxxxxxxxxx> Cc: "Lairson, Kathleen A." <kal@xxxxxxxxxxxxx> Sent: Wednesday, July 09, 2003 7:11 PM Subject: Source changes ... > We are trying to put together a process for listing when a source file > member was changed last... > > When we list member descriptions for a source file to a database file we see > all kinds of data including: > > MBFCCN Century created: 0=19xx, 1=20xx > MBFCDT Date created: year/month/day > MBFCTM Time created: hour/minute/second > > MBCCEN Member creation century: 0=19xx, 1=20xx > MBCDAT Member creation date: year/month/day > MBCTIM Member creation time: hour/minute/second > > MBCHGC Last change century: 0=19xx, 1=20xx > MBCHGD Last change date: year/month/day > MBCHGT Last change time: hour/minute/second > > MBUPDC Last source update century: 0=19xx, 1=20xx > MBUPDD Last source update date: year/month/day > MBUPDT Last source update time: hour/minute/secon > > The MBCDAT date seems to be reasonable as well as the MBUPDD date. However, > the MBCHGD date doesn't seem to make sense. What events could be causing > this field to be updated. We found some source files in our protected > production source file that had a MBCHGD with today's date! Even though the > MBUPDD date was something like 8/27/99 ... > > So my question for the group is, what events cause these date fields to get > updated, especially the MBCHGD field? > > Kenneth > -- > ******************************** > Kenneth E. Graap > IBM Certified Specialist > AS/400 Professional > System Administrator > NW Natural - Information Services > System Services > Phone 503 226 4211 X5537 > FAX 603 849 0591 > keg@xxxxxxxxxxxxx > ******************************** > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.