NET/MASTER Management Services (MS) Operator's Guide

How the Guardian User ID of External Processes is Determined
Accessing External Utilities and Applications
7–18 106379 Tandem Computers Incorporated
You realize that the wrong file is being loaded and issue a KILL command to terminate
the FUP1 session immediately and stop the FUP process (if you are in the Command
Entry facility, press SF14 to issue the command):
OPSYS KILL FUP1
To force all utility processes associated with your current environment to be stopped,
enter the following (if you are in the Command Entry facility, you must either prefix
the command with a slash (/) or enter spaces in the UTILITY field):
OPSYS CLEANUP STOP
The STOP command stops the utility processes. If you only want to terminate your
sessions with the utilities, but not to stop the utility processes, use the DOWN
operand.
How the Guardian User ID
of External Processes Is
Determined
When you create a process using the OPSYS SEND or the PROGRUN command, the
process is assigned a GUID. The PARAM SWGUID setting on your NonStop
NET/MASTER MS system determines how the GUID of any process you create by
using OPSYS or PROGRUN is determined (see Figure 7-2).
If PARAM SWGUID=YES (the default), then the process is allocated the current
GUID of the user creating the process.
If PARAM SWGUID=NO, the process is allocated the GUID of NonStop
NET/MASTER MS (this is the GUID of the person who started NonStop
NET/MASTER MS).
Figure 7-2. How the Guardian User ID of External Processes is Determined
010
NO
Current
Guardian
User ID
OPSYS /
PROGRUN
YES
PARAM
SWGUID
NNM
Guardian
User ID
NNM (NonStop NET/MASTER MS)