HLASM Toolkit Feature Interactive Debug Facility User's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


STMTSTEP

HLASM Toolkit Feature Interactive Debug Facility User's Guide
GC26-8709-07

Performs a repeated single-step operation until the target program is executing a source statement other than the one it was executing when the command was issued.
Read syntax diagramSkip visual syntax diagram
>>-STMTstep----------------------------------------------------><

If a significant event occurs during the execution of the STMTSTEP command, execution stops at that point. Examples of significant events are cases where the target has branched outside its boundaries, completed, and returned control to IDF, breakpoints, watchpoints, and so on.

By default, if the repeated single-step operation reaches code that is within a code section for which IDF Language extract data was not loaded, IDF stops single-stepping. Turning off the STOPSTMT option or using the NOSTOPST option prevents IDF from stopping at these points.

No exit routine processing is performed during, or at the completion of, the STMTSTEP command. As with MRUN or MSTEP, if the STMTSTEP command is issued within a macro, use EXTRACT EVENT to determine what type of event completed the command.

If you issue the STMTSTEP command when the PSW is pointing to code that is within a code section for which IDF Language extract data was not loaded, IDF attempts to issue LANGUAGE LOAD for you. This only works if the name of the code section (CSECT) containing the code matches the file name of the extract file. If you do not want IDF to automatically issue these LANGUAGE LOAD commands you should set the AUTOLOAD option to OFF or the NOAUTOLD option to ON.

If the STOPNOP option is OFF or the NOSTOPNP option was used, then IDF does not stop on NOP and NOPR instructions that follow BAL, BALR, BAS, and BASR instructions.

z/VM
If you issue STMTSTEP from within an IDF macro, you should ensure that it is issued through the LPSW Fastpath addressing environment, which is the default environment established when the IDF macro is entered. Using this interface eliminates any SVC linkages between REXX and IDF, so that IDF can provide optimum flexibility in what the target program can itself execute under STMTSTEP. See the usage notes under MRUN for further details.

For more details see Controlling single-stepping your program.

Return codes

0
Operation successful
6
Command issued before IDF initialization is complete

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014