|
The creating process is the process owner for the purposes of the
contents of the username -- specification of /UIC mungs just the
UIC field of the new process.
There is no guarantee of one-to-one mapping of UIC to username.
(We encourage it, but that's not always the way it works...)
Which means that there's no reliable way to use /UIC to get to
a specific username.)
(We go through the underlying "how do I get a job created under some
other username" discussion periodically.) From DCL, the easiest ways
include the use of SUBMIT/USER, and the use DECnet task-to-task, and
similar mechanisms.
With recent versions of OpenVMS, one can use a program that calls the
personna system services (present and documented in V6.2 and later,
the documentation is easiest to find in either the V7.1 system service
manuals or the V6.2 new features manual) and then a call to sys$creprc.
This is probably worth a QAR against the documentation, as it's a regular
source of confusion.
|
| re .*
Yeah, it's a pity that RUN doesn't flag these 99.9999% conflicting
qualifiers.
Before everyone jumps on me and says that this might break existing
command procedures - actually based on the frequency of occurrence of
this inquiry I would say that it *will* break command procedures - it
could be just an informational.
Basically /AUTHORIZE is incompatible with lots of qualifiers of
RUN. I would expect /DETACH, /PROCESS, /INPUT, /OUTPUT and /ERROR to
work. Some of the flags (/ACCOUNTING, /DUMP, /RESOURCE, /SERVICE,
/SWAPPING) may work. /AUTHORIZE requires that the image be LOGINOUT.
|