Inspect Manual

Inspect Concepts

Inspect Manual—429164-006

2-8

The Run State

A program is in the run state as long as it is executing. A program enters the run state

when it is first created (and it is not configured to enter the hold state immediately) or

when you enter a RESUME or STEP command to release it from the hold state.

A program leaves the run state when it completes execution, whether normally or

abnormally, or when a debug event occurs. In the former case, the program enters the

stop state. In the latter case, the program enters the hold or stop state, depending on

the nature of the debug event.

The Hold State

A program is in the hold state while its execution is suspended. A program enters the

hold state as the result of a debug event. Many Inspect commands are valid only when

the program is in the hold state. For example, you can use MODIFY to change data

values only when execution is suspended.

A program leaves the hold state (and re-enters the run state) when you enter a

RESUME or STEP command.

The Stop State

A program is in the stop state just after it completes execution, whether normally

(STOP) or abnormally (ABEND). A program enters the stop state when it calls the

STOP or ABEND system procedure, when another program stops it by calling the

STOP system procedure, or when you stop it using the TACL STOP command.

Normally a program is removed (that is, its code and data areas are freed for other

use) after it enters the stop state; however, a program is also in the stop state if:



The program was suspended by a breakpoint set on STOP/ABEND.



You examine a save file that was created from a program in the stop state.

Once a program is in the stop state, it cannot enter the run or hold state. Furthermore,

you cannot set breakpoints in it, modify its data, or resume its execution.

The Gone State

A program is in the gone state after you have stopped program execution and a

message has been sent to DMON. Processes only exist in the gone state for as long

as it takes DMON to compete the stopping process. Your program is not cleared from

the list until DMON returns a message. It is possible to catch a program you have

stopped if the program is still in the gone state.

Debug Events

A debug event is an action that causes Inspect to suspend the execution of a program.

Because save files are not executable, debug events do not apply to them.