Native Inspect Manual (H06.04+)

Syntax of Native Inspect Commands

Native Inspect Manual—528122-005

4-72

step command, stepi command

Advances program execution by one source statement or by a specified number of

statements. For COBOL programs, execution advances to the next verb. Execution

steps “in” any function calls or PERFORM statements that are executed within the step

range.

If a function call is made within the stepping range, the call is followed and execution

suspended after the function’s prolog code is executed. Execution transparently steps

though any run-time environment functions, such as import stubs, for which stack

unwind information is not present.

The stepi command advances program execution similarly, but the units of stepping is

instructions. Also, function prolog code is not automatically executed by the stepi

command. You will have to step through the prolog code before the stack frame is

properly initialized.

The step and stepi commands are similar to the next command, nexti command.

Aliases: s for step command, si for stepi command

count

is a positive integer, the number of statements (step command), or instructions

(stepi command) that you want to advance.

For both step and stepi, if the program calls a privileged function but the set mode

command has not been used to enable privileged debugging, execution steps over the

function.

Example

See the example of stepping execution for the next command, nexti command.

switch command

Transfers the current process to either Visual Inspect or Inspect, as appropriate:

•

Transfers a TNS/E native process to Visual Inspect

You must be running a Visual Inspect client (on Windows) connected to the

NonStop system using the same user ID as the TNS/E native process.

•

Transfers a TNS process to Inspect

{ step | stepi } [ count ]

switch