Re: Does line actually execute in debug?

On 04-Sep-2015 07:15 -0600, Bill Howie wrote:

I have a question. I'm running a program in debug and trying to
figure out if a particular display format is being executed. I've set
a breakpoint on the line and the program does stop there. However the
actual execution of the line is dependent on an indicator like so:

99 EXFMT FORMATA

and the indicator is OFF at the time. I'm thinking that I'm correct
in saying that the debug processor stops before the execution of the
actual line. So technically if the indicator is off, this line is NOT
getting executed in any way. This program has several display formats
that are almost identical, and I check the open files directly after
this statement and it does not show this format being displayed.

Thoughts?

For both ILE and OPM source debug, a breakpoint set on that line of code will always stop; i.e. stops, irrespective the value of *IN99. As such, the onus is on the programmer to issue a request of the debugger to "EVAL *IN99" to determine if the EXFMT opcode will actually be performed :-(

With the OPM program however, the capability exists to get an IRP listing from which one can learn how to add the instruction-level breakpoint for the target of the CALLI FmtNam that effect activation of that format; typically the breakpoint name is the format name itself, thus: ADDBKP 'FmtNam'. If that breakpoint is hit, then the format should be activated, and if successfully, then the Record Format name will appear in the Open File listing, as seen from Display Job (DSPJOB OPTION(*OPNF) issued when at a breakpoint on the next statement. FWiW: To mimic the breakpoint of the source debugger, the instruction-level breakpoint would be set for the following MI that tests the value of the *IN99 [shown in the listing soon before the CALLI FmtNam]:
;CMPBLA(B) *IN99,*ON/NEQ(.xxx####)/*ZINDCK*/]