Inspect Manual

Notes for System Operators
Inspect Manual—429164-006
C-2
Usage Considerations
If you do not specify a backup processor, the primary IMON process selects a
processor for the backup process using these guidelines:

IMON regards the system as a group of even-odd processor pairs (0,1), (2,3), and
so on.

If the primary IMON process is running in one processor of such a pair, the backup
IMON process will be run in the other member of the pair.
Consequently, if your system has an odd number of processors, and the primary IMON
process is in the last processor, IMON cannot create a backup because the other
member of the pair doesn't exist. In this case, you must specify a backup processor.
Usage Considerations

IMON assumes that the program files for the DMON and Inspect processes are in
the same volume and subvolume as the IMON program file.

Users can issue an implicit RUN command to start Inspect only if the Inspect
program file is in the $SYSTEM.SYSTEM subvolume or the currently running
$SYSTEM.SYSnn subvolume.
IMON and CMON
The IMON process always communicates with the CMON process (if present) for the
CPU number and priority to start Inspect. Inspect should be started at the same priority
as command interpreters or other interactive programs. The IMON process sends the
request to the CMON process with the Inspect file name in the local internal file format,
which implies that the Inspect file name does not contain the node number.
Stopping IMON and DMON Processes
To stop the Inspect subsystem, stop the IMON process and then stop all DMON
processes. To stop IMON, use the name form of the TACL command STOP. For
example:
> STOP $IMON
Only the super ID (255,255) user can stop the primary IMON process.
Stopping the $IMON process pair by name stops only the IMON processes, not the
DMON processes. You should stop all the DMON processes after a $IMON pair has
been stopped. No special shutdown procedures are required for IMON and DMON
processes.
IMON restarts DMON processes when DMON ABENDs or STOPs. If DMON
repeatedly ABENDs, IMON will not restart DMON, and issue an error message. To
restart DMON, you must restart IMON.
Note. If the CMON process is not present or the IMON process is unable to communicate with
the CMON process, the IMON process starts Inspect at its own priority.