Inspect Manual

Notes for System Operators

Inspect Manual—429164-006

C-5

DMON Errors

The following errors are reported by DMON.

This error is reported at DMON start up time if, for some reason, the initialization of the

operating system mechanism that reports debugging events to DMON failed.

This error is reported if DMON receives a debugging event and no IMON process

exists.

This error is reported if the DMON process encounters a run-time trap. n is the trap

number (in octal), and xxxxxx is the address.

This error is reported if an attempt is made to start DMON by running the DMON

program file. To start DMON, you must start IMON, IMON then starts a DMON in each

CPU.

This error is reported if, when DMON is processing a debugging event, it finds that the

process no longer exists. Process is a string of the form cpu,pin [(name)]. For example,

1,30 ($DBMON).

DMON reports this error if an error occurs during the creation of a save file for a

process. Depending on the error, this could indicate a resource shortage, such as disk

space.

This error is reported if an internal error is detected. If this error occurs, contact your

Tandem representative.

This error is reported if DMON's attempt to stop a process fails. (when a process that

has its Inspect bit set stops or abends, control of the process is given to DMON,

allowing it to create a save file if appropriate. DMON then calls STOP to complete

Initialization of Guardian event reporting failed

IMON ($IMON) does not exist

Fatal trap %n at P = %xxxxxx

DMON must be started by $IMON

Process deleted during DMON processing: process

Save file error nn, volume vol, process id, object file

Save file error - internal, P-%nnnnnn, process id, object

file

Unable to stop process: process