| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 433.1 | f$getjpi() | VAXUUM::DYER | Adventures in Success | Fri Mar 27 1987 16:38 | 3 |
| Use f$getjpi(); f$getjpi(0,"pid") is your current PID. You can then use that
PID to get other information with f$getjpi().
<_Jym_>
|
| 433.2 | just use "" in lieu of pid | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Fri Mar 27 1987 19:05 | 6 |
| If you're only interrogating your own job, there's no need to get your
pid first. Just do this:
f$getjpi ("","whatever-item-you-want")
/Eric
|
| 433.3 | 0 or "" - Same Difference | VAXUUM::DYER | Adventures in Success | Mon Mar 30 1987 13:12 | 0 |
| 433.4 | you missed my point | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Mon Mar 30 1987 20:03 | 10 |
| You missed my point.
I was pointing out that .1's suggestion about getting your own
pid and THEN using it to get other info is not necessary.
You can get the other info directly.
I wasn't talking about 0 vs. "".
/Eric
|
| 433.5 | need more info...then maybe... | LASSEN::GERMANO | | Mon Mar 30 1987 21:43 | 5 |
| I think I have some ideas (& hacks) for you but not sure what
your end goal is. Do you have the users cooperation or do you
want to do this surreptitiously or as a manager? Are the users
remote logins, locals, or a mixed bag?
John
|
| 433.6 | Maybe Process name good enough? | DLO05::BEATTIE | Bliss is NOT ignorance (is it?) | Thu Apr 02 1987 16:09 | 16 |
| If I understand the question in .0, I believe that your own suggestion
of using the process name will be good enough. VAX VMS guarantees
that on a given VMS system, and within the SAME group, the process
name for each process must be unique.
Since all users are using the same captive account, they all have
the same UIC, and are therefore all in the same group, and must
therefore all have unique process names [intended as a rhetorical
question] ??
Of course, in order for you to specify a process by name [for process
control funtions, for instance], your process must also be in the
same group...
Hope this helps.
-- Brian
|
| 433.7 | | TLE::BRETT | | Thu Apr 02 1987 20:01 | 10 |
| Last time I checked VAX VMS made no such guarantee!
The simplest way to get two processes in the same group
with the same name is
$ SET UIC [some other group]
$ SET PROCESS/NAME="Same name"
$ SET UIC [same group]
/Bevin
|
| 433.8 | I don't think that ? was rhetorical | IDLEWD::LENZMEIER | Chuck, DECwest Engineering | Fri Apr 03 1987 01:18 | 10 |
| Re: .6, .7
.7 is correct that it is possible to have two processes in the
same group with the same name.
However, if all of the processes in question are running under
the same captive account, and the captive procedure doesn't allow
the user to change the process's UIC (we can only hope that the
account doesn't have CMEXEC or CMKRNL!), then none of the processes
will have the same name.
|
| 433.9 | you can get dup. names even WITHOUT set uic | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Fri Apr 03 1987 13:22 | 8 |
| No, you are *not* guaranteed unique process names.
You don't even need SET UIC privileges to create multiple names.
My favorite method is with SET HOST. I've described how to do this
in other notes and will repeat if needed.
/Eric
|
| 433.10 | Users Can Get Quite Cute | CLOSET::DYER | I Park at Mrs. Nelson's Candy House | Tue Apr 07 1987 19:38 | 2 |
| Also bear in mind that users can change process names, but not PIDs.
<_Jym_>
|