OK, you guys have piqued my interest.  What are UUID's and how/why are they

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------------- Original Message --------------------------
Thank's to all who helped with GENUUID(). It's working great!


With respect to the latency warning, are you referring to potential
performance bottlenecks, or a risk of duplicate ID's?

Your warning did get me thinking, so I decided to run a crude little test. I
created a PF with a single field to store the UUID value, and no primary
key. I then created a program that called GENUUID() and wrote a PF record
with the result, for 5000 iterations. The program was submitted to three
different subsystems (jobs held) and all three were released within a second
of each other. It took about 8 seconds for all jobs to complete. Finally, I
did an ADDPFC TYPE(*PRIKEY) in order to test for uniqueness. Everything
worked just fine.

Do you think my test was too simplistic?

John Taylor

----- Original Message -----
From: "Richard Jackson" <richardjackson@richardjackson.net>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, November 10, 2000 07:04
Subject: RE: UUID's

> beware of latency - you may need them very quickly.
> Richard Jackson
> Richard Jackson and Associates Ltd.
> IBM Business Partner
> mailto:richardjackson@richardjackson.net
> http://www.richardjacksonltd.com
> Telephone: 1 (303) 808-8058
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].