At 09:20 -0700 on 06/07/2013, Ed Jaffe wrote about Re: Age of
datasets in hours, not days?:
As a software developer, I have had multiple occasions to process
event times stored as all or part of a TOD value. For obvious
reasons, end users prefer everything displayed to them in local
time. Therefore, accurate reporting of these events in
human-readable form requires knowledge of the locale's time zone
policy going back many years (for (E)JES, we go back 10 years). For
this reason, I have come to very much appreciate event times stored
as local time. For example, ISPF stores member create/update time as
a local time value. No conversion necessary.
OTOH: It can cause a dataset that is shown has having been
created/updated at 2:30 to actually be an older version of the same
dataset in another directory which is shown as having been
created/updated at 2:15 (ie: 45 minutes later due to the 1 hour
rollback).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
