Description: The current status of this process. The various possible values are described as follows:

inactive : This process is not currently executing any script. This is the default state after creating a row in the table. running: The process is currently executing a script, and that script is not currently blocked by any internal asynchronous activity. 'running' actually means that this process is capable of being scheduled and is in a 'ready to run' scheduling queue. suspended: The script being executed by this process is currently blocked waiting for the completion of some asynchronous activity. dying: The script that was being executed by this process has completed and is waiting to be tidied up. When the tidyup has been completed this process will either automatically be destroyed or will enter the 'inactive' state. paused: The script being executed has been manually stopped, generally for debug purposes. A script can enter this state either voluntarily be requesting the system to stop it (ie similar to a breakpoint) or can be paused by writing to the cmdExecOperation variable. searching: When a process is given a script to execute the engine must first find that script. The script is identified by name (spe cified in cmdExecMacroName). The agent must search all possible sources for the script, which may take some time. The MIB allows the script to be specified by any name and so some implementations may allow the name to identify a file on some remote file system, for example by using a URL. While the agent searches for the script the process enters the 'searching' state. If the agent locates the script it will enter the 'running' state. If the script cannot be located then the process re-enters the 'inactive' state.