The ESCOFF verb disables program escape traps, while the ESCON verb
re-enables them. While ESCOFF is in effect, all SETESC statements execute
normally. However, the SETESC branch will not be taken, should an escape
occur. Because console mode access is the simplest method for locating
bugs, this is helpful in locating a bug in an application that has already
implemented escape traps.
ESCOFF remains in effect until an ESCON is executed. No other verb (START, RESET, etc.) cancels an ESCOFF. Because PRO/5 always remembers SETESC statements, any escape trap will be properly set when an ESCON is executed, though a SETESC may have been executed while ESCOFF was in effect.