Re: CCSID - change from 65535 to 37...issues? stories?

On Thu, Sep 18, 2014 at 5:11 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 9/18/2014 3:54 PM, John Yeung wrote:

Well, if you're using PDM, and don't have any version control
software, that date *is* pretty handy.

It would be handy if it could be trusted. After a machine upgrade that
required a save on the old machine and a restore on the new one, the
'last changed' dates for every filt and member were set to the date of
the restore.

Of course it's not 100% trustworthy, but no date of any kind is.
There are all kinds of ways that dates can be unhelpfully updated, or
even downright forged.

But a date doesn't have to be 100% trustworthy to have value. The
fact is, under normal circumstances, the member change date is a
convenient and reliable *enough* source of information that for
PDM/SEU users, it is unequivocally handy.

Whenever some momentous event (like a system migration or an errant
CHGSRCPF) destroys that data, a lot of value is wiped out. But then
from that point on, the value starts to build up again, until the next
event, when the cycle begins anew. It's like waterfront property
after a hurricane.

John Y.