Just my opinion: setting Changed date based on a read where no data or attribute
other than the object Accessed date is, at least, misleading. Hence my comment
that iSeries leaving Changed >unchanged< when a file is opened/closed with no
data or name change seems more logical and correct.

All of this by my assumption, from reading, that other systems may update
Changed date on access alone.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, May 29, 2014 10:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: IFS file Created, Accessed and Changed info

On Thu, May 29, 2014 at 12:36 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:
There's a system call named "stat" on both Unix and Windows, that
retrieves three times. "Access" time and "content modification"
time have the same meaning on both systems,

That's interesting to me because it's a significant difference between
what I see on iSeries where "Access" time and "content modification"/
"Changed" time values seem to be handled in a more logical or "correct"
way ?

I don't know what you mean by more logical or correct. Well, first of all, I don't know what iSeries behavior you're referring to. I mean, how is it handling the timestamps, and what about that handling is
*different* (never mind more logical or correct) than Unix or Windows handling?

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.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page