Cisco Support Tools 1.0 User Guide How to Use the Processes Utility from a Command Line 128
Command Line Options
Command: Description: Example:
cmdhelp, chelp Displays a list of commands specific to this
utility.
Note: Using Help or ? also displays this list, but
includes several additional ICM commands (e.g.,
echo, error_stop) not used by this utility.
>cmdhelp
/? Displays syntax for a specified command. ><command> /?
appserver Specifies the system on which the utility should
run. If not specified, the utility is run on the local
system.
><app_servername>
/<options>
system Specifies the target system the utility should run
against. If not specified, the utility is run against
the local system.
> /system <host_name>
/<options>
localhost Sets the network address of name of the target
node agent to the local host.
Note: By default, unless a different system is
specified (using the system command) the local
host is assumed to be the target system.
>localhost
list Displays information on all processes on the
target system.
For each running process, this command
displays:
y Process Name: The process's name.
y PID: The process's process ID.
y Type: Critical, Known, or Unknown, as
defined in the target system's
processinfo.xml file.
Optionally, you can include an argument to dump
this output to a local file. Output is stored as
XML-formatted text.
>list
OR
>list <localfile_path\filename>
kill Terminates a started process on the target
system. >stop <pid> <process_name>
save Saves the latest list command results to a
processes file in the application server's
Repository.
Saved output is stored as XML-formatted text.
If no file name is specified, output is saved to a
file named: ProcessesList <host_name>
<timestamp>.xml.
If desired, you can include an argument that
specifies a file name.
>save
OR
>save <filename>
files Displays t he list of processes files in the
application server's Repository. >files