Inspect Manual

Inspect Manual—429164-006
A-1
A Error and Warning Messages
Inspect scans command lists command by command and notifies you of an error or
potential error by issuing an error or warning message:

An error message indicates that Inspect could not execute the command. When
Inspect generates an error message, it disregards the command that caused the
error and any commands that followed it in the command list.

A warning message indicates that Inspect was able to execute the command, but
that the user should be made aware of some detected condition. When Inspect
generates a warning message, it completes the command that caused the warning
and continues to the next command in the command list.
Fatal Errors During Session Start-Up
If IMON encounters a system error that prohibits it from creating an Inspect process, it
reports a fatal error and does not start an Inspect session. For example, if the
intended swap volume for the Inspect process is full, the operating system reports a
system error to IMON; IMON then reports a fatal error.
If Inspect encounters a fatal error, it will issue an internal stack trace and then ABEND.
On TNS/R systems, you must stop any processes you were debugging. On TNS/E
systems, the process will be activated. Report any fatal errors to your HP
representative.
HELP Availability
Error and warning message descriptions are available in online help. To access the
message descriptions from online help, enter “HELP ERROR” followed by the error or
warning number.
1
The sequence of input characters does not result in a valid Inspect command. Inspect
redisplays the input and places a caret (^) under the point where it detected the error.
Note. The file INSPMSG must be located in the same volume and subvolume as Inspect in
order for Inspect to access the textual messages it contains. If this file cannot be located,
Inspect issues only a number associated with a particular error or warning. No message
appears to help you diagnose the cause of the error.
Invalid syntax