You can create a VOC entry to run from an execute within a transaction.
Put an 'H' code in att4 to allow it to be called during a
transaction...
SBTESTCT VOC UUIDGEN
UUIDGEN
0001 Verb to call aix uuid generator
0002 /etc/ncs/uuid_gen
0003 U
0004 CGHIM
-Original Message-
I need to
source code supplied in
http://www.ietf.org/rfc/rfc4122.txt. Not exactly a trivia task.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Boydell, Stuart
Sent: Thursday, February 14, 2008 3:50 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV
Jacques,
How unique do your UUID's need to be? Do you need them to conform to
the 32 hex digit format? If not, you could generate unique identifiers
based on the port number (@userno) and current date/time.
Alternatively, you could use GCI to integrate the uuidgen function into
the
PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, February 12, 2008 1:22:57 PM
Subject: Re: [U2] [UV] Named commons
Jacques,
How unique do your UUID's need to be? Do you need them to conform to
the 32 hex digit format? If not, you could generate unique identifiers
based on the port number
DIGEST creates an MD5 checksum, but it's binary and you need to convert
it to hex. See http://www-306.ibm.com/software/data/u2/pubs/library/ to
get the latest documentation.
rex
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
: Tuesday, February 12, 2008 1:48:40 PM
Subject: Re: [U2] [UV] Named commons
Jacques,
Here's an example of generating a uuid using the userno and time. Note
the line wrap on the RESULT = line:
EQU TD$UTCSECS LIT '(SYSTEM(99))' ; * seconds since 1970-01-01
EQU TD$MILLIS LIT '((SYSTEM(12) * 1000) R
Jacques,
Here's an example of generating a uuid using the userno and time. Note
the line wrap on the RESULT = line:
EQU TD$UTCSECS LIT '(SYSTEM(99))' ; * seconds since 1970-01-01
EQU TD$MILLIS LIT '((SYSTEM(12) * 1000) R%3)'
ERRCODE = DIGEST(MD5, @USERNO:TD$UTCSECS:TD$MILLIS, 1, RESULT)
A named common is visible from a session. If Bob is logged in on session 1
and Jane on session 2, Jane has no visibility to Bob's named common or vice
versa. Certainly when someone logs in you could put your GUID in a named
common and it'll be there until that person logs off. You'll still have
@listserver.u2ug.org
Subject: Re: [U2] [UV] Named commons
A named common is visible from a session. If Bob is logged in on
session 1
and Jane on session 2, Jane has no visibility to Bob's named common or
vice
versa. Certainly when someone logs in you could put your GUID in a
named
common and it'll
