Your program's defined limits

IDF considers "your program" to be any location within the initial target phase, and any more phases that you have defined.

When the target is loaded, IDF determines its limits by examining the directory entry for the phase.
Extra modules are implicitly defined as the result of the triggering of a deferred breakpoint that was established with a DBREAK command.
Extra phases are explicitly defined with the IDF MODULE command:
- If the module is described in the phase load trace table, establish the module definition with a MODULE command.
- Define an explicit module origin and size with MODULE BASE and MODULE SIZE commands.
- You can establish an explicit module's CSECT structure with a LOAD SYMBOLS command (see LOAD).

The origin and size of the programs known to IDF are displayed in the Target Status window, when open.

Whenever possible, IDF notifies you if your program is preparing to branch to a location outside its defined limits. This is often useful in locating a "wild branch", for example to location zero.

If you have specified the TRACEALL option, IDF considers the defined limits of your program to begin at location zero and extend upward to the end of storage. Thus when you specify TRACEALL, you can trace through all of virtual memory.

Care should be taken if you attempt to trace through protected (read only) storage.