The Support Tools Manager (STM) allows you to run various support tools on one or more PA-RISC/IA64 machines. Support tools include information modules, verifiers, diagnostics, exercisers, firmware update tools, expert tools, and utilities.
After you start cstm, enter the command map to display a system map (device map) showing the devices configured on the Unit Under Test or UUT (for more information, see User Interface (UI) and Unit Under Test (UUT)).
Select devices by entering the select command. For example: select device 2 for device 2 in the system map, or select path 32.8.0 for the device at path 32.8.0.
Enter commands at the cstm prompt to perform operations on the selected devices. Typical operations are verifying devices and viewing Failure Logs.
The results of a running a tool are reflected by changes in the "Last Op Status" column of the device map:
You can run the cstm interface on one machine, and use it to run support tools on one or more remote machines (Units Under Test, or UUTs). Alternatively, you can run the cstm interface on one machine, and use it to run support tools on the same machine (i.e., the machine running cstm and the UUT are one and the same).
The cstm program is the command line interface for the Support Tools Manager (STM). There are also two other interfaces that run under STM:
On User Interface (UI) and Unit Under Test (UUT)
STM has been designed so that the support tools can be run on the local machine or on remote machines.
The computer running the user interface is the UI system, and the computer being tested is the Unit Under Test or UUT.
You can run the user interface and the support tools on the same machine. In this case, the UI machine and the UUT are one and the same.
You can also run the STM user interface on one machine, and from it, run support tools on one or more remote machines.
Troubleshooting STM
By default, the test system (Unit Under Test) is the same as the computer system running the user interface.
To select a remote system for testing, do the following:
You will see a dialog displayed, containing a list of test systems to choose from, the operating system (OS) they are running with their revision levels, and one of six statuses:
If you wish to delete a system from the list, type "delete", followed by its network name or index number in the "System to Test" list, and hit "Return".
NOTE: When a system is made the current test system, it is automatically connected to the User Interface (UI), if it is not already connected.
To connect to multiple systems:
A dialog similar to the one you saw for the "ConnectSys" command will be displayed; it is edited in exactly the same manner, with one major exception: you can only select one system to be "current" at one time, and therefore, multiple system selection is not allowed in this dialog.
NOTE: When a system is made the current test system, it is automatically connected to the User Interface (UI), if it is not already connected.
To disconnect from one or more systems:
You will see a dialog displayed, which is similar to those you have seen displayed for the "ConnectSys" and "SelCurrentSys" commands.
Most support tools do not require a support tool license. A few of the advanced tools (for example, expert tools) require a license from HP.
The following procedure tells you how to install and deinstall support tool licenses:
NOTE: If you selected "license", your permissions are only valid on the current test system.
If you selected "hplicense", your permissions are valid on all test systems accessible to the user interface, until the user interface is exited. Your permissions are only valid on the system running the user interface during the current test session.
To deinstall all licenses on the current test system (including any HP-Only licenses on the system), type DeinstallLic or "DLIC".
A dialog is displayed, cautioning you of the consequences of continuing with the deinstall process, and asking you if you wish to continue or cancel.
You can modify the behavior of tools by setting test options at the user interface. For example, you can set an option for all exercisers to loop continuously when they are run.
To select and set test options, do the following:
The "Verify Options" dialog is then displayed.
NOTE: WARNING: When you disable the "Allow User Queries" function, some tools will perform DESTRUCTIVE tests. This means that ALL DATA on unmounted disks WILL BE DESTROYED. The ability to disable this function is intended for manufacturing purposes only. It is highly recommended that you use the "Allow User Queries" function, and DO NOT DISABLE IT.
Before you can run a tool, you select the device or devices on which the tool is to be run. You can select a device in several different ways:
More advanced methods for selecting devices:
NOTE: If you typed "SelClass" ("SCL") or "UnselClass" ("USCL"), a dialog will be displayed, prompting you to enter the appropriate device class qualifiers, such as "Disk"; enter the information requested, and follow each response by hitting "Return".
To get information about a hardware device(s), run an information tool:
To quickly determine whether or not a selected hardware device(s) is usable (for example, on system bring-up or after adding a new device to your configuration), do the following:
Type Verify or "VER".
Type Map.
The map will be updated and displayed, which will inform you of the results of the verification procedure (e.g., "Success" or "Failure").
For more detailed information, View Device Status.
To determine whether or not a selected Field Replaceable Unit (FRU) is failing, run a diagnostic tool on the device:
The map will be updated and displayed, which will inform you of the results of the procedure (e.g., "Success" or "Failure").
For more detailed information, View Device Status.
To locate intermittent problems in a hardware device(s), run an exerciser on the device(s):
The map will be updated and displayed, which will inform you of the results of the procedure (e.g., "Success" or "Failure").
For more detailed information, View Device Status.
To update the firmware on a specific device, run a firmware update tool on the device:
NOTE: The firmware update process is device-specific. This means that while the user interface to the update process remains consistent, the specifics of the process for a given device may vary considerably. This procedure is an example only, using a SCSI disk. CAUTION: Be sure that you put the firmware file on the UUT (for example, with FTP), before starting the update process.
CAUTION: If absolutely necessary, you can interrupt or abort the firmware update process; however, it is not advisable.
To run non-device-specific support tools (utilities), do the following:
The "Run Utility" screen will be displayed, prompting you to select a utility from a list of all utilities for which you have licensing privileges.
The fastest way to determine the status of a device is to examine its status in the rightmost column of the system map.
For more information, you can view the Current Device Status:
A display will inform you of the results (e.g., "Success" or "Failure") for the most recently executed tool, and will recommend further action, as appropriate.
When a tool has detected a device failure, the icon for the device in the system map turns red and displays the word "FAILURE". To get a description of the failure, the suspected cause and recommended action(s), look at the failure log for the device:
The "Tool Failure Log" for the Exercise tool will be displayed.
When a tool is run on a device, it creates a log of its activity. This log may contain technical and low-level information.
The tool's Activity Log is useful when there are problems running a tool on a device. If a tool reports a device failure, you should first View the Failure Log. Only if that information is not sufficient do you need to look at the Activity Log.
Note that you can view logs for multiple selected devices.
To view a Tool's Activity Log:
The "Tool Activity Log" for the Exercise tool will be displayed.
After you have performed the procedure to Get Information on a Device, you can look at the information log created for the device:
The Information Log for the chosen device is displayed.
For more detailed information, View Device Status.
cstm allows you to view the following logs:
For more information on a particular type of log (e.g., the UI Activity Log), select its hyperlink (e.g., UI Activity Log).
Log contents are unique, but all of the logs displayable under cstm employ a similar log viewing dialog. Using this dialog you may:
The title of the log viewing dialog will specify the log type, as well as the tool or utility (and device, if necessary) whose log you have selected.
Note that multiple logs can be viewed at once; "Prev" and "Next" commands are provided to simplify navigation through these logs when viewing them.
The UI Activity Log contains a record of the errors encountered by the cstm user interface. The log dialog allows you to view, save, print, and clear the contents of the log, as desired.
There is only one copy of the log per machine, although multiple instances of the User Interface (UI) may be executed. Each log entry contains a label with a timestamp, user name, and the UI process id, in order to allow you to distinguish between these separate invocations of the UI. Here is an example of such a label:
Wed Dec 7 15:18:49 1994: User Name: joeuser, UI Process ID: 27697
To view the UI Activity Log, do the following:
The "UI Activity Log" screen is displayed.
The Map Log contains a record of what transpired while the system map was being built. The log dialog allows you to view, save, and print the contents of the log, as desired.
The log is created at boot time, and whenever the RemapSystem or "RS" command is executed.
To view the Map Log, do the following:
The "Map Log" screen is displayed.
The System Activity Log contains a record of system startup and shutdown events, events that occurred during operations, and tool start and completion information. The log dialog allows you to view, save, print , and clear the contents of the log, as desired.
To view the System Activity Log, do the following:
The "System Activity Log" screen is displayed.
The information provided by the Information Log is device-specific, but should at least include:
You should include the firmware revision, if it is available.
To view the Information Log, use the following procedure:
The Information Log for the chosen device is displayed.
The Information Tool Activity Log allows you to review details of the most recent execution of the Information support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Information Tool Activity Log for a particular device, do the following:
The "Tool Activity Log" for the Information tool will be displayed.
The Information Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Information support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Information Tool Failure Log for a particular device, do the following:
The "Tool Failure Log" for the Information tool will be displayed.
The Verify Tool Activity Log allows you to review details of the most recent execution of the Verify support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Verify Tool Activity Log for a particular device, do the following:
The "Tool Activity Log" for the Verify tool will be displayed.
The Verify Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Verify support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Verify Tool Failure Log for a particular device, do the following:
The "Tool Failure Log" for the Verify tool will be displayed.
The Diagnose Tool Activity Log allows you to review details of the most recent execution of the Diagnose support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Diagnose Tool Activity Log for a particular tool, do the following:
The "Tool Activity Log" for the Diagnose tool will be displayed.
The Diagnose Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Diagnose support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Diagnose Tool Failure Log for a particular tool, do the following:
The "Tool Failure Log" for the Diagnose tool will be displayed.
The Exercise Tool Activity Log allows you to review details of the most recent execution of the Exercise support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Exercise Tool Activity Log for a particular tool, do the following:
The "Tool Activity Log" for the Exercise tool will be displayed.
The Exercise Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Exercise support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Exercise Tool Failure Log for a particular tool, do the following:
The "Tool Failure Log" for the Exercise tool will be displayed.
The Firmware Update Tool Activity Log allows you to review details of the most recent execution of the Firmware Update support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Firmware Update Tool Activity Log for a particular tool, do the following:
The "Tool Activity Log" for the Firmware Update tool will be displayed.
The Firmware Update Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Firmware Update support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Firmware Update Tool Failure Log for a particular tool, do the following:
The "Tool Failure Log" for the Firmware Update tool will be displayed.
The Expert Tool Activity Log allows you to review details of the most recent execution of the Expert Tool support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Expert Tool Tool Activity Log for a particular tool, do the following:
The "Tool Activity Log" for the Expert Tool will be displayed.
The Expert Tool Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Expert Tool support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Expert Tool Tool Failure Log for a particular tool, do the following:
The "Tool Failure Log" for the Expert Tool will be displayed.
The Utility Tool Activity Log allows you to review details of the most recent execution of the Utility support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Utility Tool Activity Log for a particular tool, do the following:
The "Tool Activity Log" for the Utility tool will be displayed.
The Utility Tool Failure Log allows you to review details of failures encountered during the most recent execution of the Utility support tool against a specific device. The log dialog allows you to view, save, and print the contents of the log, as desired.
To view the Utility Tool Failure Log for a particular tool, do the following:
The "Tool Failure Log" for the Utility tool will be displayed.
Occasionally, you may have problems running the Support Tools Manager. While such problems will occur infrequently, if at all, the following are the situations you are most likely to encounter, with their proposed fixes:
If the kernel cannot bind in the appropriate drivers, or is unable to recognize the hardware, STM cannot communicate with the hardware in order to identify it.
For new hardware (if you have attached new hardware or powered up previously unpowered hardware):
For software problems, try the following:
For hardware problems, try the following:
Report STM defects through an HP representative. HP personnel should use the CHART defect-tracking program with the project name diag.stm.tools.hpux or diag.stm.ui.hpux.
Be sure to include the information from the Map Log and ioscan -kf commands.
The MapLog should indicate the cause of this problem, as well as what do about it.
You can determine if you have an old version of STM by checking the Release Notes at /usr/sbin/stm/Rel_NOTES.STM.
HP personnel can file an SR, use product number B4708AA and product name STM.
Be sure to include the information from the Map Log and ioscan -kf commands.
Consult the following for the information needed to determine the cause for an unavailable tool:
The message "Tool expected?" indicates that a particular tool should be available. Whether this is the case can be determined by checking the Release Notes (/usr/sbin/stm/Rel_NOTES.STM). It can also be ascertained during the process of installing a new tool.
Some tools (e.g., Expert Tools) require that you have a license to run them. If you do not have a license to run a particular tool, or if it is not installed, you will not see it listed as an available tool. In this instance, you should examine current device status (type "currdevstatus"); a listing of all licensed and non-licensed tools for a specific device will be displayed.
If necessary, install the license and try to run the tool again.
HP personnel can file an SR, use product number B4708AA and product name STM.
Note: Be sure to include the information from the SysActLog, prod_op_xref file, CurrDevStatus, and DisplayLic.
One indication that you have encountered this situation is that an invalid user name or password error will be displayed to you.
If "ping" works for the IP address, but not for the hostname, use the IP address.
When checking "uname -s" and "nslookup", ensure that the hostname portions match; for example,
"uname -s" returns "hprdstl6" "nslookup" returns "hprdstl6.rose.hp.com"
In the following instances, you must make the system independent of the network and the nameserver:
To do this, move the "/etc/resolv.conf" nameserver file, and create a local "/etc/hosts" file, which contains the local hostname and IP address. This will allow you to override the nameserver, permitting the system to run locally.
Consult the following (on the UUT) for the information needed to determine the cause of a failure to connect to the UUT:
When running STM locally on a system which had a problem performing a remote connect, errors may be displayed when STM attempts to perform a local connect: you may safely ignore these error messages.
You may have to restart "diagmond": you must be root in order to do so (STMStartup).
This is one of the more common problems you may encounter with the operation of the STM. Tools may move into and out of the "HUNG" state in the following instances:
If any of the above conditions is true, update the "diagmond" configuration so that it waits longer before marking a tool as "HUNG" (the default wait time is 4 minutes).
If a tool stays in the "HUNG" state, determine if there is an error by examining the activity log for the tool you are running (e.g., Verify Tool Activity Log) for errors, and/or to determine the last time the tool logged, compared to the current time. You may also want to examine the process, using the "ps -ef" command.
If the activity log for the tool you are running is actually hung, attempt to abort the tool. If the tool remains in the ABORT PENDING state indefinitely, kill the tool manually. To do so, logon to the UUT, find the tool that is executing, note its pid, and send it a KILL signal ("kill -9 tool_pid").
You may not be able to start tools, or perform initiation tasks, in the following instances:
In the first instance, the UIActLog will indicate a timeout when attempting to start the tool. In the second instance, the activity log for the tool you are trying to run will indicate a timeout when attempting to initialize.
In both of these instances, keep retrying, or wait for a time when the system is less busy and retry.
Also, some tools (e.g., Expert Tools) require that you have a license to run them. If you do not have a license to run a particular tool, or if it is not installed, you will not see it listed as an available tool. In this instance, you should examine current device status (type "currdevstatus"); a listing of all licensed and non-licensed tools for a specific device will be displayed.
If necessary, install the license and try to run the tool again.
The main window displays the system map, which provides configuration information, test status, and forward progress indicators, as appropriate.
It is also the starting point for accessing all other system functions and commands.
The easiest way to determine the last state of a device is by checking the "Last Op Status" field on the system map, and noting any text displayed.
The following is a list of possible statuses with their meanings:
Status Description ------ ----------- (blank) The device has not been tested Testing Testing is in progress QUERY PENDING Query waiting; click icon to respond SUSPENDED Suspended by the user HUNG The operation has hung ABORTED The operation was aborted WARNING The operation completed, with warnings in the Tool Activity Log INCOMPLETE The operation could not be completed FAILURE The most recent operation failed Success The most recent operation succeeded
For information on selecting a device, see Select Device(s).
Format: COMMAND_NAME (ACCELERATOR_NAME)
File: System: Device:
saveconfig (scfg) connectsys (cs) currdevstatus (cds)
restoreconfig (rcfg) selcurrentsys (scs) cleartoolstatus (cts)
recordcmdfile (rcf) disconnectsys (ds) select (sel)
stoprecordcmd (srcf) savemap (smap) selall (sall)
runcmdfile (rncf) printmap (pmap) slclass (sc)
recordoutput (ro) remapsystem (rs) seldev (sd)
stoprecordout (sro) maplog (ml) selprod (sp)
uiactlog (uial) displaylic (dl) seldevabove (sda)
readuutconfigfile (ruc) license (lic) seldevbelow (sdb)
updatetoolinfo (uti) hplicense (hlic) unselall (usal)
stmstartup (ssu) deinstalllic (dlic) uslclass (usc)
stmshutdown (ssd) sysactlog (sal) setfilter (sf)
resetsysactlog (rsa) daemonstartup (dsu) clearfilter (cf)
localmaplog (lml) daemonshutdown (dsd)
localsysactlog (lsal) daemonkill (dk) To save time, enter
syslog (sl) daemonactlog (dacl) the accelerator for
os (os) map (map) a command.
quit (q) example: "cstm> fal"
exit (ex) UPPER or lower case.
Tools: Tools (Continued) Options:
information (info) fwupdatefaillog (ffl) infooptions (iop)
infolog (il) fwupdateinfo (finf) veroptions (vop)
infoactlog (ial) experttool (xt) diagoptions (dop)
infofaillog (ifl) expactlog (xal) exeroptions (eop)
infoinfo (iinf) expfaillog (xfl) fwupdateoptions(fop)
verify (ver) expinfo (xinf) expoptions (xop)
veractlog (val) runutil (ru) utiloptions (uop)
verfaillog (vfl) utilactlog (ual) launchoptions (lop)
verinfo (vinf) utilfaillog (ufl) mapoptions (mop)
diagnose (dgn) utilinfo (uinf) generaloptions (gop)
diagactlog (dal) lateactlog (lal)
diagfaillog (dfl) latefaillog (lfl) Help:
diaginfo (dinf) aborttool (abt) help
exercise (exc) suspendtool (st) help more
exeractlog (eal) resumetool (ret) help syntax
exerfaillog (efl) abortutil (abu) help all
exerinfo (einf) displayquery(dq) help COMMAND (ACCEL)
firmwareupdate (fwu) attach (at) help help
fwupdateactlog (fal) wait (wait) version (vers)
killtool (klt)
killutil (klu)
FILE SaveConfig: Save current interface state as file commands RestoreConfig: Read/execute saved config commands from file RecordCmdFile: Enable/disable recording of commands to file StopRecordCmd: Disable recording of executed commands RunCmdFile: Read/execute sequence of cstm commands from file RecordOutput: Record commands/output to file in cstm format StopRecordOut: Disable recording of terminal output UIActLog: View log of errors encountered by cstm ReadUutConfigFile:Read config file on current test system UpdateToolInfo: Reread list of available tools for a device STMStartup: Turn off diagnostics on local machine STMShutdown: Restart diagnostics on local machine (root only) ResetSysActLog: Clear System Activity Log on current UUT LocalMapLog: View the Scan HW Log on local system LocalSysActLog: View the System Activity Log on local system Syslog: View log of system daemon information OS: Suspend STM and invoke an OS command shell Quit: To leave cstm (alias for "Exit") Exit: To leave cstm SYSTEM ConnectSys: Connect to test system chosen from list SelectCurrentSys: Select current test system from a list DisconnectSys: Disconnect from test system on list SaveMap: Write ASCII copy of device map to file PrintMap: Print ASCII copy of device map to printer RemapSystem: UUT re-examines configured hardware MapLog: Record of all system devices in last map DisplayLic: Display the currently installed license level License: Obtain required license level to run tools HPLicense: Obtain required license level to run HP-only tools DeinstallLic: Deinstall licenses on the current test system SysActLog: Record of all operations performed by cstm DaemonStartup: Initiate a daemon on the test machine DaemonShutdown: Abort a daemon on the test machine DaemonKill: Kill a daemon on the test machine DaemonActLog: View a daemon activity log Map: To explicitly request a map display DEVICE CurrDevStatus: Display device info/suggest further action ClearToolStatus: Reset map status for devices not under test Select: Choose a single device for testing SelClass: Choose several devices at the same time SelAll: Choose all devices in the hardware map Unselect: Deselect a single device UnselClass: Deselect several devices at the same time UnselAll: Deselect all devices in the hardware map TOOLS Information: Generate an info log for a selected device InfoLog: View log describing/identifying a device InfoActLog: View log of actions performed on a device InfoFailLog: View log of test failures on a device InfoInfo: View tool-specific help for a device Verify: Pass/fail test of hardware's usability VerActLog: View log of actions performed on a device VerFailLog: View log of test failures on a device VerInfo: View tool-specific help for a device Diagnose: Error isolation test to the FRU level DiagActLog: View log of actions performed on a device DiagFailLog: View log of test failures on a device DiagInfo: View tool-specific help for a device Exercise: Stress test of target hardware for intermittents ExerActLog: View log of actions performed on a device ExerFailLog: View log of test failures on a device ExerInfo: View tool-specific help for a device FirmwareUpdate: Update firmware on a selected device FWUpdateActLog: View log of actions performed on a device FWUpdateFailLog: View log of test failures on a device FWUpdateInfo: View tool-specific help for a device ExpertTool: Run device-specific interactive tool ExpActLog: View log of actions performed on a device ExpFailLog: View log of test failures on a device ExpInfo: View tool-specific help for a device RunUtil: Run non-device-specific cstm tools UtilActLog: View log of actions performed on a device UtilFailLog: View log of test failures on a device UtilInfo: View tool-specific help for a device AbortTool: Prematurely halt tool execution on a device SuspendTool: Pause execution of a tool on a device ResumeTool: Start running a suspended tool on a device AbortUtil: Prematurely halt utility executing on a device SuspendUtil: Pause execution of utility on a device ResumeUtil: Start running suspended utility on a device DisplayQuery: Display tool request for input/action Attach: Connect display to selected interactive tool Wait: Continue only after current operations complete OPTIONS InfoOptions: Configure information tool options VerOptions: Configure verification tool options DiagOptions: Configure diagnostic tool options ExerOptions: Configure exerciser tool options FWUpdateOptions: Configure firmware update options ExpOptions: Configure expert tools options UtilOptions: Configure utility options LaunchOptions: Enable/define test and debug options MapOptions: Configure device map options GeneralOptions: Configure general interface options HELP Help: Display summary of commands. Help more: Display description of all commands Help syntax: Display syntax for all commands Help all: Enter complete help system Help COMMAND (ACCEL): Display help on an individual command Help help: Display help on how to use online help Version: Display current interface version banner
The cstm comands are organized in six command categories, corresponding to the menus in xstm and mstm.
For a detailed listing of all the commands, their function, and syntax, see the On Command Syntax (Detailed).
The File Category includes seventeen commands:
Syntax: saveconfig | scfg [file {<file name>}]
Use this command to save the state of the user interface in a specified file. The following items will be saved:
See also RestoreConfig.
The information you enter here will be saved as a comment in the configuration file.
For example, you might enter something like the following: "This config tests the workstations in building R5".
You enter the path (i.e., directory) and filename of the configuration file to which you wish to save the current configuration.
Hit "Return" and the current configuration will be saved to that file.
Syntax: restoreconfig | rcfg [file {<file name>}]
Use this command to repaint the display map, using the configuration stored by the SaveConfig command. Before reading the configuration file, the interface restores the factory default configuration; this means that the user interface disconnects from all test systems.
You enter the path (i.e., directory) and filename of the configuration file from which you wish to restore a saved configuration.
Hit "Return" and the configuration will be restored from that file.
Syntax: recordcmdfile | rcf [description {<description string>}] [file {<full file path}]
By using this command, you can record the commands executed by the interface in a file you specify, or you can toggle recording off. cstm operations are recorded as a series of commands which can be read by:
A wait command is automatically inserted after each identify, verify, exercise, or diagnose operation, so that operations executed sequentially at the time of recording, won't attempt simultaneous execution at playback time. You may wish to edit the output file and remove some of these wait commands.
The information you enter here will be saved as a comment in the command file.
For example, you might enter something like the following: "This command file verifies the disks and tapes."
You enter the path (i.e., directory) and filename of the command file to which you wish to save the commands you are recording.
Hit "Return" and the commands being recorded will be saved to that file.
Syntax: stoprecordcmd | srcf
Use this command to disable recording of commands you are executing. The command is unavailable unless recording is in progress.
Syntax: runcmdfile | rncf [file {<full file path>}] [stop {yes|no}]
Use this command to have cstm read in and execute a sequence of commands saved by the RecordCmdFile command. Alternatively, any sequence of cstm commands can be read and executed by this command.
You enter the path (i.e., directory) and filename of the command file from which you wish to read in and execute commands.
Hit "Return" and the commands in the command file you have selected will be read in and executed.
If you no longer wish to run the currently executing command file, enter "Cancel".
Syntax: recordoutput | ro [description {<description string>}] [file {<full file path>}]
During any cstm session, you can use this command to save the terminal output commands generated by the session to a file of your choice. The output will show both the commands executed and the output they produced.
The information you enter here will be saved as a comment in the output file.
For example, you might enter something like the following: "This is the output of the disk verification."
You enter the path (i.e., directory) and filename of the file to which you wish to save the terminal output.
Hit "Return" and the terminal output will be saved to that file.
Syntax: stoprecordout | sro
You use this command to disable terminal output recording. The command is unavailable, unless recording is in progress.
Syntax: uiactlog | uial
Consult the UI Activity Log when you want to view a display of errors recorded by the user interface. You can view ("view" command) and save the contents of the log to a file ("saveas" command), print a hardcopy of the current log contents ("print" command), or clear the current log contents ("clear" command).
There is only one copy of the log on a single machine, even though more than one cstm session may be executed. Each log entry contains a label containing a timestamp, the user name, and the cstm process ID, in order to distinguish between separate cstm sessions on the same machine (for example, "Wed Dec 7 15:18:49 1994: User Name: bobcap, cstm Process ID: 27697").
The UI Activity Log is not temporary; all other cstm session files are removed, once the session is terminated.
If the log file reaches the configurable size threshold, a warning will be displayed to inform you.
If you select this command, you will clear the current UI Activity Log of its present contents.
Syntax: readuutconfigfile | ruc
Use this command to have the current test system "diagmond" daemon read its configuration file.
Syntax: updatetoolinfo | uti
Use this command to have the list of available tools for a selected device be reread. This provides the basic functionality for incorporating a newly installed support tool into cstm.
Syntax: stmstartup | ssu
Use this command to start the diagnostic system on the local machine, i.e., the machine on which cstm is running, when you are logged on as root.
Syntax: stmshutdown | ssd
Use this command to shut down the diagnostic system on the local machine, i.e., the machine on which cstm is running. You will see a warning/confirmation displayed, stating that the diagnostic system is being shut down and that it may only be restarted by the root user. If the local Unit Under Test (UUT) is connected, it will be disconnected before the diagnostic system is shut down.
Syntax: syslog | sl
Syslog is a system log, which is administered outside the Support Tools Manager by the "syslogd" daemon. It provides you with information logged by "syslogd" on behalf of the daemons running on the system (e.g., inetd, ftpd, etc.). The Support Tools Manager daemon is called "diagmond", and you will find its starting and completion messages logged in "syslog" (1 line entry for startup and 1 line entry for shutdown).
Syntax: resetsysactlog | rsa
Use this command to clear the System Activity Log on the current Unit Under Test (UUT).
See also LocalSysActLog.
Syntax: localmaplog | lml
Use this command to view the Map Log on the local Unit Under Test (UUT), without having to be connected to the cstm machine.
See also LocalSysActLog.
Syntax: localsysactlog | lsal
Use this command to view the System Activity Log on the local Unit Under Test (UUT), without having to be connected to the cstm machine.
See also LocalMapLog and ResetSysActLog.
Syntax: os | os
Use this command to suspend the Support Tools Manager user interface, and invoke an operating system command shell. You may then enter system commands at the shell prompt.
You type "exit" to return to cstm.
If you type an exclamation point in the first column of your input, the rest of the line will be passed to the operating shell for execution. Once this command terminates, cstm will resume execution.
Alias for "exit".
Syntax: quit | q
Use this command to leave the user interface, and return to the prompt from which you launched cstm. The connection to the Unit Under Test is shut down, and all interactive tool execution is terminated. Non-interactive tools will continue execution.
Syntax: exit | ex
Use this command to leave the user interface, and return to the prompt from which you launched cstm. The connection to the Unit Under Test is shut down, and all interactive tool execution is terminated. Non-interactive tools will continue execution.
The System Category includes twelve commands:
Syntax: connectsys | cs [system {<system name>}]
Use this command to maintain a list of test systems, and to connect to those chosen (selected systems are indicated by an asterisk in the first column). To select items, or to use the "delete" command, use either the system name or the index number to the left of the system name. To deselect items, precede the index number or the system name with "-".
The System information portion of the dialog contains the list of test systems available, and may be edited. When adding a test system, only the system name need be specified. The OS and OS Revision are automatically determined, to provide the necessary information prior to system connection.
Multiple systems may be selected, and are connected when the dialog is finished by entering "ok", followed by "Return"; "cancel" is used to abort the dialog. Another dialog is generated to prompt you for the logon name and password necessary to establish the connection. The same name and password are used to connect all the selected systems. An attempt to connect all the selected systems will be made; in case of an error, a list of systems not connected will be included in the error display.
The status of each test system is listed in its entry in the list of available test systems. The possible statuses and their meaning are as follows:
This dialog allows you to add systems to, or delete them from, the list of test systems maintained by the interface.
To add a system to the list of systems to test, type "add" followed by the network name of the system (e.g., "system5.cup.hp.com") in the "Enter Command" field; then hit "Return".
To delete a system from the list of systems to test, type in "delete", followed by the index number or the system name in the "System to Test" area of the screen display.
When "ok" is entered, a dialog box will be displayed, prompting you for your login and password on the system you chose to be connected to.
Syntax: selcurrentsys | scs [system {<system name>}]
Use this command to select which system will display the testing information for the current test system, which you choose from the list of connected test systems.
Only one test system can be selected by this command at a time; the list of test systems may be edited. When you choose a system to be the current test system, it is automatically connected to cstm, whenever possible, if it is not already connected.
When a new system becomes the current test system, all the displays are altered to reflect the status of this new system. However, the previous test system remains connected to cstm, and will continue to execute any currently active support tools.
If you exit cstm without making the previous system current again, then all interactive support tools running on that system are terminated, and the output from them is lost (non-interactive support tools will continue to execute). You will be warned that this is about to happen, and will be given the opportunity to cancel.
All connected systems are listed in the Status column of the list of systems available for testing.
If the connection to the current system fails, there will be no current system. You will be warned and the device map will be cleared.
This dialog box allows you to add systems to, or delete them from, the list of test systems maintained by the interface, and to select one system at a time to be the current test system.
To add a system to the list of systems to test, type "add", followed by the network name of the system (e.g., "system5.cup.hp.com") at the "Enter Command" prompt; then hit "Return".
To delete a system from the list of systems to test, type "delete", followed by the system's name or index number from the "System to Test" area of the screen display.
When "ok" is entered, a dialog box will be displayed, prompting you for your login and password on the system you chose to be the current test system.
Syntax: disconnectsys | ds [system {<system name>}]
Use this command to disconnect from systems you have chosen to be connected with; the list of test systems is not editable in this dialog.
Multiple systems may be selected, and are disconnected when "ok" is used to finish the dialog.
This dialog box allows you to disconnect from one or more systems at a time.
To disconnect from a system, type "delete", followed by the system name or index number from the "System to Test" area of the screen display; then type "ok".
Use "cancel" to abort the dialog.
If there are currently active interactive tools, you will be asked for confirmation before the system on which they are running is disconnected.
Syntax: savemap | smap [file {<full file path>}]
Use this command to write an ASCII copy of the device map to a specified file.
Save your configuration display information to a file by typing "savemap". You will be prompted for the name of the file to which you wish to save your configuration. Enter the name of the file and type "Return".
Syntax: printmap | pmap [printers {<printer name>}]
Use this command to print an ASCII copy of the device map to a specified printer. The list of available printers includes all those configured on the system on which cstm is being run.
To print out a hardcopy of the device map to a particular printer, select a printer from the list displayed in the "Printer" area of the screen display (selected printers are preceded by an asterisk) by typing its index number at the "Enter Selection: (lp)" prompt; then type "ok".
Syntax: remapsystem | rs
Use this command to determine what hardware is attached to the unit under test. This command is especially useful when you have attached new hardware to your system, or have powered up previously unpowered hardware. At the OS prompt, issue an ioscan command, so that the system will recognize the new hardware; then run the Remap System command in STM. Once the rescan is completed, the device map will be redisplayed. All devices are displayed and are unselected.
Whenever this command is executed, the MapLog is created.
Syntax: maplog | ml
Use this command to view a record of all the devices identified when the system map was last built. You can view, save, or print the log. The log is created at boot time, and whenever the RemapSystem command is executed.
The log displays the log creation time (e.g., "Fri Dec 9 13:27:31 1996"), followed by a list of log entries, describing events which occurred during the system map build. The individual log entries are preceded by the day, date, and time at which the logged event occurred. Log entries may contain information, error messages, tool status, etc.
See also RemapSystem.
Syntax: license | lic [password {<stm licence password>}]
Use this command to install the level of licensing you need to run support tools. The password you enter will determine the level of access the system grants you. All permissions granted you apply to the current test system only.
The password you type is not displayed on the screen.
See also HPLicense and DeinstallLic.
In order to determine the level of access granted you by the system on which you have installed your support tools license, you must enter a password at this time, and then enter "OK" to proceed. If you do not want to continue with the password installation, enter "Cancel" instead.
The password you type is not displayed on the screen.
Syntax: hplicense | hlic [password {<hp licence password>}]
Use this command to install the HP-Only license. HP-Only privileges will be enabled on all test systems accessed by cstm, until the user interface is exited. On the User Interface (UI) system, however, the HP-Only password is only enabled for the current session.
The password you type is not displayed.
See also License and DeinstallLic.
In order to enable HP-Only run privileges on all systems accessed by the STM until you exit the current login session, or to enable HP-Only run privileges on the user interface for the current session, you must enter a password at this time, and then enter "OK" to proceed. If you do not want to continue with this login session, enter "Cancel" instead.
The password you type is not displayed on the screen.
Syntax: deinstalllic | dlic
Use this command to deinstall licenses on the current test system. When executed, all licenses on the system will be deinstalled, including any active HP-Only licenses. Before the operation begins, however, a dialog will be displayed, which will ask you to confirm or cancel the operation.
See also License and HPLicense.
Syntax: sysactlog | sal
Consult the System Activity Log when you want to view a display of events which occurred during system startup and shutdown, as well as any events which occurred during operations ("view"); the log also contains tool start and completion information. There are also commands which allow you to save the current contents of the log to a file ("saveas"), print a hardcopy of the current log contents ("print"), or clear the current log contents ("clear").
The log displays host and user names, followed by log creation time (e.g., "Fri Dec 9 13:27:31 1996"). Each of the following log entries is preceded by a day, date, and timestamp of the same format. The log entries may include tool status messages, error messages, etc.
If you enter "ok", the current contents of the System Activity Log will be deleted. If you don't wish to delete the current contents of the System Activity Log, enter "cancel".
Syntax: map | map
Use this command to explicitly request a map display. You might want to run this command when you add a peripheral or other system device, to ensure that you are displaying the most current map of system devices.
Syntax: daemonstartup | dsu [daemon {<daemon name>}]
Use this command to initiate a daemon on the test machine. When invoked, a dialog appears listing all available STM daemons on the UUT (excluding diagmond).
Syntax: daemonshutdown | dsd [daemon {<daemon name>}]
Use this command to abort a daemon on the test machine. When invoked, a dialog appears listing all available STM daemons on the UUT (excluding diagmond).
Syntax: daemonkill | dk [daemon {<daemon name>}]
Use this command to kill a daemon on the test machine. When invoked, a dialog appears listing all available STM daemons on the UUT (excluding diagmond).
This command is allowed to complete only if the daemon has been issued an abort by the Daemonshutdown command, and has not terminated. If this command is run, and no running daemons have been issued an abort, an informational dialog will pop up, which will tell the user to run the "daemonshutdown" command. Otherwise, this command sends a "kill -9" command to the daemon process.
Syntax: daemonactlog | dacl [daemon {<daemon name>}]
Use this command to view a daemon activity log.
This dialog has a clear button.
The Device Category includes several commands:
Syntax: currdevstatus | cds
Use this command to display all known information for the selected devices, including current status, and to receive suggestions on further actions which you might take at this point. The data displayed for each device includes the following:
The "Current Device Status" may be run at any time, even if the device is currently busy, as it does not access the device to obtain its information.
When a utility is executing, the current status field also shows the process number for the utility.
The recommended action field is used to suggest what action you might want to take next. For example, in the event of a tool failure, you might see a message suggesting that you examine the InfoActLog and the InfoFailLog.
Syntax: cleartoolstatus | cts
Use this command to reset the state of all selected devices which do not have a currently running support tool process to "Untested". This command also removes the InfoActLog and the InfoFailLog for all devices.
Syntax: select | sel {[-] all | device {[-] all | <device num>|<device num> - <device num>}| path {[-] all | <path string>}}
Use this command to select a single device displayed in the hardware map.
Syntax: selall | sall
Use this command to select all the devices displayed in the hardware map.
Syntax: slclass | sc [device {<device type/device qualifier>}] [product {<product (qualifier)>}]
Use this function to select several devices at once, adding these to devices already selected. All devices to be chosen must satisfy one of the items specified in one of the two lists: "Devices" or "Products". Currently selected devices are not unselected by this function. If you wish to select only the devices which meet these criteria, use the UnselAll function prior to choosing the "Select Class" function.
"Devices" is defined as "Device Type/Device Qualifier." "Device Type" and "Device Qualifier" are displayed by the CurrDevStatus command.
Examples of "Devices" include:
Don't select anything if you do not want to use the device type and qualifier to select devices.
"Products" is defined as "Product (Qualifier)." "Product" and "Qualifier" are displayed in the device map and by the CurrDevStatus command.
Examples of "Products" include:
Don't select anything if you do not want to use the product to select devices.
Syntax: seldev | sd
This command will select all devices with the same device type and device qualifier as those devices which are already selected. The device type and device qualifier can be viewed using the CurrDevStatus command.
Syntax: selprod | sp
This command will select all devices which are the same product as those devices which are already selected.
Syntax: seldevabove | sda
This command will select all devices which are in the hardware path between the system processing unit and the selected devices. If, for example, a SCSI disk is selected, then using this command will also cause the SCSI interface card and any I/O or bus adapters to which this card is connected to also be selected.
Syntax: seldevbelow | sdb
This command will select all devices which are connected below the selected devices. If, for example, a SCSI interface card is selected, then using this command will also cause any SCSI devices connected to this card to be selected.
Syntax: selclass | scl [type {all | <device type>}] [qualifier {all | <device qualifier>}] [hwpath {<path name>}]
Use this command to select several devices at once, adding these to devices already selected. All devices to be chosen must satisfy three specified criteria: device type, qualifier type, and hardware path; currently selected devices are not unselected by this command. If you wish to select only the devices which meet these three criteria, use the UnselAll command prior to entering the "Select Class" command. This command is retained for compatibility reasons. The SlClass command is recommended instead of this command.
Examples of device types include:
Type "All" (or its index number) if you don't wish to limit the devices you are selecting by device type.
Examples of qualifier types include:
Type "All" (or its index number) if you don't wish to limit the devices you are selecting by qualifier type.
The final criteria for device selection is hardware path. You can select those devices which have a hardware path below a specified hardware path. This field should be blank, if you do not wish to limit the devices being selected by device path.
Scroll through the "Select only Device Type" screen display area to the device type you wish to select (e.g., "All" or a specific device type like "Channel Adapters") and enter its name or index number. Next, move to the "Select only Qualifier" screen display area, "Select only Devices below Hardware Path" screen display area, or enter "ok", as desired.
Scroll through the "Select only Qualifier" screen display area to the qualifier you wish to select, for the device type you chose in the "Select only Device Type" window (e.g., "All" or a specific qualifier like "CS80" or "FLEX"), and enter its name or index number. Next, move to the "Select only Devices below Hardware Path" screen display area, or enter "ok", as desired.
If you wish to select devices whose hardware path (device address) is below a hardware path of your choice, enter the hardware path information at this prompt. For example, if you wish to select all devices below the channel adapter at hardware path "4.2.3", enter "4.2.3" at the "Select only Devices below Hardware Path" prompt.
Once you've entered your hardware path information, enter "ok".
Use this command to deselect a single device on the hardware map.
Syntax: unselall | usal
Use this command to deselect all devices on the hardware map.
Syntax: uslclass | usc [device {<device type/device qualifier>}] [product {<product (qualifier)>}]
Use this function to deselect several devices at once, removing these from the set of devices already selected. All devices to be chosen must satisfy one of the items specified in the two lists: "Devices" or "Products". Currently selected devices which do not match the criteria in the dialog are not deselected by this function.
"Devices" is defined as "Device Type/Device Qualifier." "Device Type" and "Device Qualifier" are displayed by the CurrDevStatus command.
Examples of "Devices" include:
Don't select anything if you do not want to use the device type and qualifier to deselect devices.
"Products" is defined as "Product (Qualifier)." "Product" and "Qualifier" are displayed in the device map and by the CurrDevStatus command.
Examples of "Products" include:
Don't select anything if you do not want to use the product to deselect devices.
Syntax: unselclass | uscl [type {all | <device type>}] [qualifier {all | <device qualifier>}] [hwpath {<path name>}]
Use this command to deselect several devices at the same time, removing these from the number of already selected devices. You must specify three criteria for devices to be deselected: device type, qualifier type, and hardware path. Currently selected devices which do not meet all three criteria are not deselected by this command. This command is retained for compatibility reasons. The UslClass command is recommended instead of this command.
Examples of device types include:
Type "All" (or its index number) if you don't wish to limit the devices you are deselecting by device type.
Examples of qualifier types include:
Type "All" (or its index number) if you don't wish to limit the devices you are deselecting by qualifier type.
The final criteria for device selection is hardware path. You can select those devices which have a hardware path below a specified hardware path. This field should be blank, if you do not wish to limit the devices being deselected by hardware path.
Scroll through the "Unselect only Device Type" screen display area to the device type you wish to deselect (e.g., "All" or a specific device type like "Channel Adapters"), and enter its name or index number. Next, move to the "Unselect only Qualifier" screen display area, "Unselect only Devices below Hardware Path" screen display area, or enter "ok", as desired.
Scroll through the "Unselect only Qualifier" screen display area to the qualifier you wish to deselect, for the device type you chose in the "Unselect only Device Type" window (e.g., "All" or a specific qualifier like "CS80" or "FLEX"), and enter its name or index number. Next, move to the "Unselect only Devices below Hardware Path" screen display area, or enter "ok", as desired.
If you wish to deselect devices whose hardware path (device address) is below a hardware path of your choice, enter the hardware path information at this prompt. For example, if you wish to deselect all devices below the channel adapter at hardware path "4.2.3", enter "4.2.3" at the "Unselect only Devices below Hardware Path" prompt.
Once you've entered your hardware path information, enter "ok".
Syntax: setfilter | sf
The Set Filter command lets you limit the number of items which are displayed in the device map at a given time. To do so, first use the selection commands to select only the items that you wish to include in the device map. Then use the Set Filter command.
Syntax: clearfilter | cf
The Clear Filter command causes a device map filter previously set by the Set Filter command to be cleared. After issuing this command, all devices will be shown in the device map.
The Tools Category includes 38 commands:
Syntax: information | info
Use this command to create a log of information specific to each selected device, which has an information function, including:
Typically, the firmware revision code, if firmware is present in the device(s) selected, will also be displayed.
The information tool runs on all selected devices that are not currently busy.
When the tool exits, returning a "SUCCESSFUL" or "WARNING" status, you should consult the InfoLog, InfoFailLog, and/or InfoActLog for information retrieved by the tool about the hardware.
Syntax: infolog | il
Use this command to view the log(s) generated by an Information request on all selected devices for which an information log exists.
Syntax: infoactlog | ial
Use this command to review the log which contains details concerning the most recent invocation of an Information Tool on all selected devices. The command is valid only when a Tool Activity Log for an Information Tool exists for the selected device(s).
Syntax: infofaillog | ifl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of an Information Tool on all selected devices. The command is valid only when a Tool Failure Log for an Information Tool exists for the selected device(s).
Syntax: infoinfo | iinf
Use this command to display help information unique to the Information Tools for all selected devices. It may always be run, because it does not access the device(s) to obtain its information.
Syntax: verify | ver
Use this command to verify all selected devices for which a verifier command exists. The purpose of the verification procedure is to ensure as quickly as possible that the target hardware is usable, and that you will be successful in using the device. Verifiers don't tend to isolate down to the FRU level, nor are they generally interactive.
To verify a selected device or devices, the target device(s) must not only support verification, it must also currently be idle.
When you first start to verify a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, you must type DisplayQuery to display the query.
Once the verify operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the InfoFailLog for information on tool failures, and the InfoActLog for all other tool activity information.
Syntax: veractlog | val
Use this command to review the log which contains details concerning the most recent invocation of a Verify Tool on all selected devices. The command is valid when a Tool Activity Log for a Verify Tool exists for the selected device(s).
Syntax: verfaillog | vfl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of a Verify Tool on all selected devices. The command is valid when a Tool Failure Log for a Verify Tool exists for the selected device(s).
Syntax: verinfo | vinf
Use this command to display help information unique to the Verify Tools for all the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: diagnose | dgn
Use this command to diagnose all selected devices for which a diagnostic exists. The purpose of the diagnostic procedure is to test the target hardware as completely as possible, and if any errors are found, to isolate to the FRU level. Isolation to the component level is also provided, when possible. Diagnostic modules are not generally interactive.
To diagnose a selected device or devices, the target device(s) must not only support diagnostics, it must also currently be idle.
When you first start to diagnose a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, you must type DisplayQuery to display the query.
Once the diagnose operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the DiagFailLog for information on tool failures, and the DiagActLog for all other tool activity information.
Syntax: diagactlog | dal
Use this command to review the log which contains details concerning the most recent invocation of a Diagnose Tool on all selected devices. The command is valid when a Tool Activity Log for a Diagnose Tool exists for the selected device(s).
Syntax: diagfaillog | dfl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of a Diagnose Tool on all selected devices. The command is valid when a Tool Failure Log for a Diagnose Tool exists for the selected device(s).
Syntax: diaginfo | dinf
Use this command to display help information unique to the Diagnose Tools for the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: exercise | exc
Use this command to exercise all selected devices for which an exerciser exists. The purpose of the exerciser procedure is to stress the target hardware in a way that meets or exceeds the stress typically placed on that hardware in the customer environment. Exercisers are not generally interactive.
To exercise a selected device or devices, the target device(s) must not only support exercise operations, it must also currently be idle.
When you first start to exercise a device(s), the device(s) state on the device map will be changed to "RUNNING".
If the operation requires you to interact with the interface, the device state will change to "Query Pending". If the UI started the tool, the query will display automatically. If the UI did not start the tool, you must type DisplayQuery to display the query.
Once the exercise operation has completed, this state will change to "Success", "WARNING", or "FAILURE", as appropriate.
You should then consult the ExerFailLog for information on tool failures, and the ExerActLog for all other tool activity information.
Syntax: exeractlog | eal
Use this command to review the log which contains details concerning the most recent invocation of an Exercise Tool on all selected devices. The command is valid when a Tool Activity Log for an Exercise Tool exists for the selected device(s).
Syntax: exerfaillog | efl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of an Exercise Tool on all selected devices. The command is valid when a Tool Failure Log for an Exercise Tool exists for the selected device(s).
Syntax: exerinfo | einf
Use this command to display help information unique to the Exercise Tools for the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: firmwareupdate | fwu
Use this command to initiate the firmware update process for a selected device. While the user interface to the firmware update tools is generic, the tools themselves are device-specific.
This command is only valid when exactly one device is selected, that device is not currently busy, and the device supports the firmware update process.
NOTE: Be sure that you put the firmware file on the UUT before starting the update process.
CAUTION: Make sure you select the correct firmware file for the device! Updating a device with incorrect firmware can make the device permanently unusable and data could be lost.
CAUTION: It is not advisable to interrupt or abort the firmware update commands.
Syntax: fwupdateactlog | fal
Use this command to review the log which contains details concerning the most recent invocation of a Firmware Update Tool on all selected devices. The command is valid when a Tool Activity Log for a Firmware Update Tool exists for the selected device(s).
Syntax: fwupdatefaillog | ffl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of a Firmware Update Tool on all selected devices. The command is valid when a Tool Failure Log for a Firmware Update Tool exists for the selected device(s).
Syntax: fwupdateinfo | finf
Use this command to display help information unique to the Firmware Update Tools for the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: experttool | xt
Use this command to invoke the expert tool for the selected device. Expert tools are device-specific troubleshooting utilities for use by sophisticated users. Their command set varies from tool to tool, but they are intended to be interactive, and rely on you to provide information necessary to perform a particular task.
This command is only valid when you select exactly one device, that device is not currently busy, and the selected device has an associated expert tool.
Syntax: expactlog | xal
Use this command to review the log which contains details concerning the most recent invocation of an Expert Tool on all selected devices. The command is valid when a Tool Activity Log for an Expert Tool exists for the selected device(s).
Syntax: expfaillog | xfl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of an Expert Tool on all selected devices. The command is valid when a Tool Failure Log for an Expert Tool exists for the selected device(s).
Syntax: expinfo | xinf
Use this command to display help information unique to the Expert Tools for the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: runutil | ru [utility {<utility name>}]
Use this command to run support tools which are not device-specific. Current tools include logging and disk backup tools.
This dialog allows you to specify which utility log information you wish to access, based on time of execution, or the device on which the utility was run.
This dialog allows you to specify which utility's log you wish to access, either the last utility executed by the UI, or the last utility executed by the UI on a particular device.
Enter "utility" or its index number if you want to view the Tool Activity Log for the most recently executed utility on the Unit Under Test (UUT), without specifying a particular device.
To select the utility, enter the appropriate utility name or index number at the prompt; then enter "ok".
Enter "device" or its index number if you want to view the Tool Activity Log for the most recently executed utility on a particular device.
To select the device, enter the appropriate device address at the "Select Device" prompt; then enter "ok".
Select a utility to run from the list displayed, then enter "OK" to proceed.
If you choose not to continue with utility selection and execution, enter "Cancel" instead.
This dialog allows you to select a utility from a list, and get more information about it.
Select the name of a utility from the list displayed to access more information about the selected utility. Enter "OK" to proceed. If you decide you do not wish to access the utility's information screen at this time, enter "Cancel" instead.
Syntax: utilactlog | ual [utility {<utility name>} | device {<device num>}]
Use this command to review the log which contains details concerning the most recent invocation of a Utility Tool on all selected devices. The command is valid when a Tool Activity Log for the Utility Tool exists for the selected device(s).
Syntax: utilfaillog | ufl [utility {<utility name>} | device {<device num>}]
Use this command to review the log which contains details concerning failures encountered during the most recent execution of a Utility Tool on all selected devices. The command is valid when a Tool Failure Log for a Utility Tool exists for the selected device(s).
Syntax: utilinfo | uinf [utility {<utility name>}]
Use this command to display help information unique to the Utility Tool for the selected devices. It may always be run, because it does not access the device to obtain its information.
Syntax: lateactlog | lal
Use this command to review the log which contains details concerning the most recently run tool on all selected devices. The command is valid when a Tool Activity Log for the most recently run tool exists for the selected device(s).
Syntax: latefaillog | lfl
Use this command to review the log which contains details concerning failures encountered during the most recent execution of a tool on all selected devices. The command is valid when a Tool Failure Log for the most recently executed tool exists for the selected device(s).
Syntax: aborttool | abt
Use this command to stop execution of the currently running tool on all selected devices.
Syntax: suspendtool | st
Use this command to momentarily halt execution of a support tool running on all selected devices.
See also ResumeTool.
Syntax: resumetool | ret
Use this command to restart execution of a suspended tool running on all selected device(s).
See also SuspendTool.
Syntax: abortutil | abu [utility {<utility name>}]
Use this command to halt execution of a utility running under cstm. Only one utility from the list of utilities can be selected at a time. Only currently executing or suspended utilities are listed. On HP-UX systems, the id number displayed is the utility's process id on the Unit Under Test (UUT).
From the list of currently executing or suspended utilities displayed to you, select one to abort, then enter "OK" to proceed. If you decided you do not wish to abort the selected utility, enter "Cancel" instead.
You selected the AbortUtil function, but there are no currently executing or suspended utilities to abort. To repeat your selection, enter "OK". To proceed without attempting to abort a utility, enter "Cancel".
Syntax: displayquery | dq
Use this command when a non-interactive tool requires your input in order to continue processing. Selecting "Display 'Query Pending'" will cause the support tool's request for information to be displayed, so that you can respond to it.
Syntax: attach | at [tool {<tool name>}]
Use this command to connect the display to a specified interactive support tool, after an "escape to UI" has been executed. You will be shown a list of non-suspended interactive support tools, and then you choose the one you want connected to your display. This command is invalid if there are no currently non-escaped interactive support tools.
Use this command to select an interactive support tool after the "Attach" comand has been entered. You will be shown a list of non-suspended interactive support tools, and then you choose the one you want connected to your display. This command is invalid if there are no currently non-escaped interactive support tools.
Enter "OK" to proceed, and "Cancel" if you decide not to continue with execution of the "Attach" command.
There are no currently non-suspended interactive tools available. You cannot attach the UI to an interactive tool at this time.
Select "OK" to proceed.
Syntax: wait | wait
Use this command to cause the user interface to wait until all invoked support operations have been completed before continuing. If a tool is in the "Starting", "Running", "Delayed" or "Hung" state, it is considered busy.
This command is automatically inserted after a tool is run while recording commands, to prevent operations which were executed sequentially at record time from being attempted simultaneously at playback time.
Note: the wait will exit if the general option "Terminate Wait Command If Any Tool Not Successful" is set and any tool is in the "Failed" or "Warning" state.
Syntax: killtool | klt
Use this command to kill a tool which is in the "abort pending" state, but which doesn't manage to abort properly (see also Killutil).
For tools which are not in the "abort pending" state, you should first try AbortTool.
Syntax: killutil | klu
Use this command to kill a utility which is in the "abort pending" state, but which doesn't manage to abort properly (see also Killtool).
For utilities which are not in the "abort pending" state, you should first try AbortUtil.
The Options Category includes ten commands:
Syntax: infooptions | iop [gentactlog {yes | no}] [reporterrors | reportwarnings | reportinfo] [queries {yes | no}]
Use this command to configure the options which will be used for subsequently executed information tools, including:
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
If you want to interact with a specified tool, instead of using the tool's default information values, enter "y" at this prompt.
WARNING: When you disable the "Allow User Queries" function, some tools will perform DESTRUCTIVE tests. This means that ALL DATA on unmounted disks WILL BE DESTROYED. The ability to disable this function is intended for manufacturing purposes only. It is highly recommended that you use the "Allow User Queries" function, and DO NOT DISABLE IT.
Syntax: veroptions | vop [execctrl] [iterations {<loop count>} | time {<minutes>} | continuously] [behavior] [errorexit | errorcount {<errors allowed before test termination>}] [testcoverage] [maxcoverage | medcoverage | mincoverage] [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo] [queries] [queryallow | querynondes | querydes]
Use this command to configure the options which will be used for subsequently executing verify tools, including:
You can control execution of future diagnose commands via the three options associated with this heading:
Enter "iterations" if you want to define the number of times the diagnose test procedure is to be repeated before it halts.
Enter "time" if you want to define the length of time the diagnose test procedure is to run (in minutes), before it halts.
Enter "continuously" if you want the diagnose test procedure to repeat until you halt or abort it.
Using the options associated with this heading, you can define the way in which you want a specified tool to behave on encountering a "soft" error; e.g., a recoverable read error (hard errors, by contrast, cause the tool to create a failure log and exit, no matter how this option is set).
You may choose to exit the tool on finding an error, you may terminate test execution after a certain number of errors have been encountered, or you may choose to continue tool execution in spite of encountering an error.
Enter "exit" if you want a specified tool to exit on encountering an error.
Enter "count" if you want a specified tool test to terminate when a certain number of "soft" errors (for example, recoverable read errors) are encountered.
Enter "continue" if you want a specified tool test to continue test execution when errors are encountered.
Using the options associated with this heading, you can specify either maximum, moderate, or minimum test coverage.
Enter "maximum" when you want to verify system hardware as thoroughly you can. Note that selecting this level of coverage may require significantly longer execution time for some devices.
Enter "medium" when you want to verify system hardware with a moderate degree of confidence.
Enter "minimum" when you want to verify system hardware, but only to the minimum standard level of adequacy and acceptance.
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
You may select whether to interact with a specified tool, or to use the tool's default information values, depending upon which of the following commands you enter:
When you enter this command, you can interact with a specified tool, instead of using the tool's default information values.
When you enter this command, you can disable the "User Queries" function, and run the tool both non-interactively and non-destructively.
When you enter this command, you will perform DESTRUCTIVE tests non-interactively.
You will see the following WARNING message displayed:
WARNING: You have set the User Queries option to enable destructive tests. ----------------------------------------------------------------------------- When User Queries is set to 'Disallow: allow destructive operations,' some tools will perform DESTRUCTIVE tests. For example, ALL DATA on unmounted disk drives WILL BE DESTROYED. The 'Disallow: allow destructive operations' setting of the User Queries option is intended for manufacturing tests only. Use of this setting is highly discouraged. ----------------------------------------------------------------------------- To change the User Queries option, you must re-enter the (verify / exercise / diagnose) options menu.
When you enter this command, you will perform DESTRUCTIVE tests non-interactively. This means that ALL DATA on unmounted disks WILL BE DESTROYED. This option is intended for manufacturing purposes only. It is highly recommended that you either use the Allow or Disallow (Non-Destructive) option instead.
Syntax: diagoptions | dop [execctrl] [iterations {<loop count>} | time {<minutes>} | continuously] [isolation] [fru | component] [testcoverage] [maxcoverage | medcoverage | mincoverage] [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo] [queries] [queryallow | querynondes | querydes]
Use this command to configure the options which will be used for subsequently executing diagnostic tools, including:
You can control execution of future diagnose commands with the three options associated with this heading:
Enter "iterations" if you want to define the number of times the diagnose test procedure is to be repeated before it halts.
Enter "time" if you want to define the length of time the diagnose test procedure is to run (in minutes), before it halts.
Enter "continuously" if you want the diagnose test procedure to repeat until you halt or abort it.
Using the options associated with this heading, you can choose to diagnose down to either the Field Replaceable Unit (FRU) or component level.
Enter "fru" to diagnose down to the level of a Field Replaceable Unit (FRU).
Enter "component" to diagnose down to the component level.
Using the options associated with this heading, you can specify either maximum, moderate, or minimum test coverage.
Enter "maximum" when you want to diagnose system hardware as thoroughly you can. Note that selecting this level of coverage may require significantly longer execution time for some devices.
Enter "medium" when you want to diagnose system hardware with a moderate degree of confidence.
Enter "minimum" when you want to diagnose system hardware, but only to the minimum standard level of adequacy and acceptance.
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
You may select whether to interact with a specified tool, or to use the tool's default information values, depending upon which of the following commands you enter:
When you enter this command, you can interact with a specified tool, instead of using the tool's default information values.
When you enter this command, you can disable the "User Queries" function, and run the tool both non-interactively and non-destructively. This option is intended for manufacturing use.
When you enter this command, you will perform DESTRUCTIVE tests non-interactively.
You will see the following WARNING message displayed:
WARNING: You have set the User Queries option to enable destructive tests. ----------------------------------------------------------------------------- When User Queries is set to 'Disallow: allow destructive operations,' some tools will perform DESTRUCTIVE tests. For example, ALL DATA on unmounted disk drives WILL BE DESTROYED. The 'Disallow: allow destructive operations' setting of the User Queries option is intended for manufacturing tests only. Use of this setting is highly discouraged. ----------------------------------------------------------------------------- To change the User Queries option, you must re-enter the (verify / exercise / diagnose) options menu.
Syntax: exeroptions | eop [execctrl] [time {<minutes>} | continuously] [behavior] [errorexit|errorcount {<errors allowed before test termination>}] [testcoverage] [maxcoverage | medcoverage | mincoverage] [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo] [queries] [queryallow | querynondes | querydes]
Use this command to configure the options which will be used for subsequently executing exerciser tools, including:
You can control execution of future exercise commands with the two options associated with this heading:
Enter "time" if you want to define the length of time the exercise test procedure is to run (in minutes), before it halts.
Enter "continuously" if you want the exercise test procedure to repeat until you halt or abort it.
Using the options associated with this heading, you can define the way in which you want a specified tool to behave on encountering a "soft" error; e.g., a recoverable read error (hard errors, by contrast, cause the tool to create a failure log and exit, no matter how this option is set).
You may choose to exit the tool on finding an error, you may terminate test execution after a certain number of errors have been encountered, or you may choose to continue tool execution in spite of encountering an error.
Enter "exit" if you want a specified tool to exit on encountering an error.
Enter "count" if you want a specified tool test to terminate when a certain number of "soft" errors (for example, recoverable read errors) are encountered.
Enter "continue" if you want a specified tool test to terminate when a certain number of errors are encountered.
Using the options associated with this heading, you can specify either maximum, moderate, or minimum test coverage.
Enter "maximum" when you want to exercise system hardware as thoroughly you can. Note that selecting this level of coverage may require significantly longer execution time for some devices.
Enter "medium" when you want to exercise system hardware with a moderate degree of confidence.
Enter "minimum" when you want to exercise system hardware, but only to the minimum standard level of adequacy and acceptance.
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
You may select whether to interact with a specified tool, or to use the tool's default information values, depending upon which of the following commands you enter:
When you enter this command, you can interact with a specified tool, instead of using the tool's default information values.
When you enter this command, you can disable the "User Queries" function, and run the tool both non-interactively and non-destructively.
When you enter this command, you will perform DESTRUCTIVE tests non-interactively.
You will see the following WARNING message displayed:
WARNING: You have set the User Queries option to enable destructive tests. ----------------------------------------------------------------------------- When User Queries is set to 'Disallow: allow destructive operations,' some tools will perform DESTRUCTIVE tests. For example, ALL DATA on unmounted disk drives WILL BE DESTROYED. The 'Disallow: allow destructive operations' setting of the User Queries option is intended for manufacturing tests only. Use of this setting is highly discouraged. ----------------------------------------------------------------------------- To change the User Queries option, you must re-enter the (verify / exercise / diagnose) options menu.
Syntax: fwupdateoptions | fop [file {<update file>}] [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo]
Use this command to configure the options which will be used for subsequently executing firmware update tools, including:
You enter the path (i.e., directory) and filename of the file from which you wish to load the updated firmware information. Hit "Return" and the firmware will be updated from that file whenever the "Firmware Update" command is executed.
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The associated radio buttons will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
Syntax: expoptions | xop [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo]
Use this command to configure the options which will be used for subsequently executing expert tools, including:
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
Syntax: utiloptions | uop [gentactlog {yes|no}] [reporterrors | reportwarnings | reportinfo]
Use this command to configure the options which will be used for subsequently executing utility tools, including:
Enter "y" at this prompt, if you want to keep a log of all actions performed by a selected tool. The succeeding prompts will let you specify whether or not you want to log only errors, errors and warnings, or errors, warnings, and information.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt, if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
Syntax: launchoptions | lop [debugmode {yes|no}] [sourcedir {<path to source code}] [motifflag {yes|no}] [display {<address of display machine}]
[testmode {yes|no}] [filename {<systest input file}]
Use this command for assistance in debugging and testing tools developed for cstm.
The dialog contains two checkboxes to enable Debug and Test Modes.
NOTE: Both modes may be enabled at the same time.
Debug mode is used to provide information for the Distributed Debugging Environment (DDE) debugger.
Test mode is used to specify a systest() input file.
Enter "y" at this prompt when you want to provide information for the Distributed Debugging Environment (DDE) debugger.
Enter the name of the source directory for the tool being debugged here.
Enter "y" at this prompt when you want to use the graphical user interface to DDE while in Debug Mode.
If you enter "n" at this prompt, the line mode interface to DDE will be used, instead.
When you use the graphical mode, the display may be specified here, or it may be allowed to default to the DISPLAY environment variable.
Test mode is used to specify a systest() input file.
You enter the path (i.e., directory) and filename of the systest() file you wish to specify. Hit "Return" and the firmware will be updated from that file.
Syntax: mapoptions | mop [maprefresh {<seconds>}] [textmap {yes|no}] [showpath {yes|no}] [pathwidth {<path field width}] [showprod {yes|no}] [showqual {yes|no}] [prodwidth {<product field width}] [showtool {yes|no}] [showtimeused {yes|no}] [showtimetogo {yes|no}] [showloopsdone {yes|no}] [showloopstogo {yes|no}] [showstatus {yes|no}] [statuswidth {<status field width}]
Use this command to configure cstm options pertaining to the device map.
The "Map Refresh Rate" field allows you to specify how often (in seconds) the device map is to be updated; the default is every 2 seconds. When the user interface is being run on a system other than the system under test, the device map information is sent between the systems at this rate.
The "Display cstm Device Map in Text Format" field allows you to display the device map in a format similar to that used in the menu interface, while running cstm; the default is "not set" (i.e., the icon map option is selected).
The "Include in Device Map" checkboxes allow you to specify which items are to be displayed in the device map.
The "Width of Fields Map" allows you to specify how many characters are to be used to display certain fields in the line oriented maps An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.
The "Map Refresh Rate" field allows you to specify how often (in seconds) the device map is to be updated; the default is every 2 seconds. When the user interface is being run on a system other than the system under test, the device map information is sent between the systems at this rate.
The "Display cstm Device Map in Text Format" field allows you to display the device map in a format similar to that used in the menu interface, while running cstm; the default is "not set".
Enter "y" at this prompt to include path information in the device map; that is, the hardware address of a device, like "2.4.3".
The "Path Field Width" field allows you to specify how many characters are to be used to display the hardware path information in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.
Enter "y" at this prompt to include product name information in the device map; for example, "HP 19744R".
The "Product Field Width" field allows you to specify how many characters are to be used to display the product name in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.
Enter "y" at this prompt to ensure that the device map indicates which tool(s) is currently active.
Enter "y" at this prompt when you want to show elapsed time during non-interactive tool execution.
Enter "y" at this prompt when you want to show time remaining during non-interactive tool execution.
Enter "y" at this prompt when you want to show how many complete repetitions of a non-interactive tool test have been completed.
Enter "y" at this prompt when you want to show how many complete repetitions of a non-interactive tool test are left to complete.
When you enter "y" at this prompt, this field will indicate the progress of the currently running tool, as a measure of percentage of execution completed. If no tools are running, it will indicate the status of the last tool that was run.
The "Last Operation Status Field Width" field allows you to specify how many characters are to be used to display operation status/percentage of test completed in the line oriented maps. An additional space, not counted in the field width, is used to separate fields. In all line oriented maps, you can leave more room on the line for other items by eliminating an item from the map, or by restricting its width.
Enter "y" at this prompt to display a graphic (scale) representation of forward test progress; i.e., to display the percentage of the test which has already completed.
Syntax: generaloptions | gop [queries {yes | no}] [confirmation {yes|no}] [hostinfo {yes|no}] [termwait {yes|no}] [cstmpager {<pager>}] [printers {<printer name>}] [uiactivitylog] [reporterrors] [reportwarnings] [reportinfo] [launchoptions {yes|no}]
Use this command to configure the following cstm options:
The "Queries are Displayed Immediately" prompt controls the behavior of queries. When a non-interactive support tool attempts to display a query, the question will be presented to you immediately, provided you entered "y" at the prompt. If you entered "n" at the prompt, the status is changed to "Query Pending".
The "Cstm Pager" field allows you to specify a program to be used to control the output of the "map", "help", and log viewing commands to the terminal. If this field is blank, the output is written to the terminal or other output device without interruptions. If used from a terminal, however, the output may scroll beyond the top of the terminal. In such a case, you may want to specify that the "Cstm Pager" be "more". The default state is "more -d".
The "Printers" list shows the different printers configured on the system on which cstm is being run. The printer which is selected by entering its index number is the one which will be the default printer for subsequent print operations. The default printer is the system default printer.
The "UI Activity Log" prompt and its succeeding prompts allow you to specify the verbosity of the UI Activity Log contents generated by the interface. You may specify that only errors be logged, that errors and warnings be logged, or that errors, warnings, and information messages be logged.
The "Tool Developer Launch Options" prompt enables tool developers to debug and test tools developed for cstm.
See also LaunchOptions.
The "Queries are Displayed Immediately" prompt controls the behavior of queries. When a non-interactive support tool attempts to display a query, the question will be presented to you immediately, provided you entered "y" at the prompt.
Enter "y" at this prompt, when you want to be prompted before the user interface overwrites any files. This only applies to files which you select via the file selection dialogs generated by the user interface. It does not apply to log files.
Enter "y" at this prompt, when you want information about your host systems to be updated dynamically whenever you invoke one of the "Select System to Test" dialogs.
The "Cstm Pager" field allows you to specify a program to be used to control the output of the "map", "help", and log viewing commands to the terminal. If this field is blank, the output is written to the terminal or other output device without interruptions. If used from a terminal, however, the output may scroll beyond the top of the terminal. In such a case, you may want to specify that the "Cstm Pager" be "more". The default state is "more -d".
The "Printers" list shows the different printers configured on the system on which cstm is being run. The printer which is selected by entering its index number at the prompt, is the one which will be the default printer for subsequent print operations. The default printer is the system default printer.
The prompts under this heading allow you to specify the verbosity of the UI Activity Log contents generated by the interface. You may specify that only errors be logged, that errors and warnings be logged, or that errors, warnings, and information messages be logged.
Enter "y" at this prompt if you want to keep a log of all errors encountered by a selected tool.
Enter "y" at this prompt if you want to keep a log of all errors encountered by a selected tool, and all warnings generated as a result of tool activity.
Enter "y" at this prompt if you want to keep a log of all errors encountered by a selected tool, and all warnings and information messages generated as a result of tool activity.
The "Tool Developer Launch Options" prompt allows you to request assistance in debugging and testing tools developed for cstm.
If you select this checkbox, the "Run Command File" command will abort execution on finding an error.
The Help Category includes two commands:
Syntax: help [all|more|syntax|<command name>|<accelerator name>]
Access online help by entering one of the following commands at the cstm> prompt:
help Summary of commands help more Description of all commands help syntax Description and syntax of all commands help all Description of cstm and access to online help help COMMAND_NAME (or ACCELERATOR_NAME) Help on an individual command help help Description of the help system
HP-UX 11.20 does not provide help on individual cstm commands (help COMMAND_NAME). Nor does it provide the complete help system described below. Instead, you can get this information from Web-based online help (this document.)
For HP-UX 10.20, 11.00, and 11i, access the complete help system by entering
help all
Once you have entered online help, help text is displayed on your screen. You move through the text by using a pager program (for example "more"). For long help text, you may want to use the pager commands (for example in "more", enter "/STRING" to search for the next instance of a string).
After the text has been displayed on the screen, you can choose one of the following:
Home - to view the home help topic ("table of contents")
Back - to view the previous help topic (if there was one)
Exit - to exit the help viewer
If there are any hyperlinks to related topics, they are also displayed. You can jump to one of these topics by entering the number that corresponds to the topic.
--------------------------------------------------------------
Printing Online Help
You can print online help information, by recording cstm output to a file, then executing the desired help commands.
cstm> recordoutput file FILE_NAME
cstm> generaloptions cstmpager cat
cstm> help syntax
cstm> stoprecordout
os lp FILE_NAME
exit
--------------------------------------------------------------
Selecting a Pager
The cstm help uses a pager program to display long help text. After each page of text, you may see a prompt like this:
[Press space to continue, q to quit, h for help]
Pressing "h" displays help information for using this pager ("more").
Cstm determines the pager to use in this way:
To select a different pager, you can use the cstm command:
cstm> generaloptions cstmpager PAGER_NAME
where PAGER_NAME is the name of the desired pager (for example, "pg"). Specify "cat" to suppress paging.
Syntax: version | vers
This command displays version information for the current cstm interface.
This section lists the cstm command syntax, giving each cstm command and accelerator command followed by its optional keywords, and a description of the command's purpose.
Notation
--------
[] optional
{} required
<> description of text to enter following a keyword
| or
Format
------
command | abbreviated command
[keyword {required keyword response}]
NOTE: Only the least number of characters that make each cstm command and keyword unique need to be entered. If only one keyword exists in a command, it may be implied.
Keywords are grouped by category (File, System, Device, etc.), corresponding the xstm menus or mstm function keys.
File:
saveconfig | scfg [file {<file name>}] Save current interface state as file commands
restoreconfig | rcfg [file {<file name>}] Read/execute saved config commands from file
recordcmdfile | rcf [description {<description string>}] [file {<full file path>}] Enable/disable recording of commands to file in cstm format
stoprecordcmd | srcf Disable recording of executed commands
runcmdfile | rncf [file {<full file path>}] [stop {yes|no}] Read/execute sequence of cstm commands from file
recordoutput | ro [description {<description string>}] [file {<full file path>}] Record commands/output to file in cstm format
stoprecordout | sro Disable terminal output recording.
uiactlog | uial View log of errors encountered by cstm
readuutconfigfile | ruc Read config file on current test system
updatetoolinfo | uti Reread list of available tools for a device
stmstartup | ssu Turn off diagnostics on local machine
stmshutdown | ssd Restart diagnostics on local machine
resetsysactlog | rsa Clear System Activity Log on current UUT
localmaplog | lml View the Scan HW Log on local system
localsysactlog | lsal View the System Activity Log on local system
syslog | sl View log of system daemon information
os | os Suspend STM and invoke an OS command shell
quit | q Leave cstm
exit | ex Leave cstm
System:
connectsys | cs [system {<system name>}] Connect to test system chosen from list
selcurrentsys | scs [system {<system name>}] Select current test system from a list
disconnectsys | ds [system {<system name>}] Disconnect from test systems on list
savemap | smap [file {<full file path>}] Write ASCII copy of device map to file
printmap | pmap [printers {<printer name>}] Print ASCII copy of device map to printer
remapsystem | rs UUT re-examines configured hardware
maplog | ml Record of all system devices in last map
displaylic | dl Display the currently installed license level.
license | lic [password {<stm license password>}] Obtain required license level to run tools
hplicense | hlic [password {<hp license password>}] Obtain required license level to run HP-only tools
deinstalllic | dlic Deinstall licenses on the current test system
sysactlog | sal Record of all operations performed by cstm
daemonstartup | dsu [daemon {<daemon name>}] Initiate a daemon on the test machine
daemonshutdown | dsd [daemon {<daemon name>}] Abort a daemon on the test machine
daemonkill | dk [daemon {<daemon name>}] Kill a daemon on the test machine
daemonactlog | dacl [daemon {<daemon name>}] View a daemon activity log
map To explicitly request a map display
Device:
currdevstatus | cds Display device info/suggest further action
cleartoolstatus | cts Reset map status for devices not under test
select | sel {[-] all|device {[-] all|<device num>|<device num> - <device num>}| path {[-] all | <path string>}} Choose a single device for testing
selclass | scl [type {all|<device type>}] [qualifier {all|<device qualifier>}] [hwpath {<path name>}] Choose several devices for testing
selall | sall Choose all devices in the hardware map
unselclass | uscl [type {all|<device type>}] [qualifier {all|<device qualifier>}] [hwpath {<path name>}] Deselect several devices in the hardware map at the same time
unselall | usal Deselect all devices in the hardware map
Tools:
information |info Generate an info log for a selected device
infolog | il View log describing/indentifying a device
infoactlog | ial View log of actions performed on a device
infofaillog | ifl View log of test failures on a device
infoinfo | iinf View tool-specific help for a device
verify | ver Pass/fail test of hardware's usability
veractlog | val View log of actions performed on a device
verfaillog | vfl View log of test failures on a device
verinfo | vinf View tool-specific help for a device
diagnose | dgn Error isolation test to the FRU level
diagactlog | dal View log of actions performed on a device
diagfaillog | dfl View log of test failures on a device
diaginfo | dinf View tool-specific help for a device
exercise | exc Stress test of target hardware for intermittents
exeractlog | eal View log of actions performed on a device
exerfaillog | efl View log of test failures on a device
exerinfo | einf View tool-specific help for a device
firmwareupdate | fwu Update firmware on a selected device
fwupdateactlog | fal View log of actions performed on a device
fwupdatefaillog | ffl View log of test failures on a device
fwupdateinfo | finf View tool-specific help for a device
experttool | xt Run device-specific interactive tool
expactlog | xal View log of actions performed on a device
expfaillog | xfl View log of test failures on a device
expinfo |xinf View tool-specific help for a device
runutil | ru [utility {<utility name>}] Run non-device-specific cstm tools
utilactlog | ual [utility {<utility name>}|device {<device num>}] View log of actions performed on a device
utilfaillog | ufl [utility {<utility name>}|device {<device num>}] View log of test failures on a device
utilinfo | uinf [utility {<utility name>}] View tool-specific help for a device
aborttool | abt Prematurely halt tool executing on a device
suspendtool | st Pause execution of tool on a device
resumetool | ret Start running suspended tool on a device
abortutil | abu [utility {<utility name>}] Prematurely halt utility executing on a device
displayquery | dq Display tool request for input/action
attach | at [tool {<tool name>}] Connect display to selected interactive tool
wait Continue only after current operations complete
Options:
infooptions | iop [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] [queries {yes|no}] Configure information tool options
veroptions | vop [execctrl] [iterations {<loop count>}|time {<minutes>}|continuously] [behavior] [errorexit|errorcount {<errors allowed before test termination>}] [testcoverage] [maxcoverage|medcoverage|mincoverage] [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] [queries] [queryallow|querynondes|querydes] Configure verification tool options
diagoptions | dop [execctrl] [iterations {<loop count>}|time {<minutes>}|continuously] [isolation] [fru|component] [testcoverage] [maxcoverage|medcoverage|mincoverage] [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] [queries] [queryallow|querynondes|querydes] Configure diagnostic tool options
exeroptions | eop [execctrl] [time {<minutes>}] [continuously] [behavior] [errorexit|errorcount {<errors allowed before test termination>}] [testcoverage] [maxcoverage|medcoverage|mincoverage] [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] [queries] [queryallow|querynondes|querydes] Configure exerciser tool options
fwupdateoptions | fop [file {<update file>}] [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] Configure firmware update options
expoptions | xop [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] Configure expert tool options
utiloptions | uop [gentactlog {yes|no}] [reporterrors|reportwarnings|reportinfo] Configure utility options
launchoptions | lop [debugmode {yes|no}] [sourcedir {<path to source code>}] [motifflag {yes|no}] [display {<address of display machine>}] [testmode {yes|no}] [filename {<systest input file>}] Enable/define test and debug options
mapoptions | mop [maprefresh {<seconds>}] [textmap {yes|no}] [showpath {yes|no}] [pathwidth {<path field width>}] [showprod {yes|no}] [showqual {yes|no}] [prodwidth {<product field width>}] [showtool {yes|no}] [showtimeused {yes|no}] [showtimetogo {yes|no}] [showloopsdone {yes|no}] [showloopstogo {yes|no}] [showstatus {yes|no}] [statuswidth {<status field width>}] Configure device map options
generaloptions | gop [queries {yes|no}] [confirmation {yes|no}] [hostinfo {yes|no}] [termwait {yes|no}] [cstmpager {<pager>}] [printers {<printer name>}] [uiactivitylog] [reporterrors] [reportwarnings] [reportinfo] [launchoptions {yes|no}] Configure general interface options
Help:
help [all|more|syntax|<command name>|<accelerator name>] Access online help
version | vers Display current interface version banner
The section is devoted to dialog help messages.
If the command file input displayed on your screen is correct, and you wish to proceed, enter "OK".
If the command file input displayed on your screen is not correct, then enter "Cancel" instead.
Once you have read the information message displayed on the screen, enter "OK" to continue.
You have attempted to access non-existent log files. Select "OK" to proceed.
If you enter "OK", you will overwrite an existing file. Enter "Cancel" if you don't wish to do this.
You chose to abort an interactive tool. If you are certain that you wish to continue with the abort operation, then enter "OK" to proceed.
If you do not wish to proceed with the abort operation, then enter "Cancel" instead.
This dialog provides options that allow you to view a file (optional), save a file, print a file, remove a file, exit the file viewer, or access the help function.
This dialog provides options that allow you to view a file (optional), save a file, print a file, exit the file viewer, or access the help function.
There are messages logged in the file, that were not found in the catalog, or file formatting was truncated.
Enter "OK" to proceed.
If you do not wish to format your log file, or wish to stop formatting at this time, enter "Cancel".
This dialog allows you to specify a log file to be printed, and then print the selected log file, or cancel the print.
Printer Name: Select the name of the printer to which you wish to print, then enter "OK" to proceed. If you decide not to proceed with the print operation, enter "Cancel" instead.
This dialog allows you to specify a log file to be saved, and then save the selected log file, or cancel the save.
File Name: Select the name of the log whose contents you wish to save, then enter "OK" to proceed.
If you decide not to proceed with the save operation, enter "Cancel" instead.
Syntax: displaylic | dl
This dialog displays the currently installed license level. Select "OK" to proceed.
You have requested connection to a system that you selected. Please enter your logon account name and password at this time. If you do not have an account on the selected system, or can't remember your logon name and/or password, please contact the system administrator for the system you wish to connect to.
You have requested connection to a system that you selected. Please enter your logon account name at this time. If you do not have an account on the selected system, or can't remember your logon name, please contact the system administrator for the system you wish to connect to.
You have requested connection to a system that you selected. Please enter your logon password at this time. If you do not have an account on the selected system, or can't remember your password, please contact the system administrator for the system you wish to connect to.
If you want to exit the Support Tools Manager, enter "OK". If you have changed your mind and have decided you don't want to exit the Support Tools Manager, then enter "Cancel".
If you are currently running an interactive tool, you may want to wait until the interactive tool completes execution before exiting the Support Tools Manager.
If you enter "OK", you will overwrite the currently existing file of the same name.
If you wish to retain your original file (that is, if you don't wish to overwrite its contents), enter "Cancel".
You specified a file which already exists. You can either replace the existing file, or append the new file to the existing file.
Replace/Append File: Select an option: replace the existing file, or append the new file to the existing file.
Replace File: To replace the existing file with the new file, select this option. Then enter "OK" to proceed. If you have decided that you do not wish to replace the existing file at this time, enter "Cancel" instead.
Append File: To append the new file to the existing file, select this option. Then enter "OK" to proceed. If you have decided that you do not wish to append the new file to the existing file at this time, enter "Cancel" instead.
You have encountered an error condition. If you are advised to consult a log, please do so at this time.
To proceed, enter "OK".
You have made a mistake in entering your input. You may have entered
Alternatively, you may have failed to
Once you have understood the error condition, and what corrective action(s) you need to take, enter "OK".
You have encountered a syntax error. Syntax errors can be generated by a variety of different error conditions; for example,
The best thing to do is to read the error message again, to see if it identifiesa cause or causes for the error condition, and then perform any explicit or implicit actions which it recommends. For instance, if you are told that the integer value you entered is out of range, and you are given the valid range for integer values, this is an implicit suggestion that you should enter a different integer value which does fall within the range of valid values specified.
Once you are satisified that you understand the cause or causes of the error condition, and know what explicit or implicit action to take, enter "OK" to proceed.
Use this function to write a copy of the tool's main window to a specified file.
Use this function to print a copy of the tool's main window to a specified printer. The list of available printers includes all those configured on the system on which the cstm is being run.
The Support Tool Manager maintains log files to help you understand and troubleshoot error conditions. Errors due to events which are likely to occur (like trying to read a non-existent file), are not logged; errors due to events which are not likely to occur are logged. Which log file you should examine will depend upon the nature of the error condition which has occurred. The following logs are those which you should consult when errors occur: