Re: duplicate key error in identity column

[Dan <dan27649@xxxxxxxxx>]

Luis,

Not too long ago, Chuck Pence pointed out that v7r2 has an enhancement to
the timestamp that allows 12 digits to be defined for the "microsecond" and
that IBM documentation seems to indicate that can be used as a unique value
across the entire system.

http://archive.midrange.com/midrange-l/201504/msg00525.html

- Dan

On Wed, Jul 15, 2015 at 1:58 PM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:

> Dale,
>
> Personally, I would advise against using a timestamp as a unique key field.
> If either the program and/or the box is fast enough a timestamp can be
> duplicated across consecutive records.
>
> Regards,
>
> Luis
>
> Luis Rodriguez
> IBM Certified Systems Expert — eServer i5 iSeries
> --
>
> On Wed, Jul 15, 2015 at 1:20 PM, Dale Janus <dalejanus@xxxxxxxxxxxxxxxxx>
> wrote:
>
> > Everyone,
> >
> > The logical file with the two fields omitted makes the most sense.
> >  But I am trying to create a timestamp based on data in the original
> file.
> > In an incredible stroke of far-sightedness for something created over 20
> > years ago, the original file had an 8 digit date and 6 digit time.  I
> want
> > to carry those over as a time stamp.  ILE RGP is pretty handy to convert
> my
> > digits into time and date, and then just add  them together to create the
> > time stamp.
> > So I will create a logical with just the id omitted, let the program
> > create the time stamp and see how far I get.
> >
> > Thanks for the suggestions.  I'll report back what works.
> > ---Dale