Pathway/XM System Management Manual

Managing Clients and Requesters
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
8-9
Displaying Status Information
The STATUS TCP Command
The STATUS TCP command displays status for a single TCP, multiple TCPs, or all
TCPs defined in a PATHMON environment.
The following example displays status for all TCPs in the Pathway/XM environment:
>> STATUS TCP *
You can also include state information (running, stopped, or suspended) in your
command. The STATE option is very useful for problem detection and management.
For example, the following command displays status only for those TCPs that are
stopped:
>> STATUS TCP *, STATE STOPPED
For each TCP, you can also view the status of the terminals the TCP controls by
including the DETAIL option in your command. For example, the following command
displays status information for the TCP associated with the terminal TERM1 and for all
terminals under the control of that TCP:
>> STATUS TCP TERM-1, DETAIL
For the syntax of the STATUS TCP command, refer to STATUS TCP on page 11-85.
The STATUS TERM Command
The STATUS TERM command displays status for a single TERM object, multiple
TERM objects, or all TERM objects in the Pathway/XM environment.
The following example displays status for the TERM objects in the terminal group
ABC:
>> STATUS TERM GROUP ABC
For each TERM object, you can also view the status of the program unit currently
executing on a TERM object by including the DETAIL option in your command. For
example, the following command displays status information for TERM TFRONT1 and
the program unit running on TFRONT1:
>> STATUS TERM TFRONT1, DETAIL
You can also include terminal state information (running, stopped, suspended) in your
command. For example, the following command displays status only for those TERM
objects that are not running:
>> STATUS TERM *, STATE NOT RUNNING
Occasionally, you might issue a STATUS TERM command for a TERM object that has
been stopped by the TCP. If your STATUS TERM command executes during the brief
interval before the PATHMON process is notified that the TERM object is stopped, you
may receive an error 3202, “TERMINAL IDENTIFIER NOT KNOWN TO TCP.”
If you encounter this error, try the command again in a few seconds.
For the syntax of the STATUS TERM command, refer to STATUS TERM
on
page 11-89.