Re: TimeStamp Problem

_MATMATR1 returns a big int whith the time up to the microsecond in the
first 52 bits and an unique value in the last 12 bits.

/*-------------------------------------------------------------
/* Materialize Machine Attributes - Prototype for _MATMATR1
/*-------------------------------------------------------------
D matmatr pr extproc('_MATMATR1')
D MMTR_Template like(Machine_Attr)
D cAttribute like(Machine_Clock)


On 04/17/2015 02:21 PM, John Yeung wrote:

On Fri, Apr 17, 2015 at 12:39 PM, Dan <dan27649@xxxxxxxxx> wrote:

Also, because when you absolutely, positively must have a unique key but
can't rely on a timestamp (even with 12 digit precision for the second!) to
provide it, what was the impetus to increase the precision? Curious
mind(s?) wants to know.

There are a few classes of impetus:

1. You need to know what happened before or after something else.
Even if you can't eliminate ambiguity, you'd like to reduce it as much
as you can.

2. You need to know how long something takes.

3. The question shouldn't be "why?" but rather, "why not?".

Note that all of these are subject to the seemingly inexorable march
of technology. There was a time when it didn't make sense to have
nanosecond precision. We didn't have any devices or applications
which could have made use of it. Today, nanoseconds matter in a
number of fields.

John Y.

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --