RE: V5R2: Source now allowed in the IFS

Steve

And I'm inclined to think it's some key to an internal index, which
contains the full path info. But this is a UNIX concept in the first place,
anyway, AFAIK. What does it mean in that realm? AFAIK, the st_ino and
st_dev together comprise the right-hand 8 bytes of the file ID reported in
opt 8 of WRKLNK. That file ID also always has, on our system, what looks
like an 8-byte integer = 1. I wonder if it's the ASP - does anyone know?

Besides, hashes are not guaranteed to be unique. There IS a GENGUID MI
instruction, that is also surfaced for use in HLLs.

Vern

At 10:37 PM 10/21/02 -0400, you wrote:

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Tom Liotta
Sent: Monday, October 21, 2002 10:06 PM

>With no better info than a guess, we might as well call it a "Hash Number
>representation of the path name". It is apparently persistent with the life
of
>the object. The 16-byte value can be used as input to the
Qp0lGetPathFromFileID
>API to return the fully-qualified path of the object. Additional fields
both
>before and after this one (Object File ID) in the audit journal entry
formats can
>be used for additional supporting info.

might be a GUID.  that is a 16 byte value that is unique across space, time,
... the world.

If so, I would like to know if the system has the facility to store a guid
identified variable length string.

Steve