Inspect Manual
Using Inspect on a TNS/E System
Inspect Manual—429164-006
18-4
Debugger Selection on TNS/E Systems
Debugger Selection on TNS/E Systems
Debugger selection is determined by the debugging attributes of a process. The rules
for debugger selection differ according to system type (TNS/R or TNS/E). The rules
followed on a TNS/R system are different from the rules on a TNS/E system. In
addition, the TNS/R system debugger is Debug, but the system debugger on TNS/E
systems is Native Inspect.
When a debugger is invoked on a TNS/E system, the system software selects the
debugger according to the rules of precedence described in Table 18-1.
Considerations About Debugger Selection
Visual Inspect can only be selected when you have already established a matching
Visual Inspect client connection.
If the Inspect subsystem is not able to find a suitable debugger (either Visual
Inspect or Inspect), the debugger selected is the TNS/E system debugger, Native
Inspect, which is not part of the Inspect subsystem.
Native Inspect has extremely limited support for debugging TNS processes.
Therefore, Inspect is the preferred debugger for TNS processes even if INSPECT
is set to OFF.
COBOL programs on a TNS/E system must be debugged using either:
Inspect for TNS COBOL85 programs
Visual Inspect for either TNS COBOL85 or TNS/E COBOL programs
Table 18-1
illustrates that on a TNS/E system, Inspect is invoked as the chosen
debugger to debug a TNS emulated process in only two cases -- when the INSPECT
attribute is ON and Visual Inspect is not available, or when INSPECT is OFF (also see
Figure 18-2 on page 18-6).
For background information about the debugging attributes of a process, see The
Debugging Attributes of a Process on page 4-4.
Table 18-1. Debugger Precedence on TNS/E Systems
Process Type INSPECT Attribute Debugger Precedence
TNS INSPECT ON Visual Inspect, Inspect, Native Inspect
TNS INSPECT OFF Inspect, Native Inspect
TNS/E Native INSPECT ON Visual Inspect, Native Inspect
TNS/E Native INSPECT OFF Native Inspect