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

• Under the save Command (page 109), indicated that snapshot files of file code 130 are used
for offline debugging.
• Added the process entered debug event to Table 6 (page 31).
• Updated Document Organization (page 11) to include Appendix B.
• Changed all references to linespec to locspec. See Syntax of locspec (page 59), which
also indicates that locspec is sometimes referred to as linespec in files and documents
that are used by or related to Native Inspect.
Made miscellaneous formatting corrections to improve accuracy and consistency.
Document Organization
This document is organized as follows:
Table 1 Contents of the Native Inspect Manual
DescriptionChapter
Describes the basic principles of using Native Inspect to debug TNS/E
native processes and snapshot files.
Chapter 1: Introducing Native Inspect
Presents a sample session using Native Inspect to debug a TNS/E native
process.
Chapter 2: Using Native Inspect
Describes features and behavior of Native Inspect that are specific to the
debugging of COBOL programs.
Chapter 3: Using Native Inspect With
COBOL Programs
Lists Native Inspect commands in related groupings and gives syntax for
all the Native Inspect commands and command-line options.
Chapter 4: Native Inspect Command
Syntax
Describes the commands of the Tool Command Language (Tcl)Chapter 5: Using Tcl Scripting
Lists Debug and Inspect commands with their Native Inspect equivalents.Appendix A: Command Mapping With
Debug and Inspect
Shows the correspondence between WDB and Native Inspect commands.Appendix B: Redirected and Aliased WDB
Debugger Commands
Notation Conventions
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS
Uppercase letters indicate keywords and reserved words. Type these items exactly as shown.
Items not enclosed in brackets are required. For example:
MAXATTACH
Italic Letters
Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in
brackets are required. For example:
file-name
Computer Type
Computer type letters indicate:
• C and Open System Services (OSS) keywords, commands, and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For example:
Use the cextdecs.h header file.
• Text displayed by the computer. For example:
Document Organization 11