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

DATA3 COBBAT 53> rund xcs000ds0
TNS/E eInspect gdb Debugger [T1237 - 20-Dec-2011 16:43]
Copyright 2008 Free Software Foundation, Inc.
Copyright 2003-2012 Hewlett-Packard Development Company, L.P.
Native Inspect (based on GDB) is covered by the GNU General Public License.
Type "show copying" for conditions for changing and/or distributing copies.
Type "show warranty" for warranty/support information.
TWorking directory \PELICAN.$SYSTEM.SYSTEM.
Symbols read in for program loadfile \PELICAN.$DATA3.COBBAT.XCS000D0.
Added process (3,1012).
Switching process (3,1012) to eInspect from DMON
Breakpoint 1 at 0x70001600:0: file \PELICAN.$DATA3.COBBAT.SCS000D, line 5.
(eInspect 3,1012):next
318 perform initialization thru initialization-exit.
Current language: auto; currently COBOL
The next command advances execution from the beginning of the program unit to the first
executable statement.
Listing Source and Setting a Breakpoint at a Line Number
The following example shows how to list source and set a breakpoint at a line number by using
the list and break commands:
eInspect 3,1012):list
313
314 PROCEDURE DIVISION.
315
316 MAIN SECTION.
317 CALE-1-MAIN-PARA-1.
318 PERFORM INITIALIZATION THRU INITIALIZATION-EXIT.
319 PERFORM READ-SEQ1-TABLE THRU SEQ1-TABLE-EXIT 4 TIMES.
320 IF ERROR-DETECTED
321 PERFORM STOP-RUN.
322 PERFORM READ-SEQ2-TABLE UNTIL EOF OR ERROR-DETECTED.
(eInspect 3,1012):break 319
Breakpoint 2 at 0x70001bd0:0: file \PELICAN.$DATA3.COBBAT.SCS000D, line 319.
The break (or abbreviated b) command sets a breakpoint at line 319 to suspend execution upon
return from the first PERFORM invocation.
Stepping Execution
The following example shows how to step through execution by using the step and next
commands:
eInspect 3,1012):step
351 PERFORM OPEN-SEQ1-FILE.
(eInspect 3,1012):next
352 IF SEQ1-FILE-ER THEN
The preceding example demonstrates the following:
• The step command steps execution into PERFORM invocations and calls to program units.
• The next command steps execution over PERFORM invocations and calls to program units.
• PERFORM invocations are not listed on the call stack.
Displaying a Level 88 Condition Name
The following example shows how to display a level 88 condition name by using the print and
continue commands:
77 SEQ1-FLAG PIC 9.
88 SEQ1-FILE-ER VALUE 0.
Sample Native Inspect Session (COBOL Program) 41