On 1/22/07, Huegel, Thomas <[EMAIL PROTECTED]> wrote:
Then I had an idea this would be a lot easier if there was a z/VM directory entry called USERDATA that would be freeform and queryable ie Q UDATA. That way one could id a user any way he wanted to and use or not use the values.
So you think about a "thirdparty check" right? Anything that runs inside the user's virtual machine is subject to tampering if that has the check, so it should be the server check some "attributes" of that user. There's ACIGROUP that the server can query through a diagnose. And if you don't need that function, you could abuse the (spare) account codes in the directory. Rob
