Perhaps I should ask the question a little differently. Due to constraints within the customer's environment, we have been asked to 'narrow' and 'control' and 'audit' the access available via the various interfaces to uniVerse, but not disallow them. If we do this at the server end, then we have the best chance. I have experience writing 'services' that can be called by the Unix rpc mechanism, and believe (hope?) it may be a similar task to write one for the UniRPC daemon. Has anyone tackled this before? or know of a techo-resource that explains the interface? I've found two uV guides that say 'it can be done', but offer no further info.
Michael McRae Magma Computing Solutions P/L email: [EMAIL PROTECTED] phone: +61 414 873 090 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
