...
grosch> tool to check new files in. In other words, any user can create the
grosch> file 'foo' as long as they create it by running program 'bar' to do
grosch> so.
The only way I've found to do that is to give the tool a userid ("tooluser");
compile the password into the tool, and give only "tooluser" write permission
to the directories in question.
Internally, the tool has to do a setpag (to avoid stepping on the user's
token) and then authenticate with it's stored password when it starts up.
Ugly, but ...
A more elegant alternative: use DCE. :)
Jim Rowan Distributed Computing Specialists DCE/DFS Consulting
[EMAIL PROTECTED] (512) 452-7403
