Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-221
Related Commands

If the REGISTERS clause is specified, Inspect does not display stack marker
information for subprocedures.

If the ARGUMENTS clause is specified, Inspect does not display parameter
names and values for subprocedures.

Inspect excludes subprocedure entries from the call history if symbol
information for the containing procedure does not exist.

If your program modified the S register, Inspect might not be able to display all
subprocedure entries in the call history. In this case, Inspect displays this
warning message:

For TNS/R native processes, Inspect displays the PC register in the normal Inspect
form as a scope name and offset. Inspect also displays the virtual frame pointer
(VFP) for that frame.

Inspect does not support debugging TNS/E native processes, but a TNS process
can be held at a TNS/E code location due, for example, to a memory access
breakpoint (MAB), a stop event, or an abend event.
The TRACE output on TNS/E systems will not show any TNS/E native frames. If a
TNS process is held at a TNS/E native address, the first line of the TRACE output
shows “Unknown TNS/E Address.”
To view both TNS and TNS/E frames, you must use Visual Inspect for TNS/E
systems.
Related Commands

LIST PROGRAM on page 6-137

SELECT PROGRAM on page 6-167
Examples
1. When using the REGISTERS clause, the TRACE command displays the L register,
ENV register, and space ID information in parentheses:
2. This example shows a TRACE command without clauses. When an entry in the
call history has only the notation SYSTEM CODE or SYSTEM LIB and an octal
** Inspect warning 185 ** Unable to trace subproc(s) due to 'S' register
modification
-TALOBJ-TRACE REGISTERS
Num Lang Location (Registers)
0 TAL #APPLY.#537(BNK) (L=%21023,RP=7,CCE,K,T,UC.0)
1 TAL #PARSER^HIGH.#240(MAIN) (L=%20730,T,UC.0)
2 TAL #MAIN.#168(MAIN) (L=%20547,T,UC.0)