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


Causing a break-in event (TSO)

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

A "break-in event" is an event that causes IDF to break in to the target program's execution and regain control, even though a breakpoint was not reached. For example, you might need to cause a break-in event if your program is in an infinite loop that does not contain a breakpoint.

When IDF initially invokes your program, it establishes an ESTAE exit. If your program has not established its own ESTAE exit (which overrides the IDF ESTAE), IDF should receive control when the ATTENTION key is pressed.

When a break-in event is recognized, IDF displays the IDF user interface screen and issues a message acknowledging the event. You can then continue your debugging session.
Notes:
  1. This requires SVC97 to operate normally.
  2. There is no break-in event if the LUNAME option is specified when IDF is invoked.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014