NAME

cstm − Command line interface to the Support Tool Manager

SYNOPSIS

/usr/diag/bin/cstm [-m] [-l log_file ]

DESCRIPTION

cstm is a command-line user interface program for accessing a variety of support actions provided by the Support Tool Manager.  cstm is a complementary interface to xstm (a graphical interface for the X11 environment) and MSTM (a menu-based interface for any HP 2392 terminal (or compatible) or on any X terminal).  cstm can be run on an HP compatible ASCII terminal or on any X terminal. 

When cstm is started, a banner is displayed; followed by a prompt.  The "map" command may be used to generate a map of the I/O and system configuration which includes processors, I/O cards, and peripherals.  The map includes the physical path of each device, a brief description of each device, and the status of all support operations that have been initiated on each device. 

Note that when cstm is run for the first time, executing the initialization phase takes longer than when it is run again.  In this sense, the initial execution of cstm is the equivalent of using the -m option (discussed below). 

A help command is provided, which displays either a brief list of commands provided by cstm, or more detailed information on a particular command.  To obtain the command list, type help or ?.  Help information for a particular command can be obtained by following the help command with the name of the command for which help is desired. 

Operations that can be performed on a specific device depend on the support tool functions available for the type of device.  Typically these actions are verify and diagnose or exercise.  verify operations consist of tasks that access the device in a way that a typical user would, to determine if the device is functional.  diagnose operations perform hardware diagnostic tests on the selected device.  exercise operations attempt to stress the device. 

Support operations for a given device are initiated by typing the appropriate command followed by the physical path of the device as shown on the output from the map command.  For example, verify 2/0/1 results in a verifier being run on device 2/0/1.  Many commands accept parameters such as loop, time, all, etc.  The exact syntax, including allowable parameters for a given command, can be determined using the help command. 

When an operation such as diagnose, exercise, or verify is selected, a message is displayed indicating that the operation was initiated.  If a map command is issued prior to the completion of the operation, the corresponding status for the selected device is shown as Running, indicating that a test is in progress.  When the action has completed, a message is displayed indicating the result of the operation.  Additionally, the status in the map is changed to reflect the result.  Typical result statuses are Success, Failed, and Warning.  In the case of Warning and Failed, the result is displayed in inverse video for easier recognition.  If an operation fails, detailed information concerning the exact nature of the failure can be obtained by issuing the viewlog command for the device.  This action creates a vi editing session on the failure-log file. 

Some actions may require assistance from the user, such as mounting a tape and making sure that the tape drive is on line.  When such operator intervention is required, a prompt is displayed to which the user must enter a response. 

Options

cstm recognizes the following options and command-line arguments:

-m At start-up, force a search of the physical devices on the system and of the diagnostic programs supported.  When this option is used, cstm takes longer to initialize to the point where user interaction begins.  This option is required when system configuration is changed or when a new diagnostic program is installed using sysdiag. 

-l log_file Specifies the name of the file to which log events that occur during the time the application is active are posted.  The default is ./stm.log.  To review the contents of this log, use the viewlog command with no parameters. 

WARNINGS

Due to the nature of this application and its associated processes, overall system performance may be degraded while CSTE is running. 

AUTHOR

cstm was developed by HP. 

FILES

Session Log File

The session log (default name stm.log) contains a detailed history of the actions performed by cstm.  This log begins with a chart indicating the system and I/O configuration for the system and records the results for each action performed during the session.  Each line of the chart specifies the location of the device, a description of the device, the current status of the diagnose action, and the current status of the verify action. 

Note that the Diagnostic, Verifier, and Exerciser status columns will contain entries of N/A, Untested, or Incompl..  N/A signifies that the corresponding action is not available for the device.  Untested signifies that the action has not been invoked; always the case when cstm is first invoked.  Incompl.  signifies that an action was attempted, but was unable to complete. 

Other Files

/usr/diag/bin/am support application manager

/usr/diag/bin/dtm diagnostic tool manager

/usr/diag/bin/DTMDUI.sh diagnostic interface shell

/usr/diag/bin/cpudaf cpu access function

/usr/diag/bin/diskdaf disk device function

/usr/diag/bin/fpudaf floating point access function

/usr/diag/bin/graphicsdaf graphics device access verifier

/usr/diag/bin/idiskdaf removable-media disk device access function

/usr/diag/bin/memdaf memory access function

/usr/diag/bin/tapedaf tape device access function

/usr/diag/bin/CSVER000 NLS message catalog for the platform

/usr/diag/bin/CCSTM000 NLS message catalog for CSTM

SEE ALSO

mstm(1M), sysdiag(1M), xstm(1M). 

Hewlett-Packard Company  —  HP-UX Release 9.0: August 1992