Causes the debugger to scan the call stack and attempt to set a
    breakpoint on every established frame-based handler whenever the
    program being debugged has an exception. The debugger does not
    discriminate between standard RTL handlers and user-established
    handlers.

    On Alpha and Integrity servers, most RTLs establish a jacket
    RTL handler on a frame where the user program has defined a
    handler. The RTL jacket performs setup, argument manipulation,
    and dispatch to the user written handlers. When processing the
    exception, the debugger can only set the breakpoint on the RTL
    jacket handler, because that is the address on the call stack. If
    the debugger suspends program execution in a jacket RTL handler,
    you can usually reach the user-defined handler by finding the
    dispatch point(s) via some number of STEP/CALLs followed by a
    STEP/INTO.

    See the OpenVMS Calling Standard for more information on frame-
    based handlers.

    If the jacket RTL handler is part of an installed shared image
    such as ALPHA LIBOTS, the debugger cannot set a breakpoint on it
    (no private user mode write access). In this case, activate ALL
    RTLs as private images via logical names. For example:

      $DEFINE LIBOTS SYS$SHARE:LIBOTS.EXE;

    Note that the trailing semicolon (;) is required. Note also that
    all (or none) of your shared installed RTLs should be activated
    privately. Use SHOW IMAGE/FULL data to realize the list of images
    with system space code sections and then define logicals for all
    of them and rerun your debug session.