Native Inspect Manual (H06.13+, J06.03+)

/G/SYSTEM/SYSTEM gtacl -cpu 2 -p einspect
(eInspect 2,-2):
After Native Inspect initializes, you must enter the attach command so that you can examine a
TNS/E native process. See the attach Command (page 66). The process must be running under
your user ID (or you must be either the super ID or the group manager of the user), and must be
running in the same CPU as the instance of Native Inspect you started.
To examine a snapshot file after starting Native Inspect, use the snapshot command. See the
snapshot Command (page 117).
For more information about starting Native Inspect and about accessing source and loading
symbols, in addition to an extended example of a Native Inspect session, see Chapter 2: Using
Native Inspect.
Reading the Custom File
NOTE: Native Inspect does not execute commands in the custom file if you specify the “no custom”
(nocstm) option.
When Native Inspect initializes, it reads the contents of its custom file, named EINSCSTM, located
in your logon default $vol.subvol on the TNS/E host. This file can contain Native Inspect
commands that you want to take effect during initialization. For example, you might establish your
typical debugging environment by including a number of set commands. See the set Command
(environment) (page 110).
Only a limited subset of Native Inspect commands are allowed to be specified in the EINSCSTM
file. These include (but are not limited to) the following commands: set, show, priv, define,
document. Process control and execution control commands are not allowed to be specified in
the EINSCSTM file.
Using the Command Prompt to Identify the Current Process
After Native Inspect initializes, it displays its command prompt. The Native Inspect prompt contains
the name eInspect, the CPU number, and the process identification number (pin) of the current
process or debugging target.
For example, the following prompt indicates that process 0,301 is the current process:
(eInspect 0,301):
The current process is the process to which all debugging commands apply and the process for
which Native Inspect waits for events.
When Native Inspect has no current process, the command prompt includes the CPU number and
“-2” as the process number. For example:
(eInspect 3,-2):
Native Inspect Command Abbreviations and Command Alternates
You can truncate Native Inspect command names provided that the abbreviation is not ambiguous.
Ambiguous abbreviations are allowed. For example, the letter s is defined as an abbreviation for
the step command even though many other command names begin with s. Use the help command
to display command information. See help Command, help Option (page 83).
Some commands have alternate forms such as the disassemble command, which has the alternate
form da. Where applicable, these alternate forms are identified in the headings of each command,
such as: disassemble (da) Command (page 75).
Process Debugging Using Native Inspect 23