pstat_drive

Parameters specified on the command line serve to uniquely identify the PSTAT for the single OPUS process which you wish to control. Enough information should be provided so that a single PSTAT may be uniquely identified, otherwise the command will fail. NOTE: you must supply values which match the case of the PSTAT blackboard.

Usage: pstat_drive [-i pid] [-o process] [-s status] [-x start_time]
                   [-p path] [-n node] <susp|resu|init|halt> [--help]

The only required argument is the command itself (e.g. susp|resu|init|halt). All other arguments serve to uniquely indentify the PSTAT. Any PSTAT selection options omitted will be replaced with default search characters that will match all PSTATs.

Inputs

Command line parameters.

None.

Returned status value is: '0' on success, '1' on general failure.

-i

OPUS process id (the PID part of the PSTAT), e.g. 000001fc.

OPUS process name (the PROCESS part of the PSTAT), e.g. listhd.

OPUS process status (the PROC_STAT part of the PSTAT), e.g. idle.

OPUS process start-time (the START_TIME part of the PSTAT), e.g. 4151da2b.

OPUS process path (the PATH part of the PSTAT), e.g. g2f.

OPUS process node, or machine name (the NODE part of the PSTAT), e.g. tufnel.

The command with which to control (or "drive") the OPUS process (e.g. susp|resu|init|halt).

Prints out the usage statement.

Assuming there is one process running in OPUS, under the "quick" path, and the output of pstat_test is:

000064cb-pypoller_-idle___________.418be2f9-quick____-tufnel______________-____

% pstat_drive -p quick -o pypoller susp

will suspend the "pypoller" process running in the "quick" path. Note that since we have only one process running, the -p and -o arguments were actually unnecessary to uniquely specify the correct PSTAT.

To resume the process, we use:

% pstat_drive -p quick -o pypoller resu

and, finally, to terminate the process, we use:

% pstat_drive -p quick -o pypoller halt