Several runtime options affect debugging in Language Environment. The TEST runtime option, for example, can be used with a debugging tool to specify the level of control the debugging tool has when the routine being initialized is started. The ABPERC, CHECK, DEPTHCONDLMT, DYNDUMP, ERRCOUNT, HEAPCHK, INTERRUPT, TERMTHDACT, TRACE, TRAP, and USRHDLR options affect condition handling. The ABTERMENC option affects how an application ends (that is, with an abend or with a return code and reason code) when an unhandled condition of severity 2 or greater occurs. Table 1 lists the Language Environment runtime options that affect debugging. For a more detailed discussion of these runtime options, see z/OS Language Environment Programming Reference .
| Description | |
|---|---|
| ABPERC | Specifies that the indicated abend code bypasses the condition handler. |
| ABTERMENC | Specifies enclave termination behavior for an enclave ending with an unhandled condition of severity 2 or greater. |
| CEEDUMP | Specifies options to control the processing of the Language Environment dump report. |
| CHECK | Determines if runtime checking is performed. |
| NODEBUG | Controls the COBOL USE FOR DEBUGGING declarative. |
| DEPTHCONDLMT | Specifies the limit for the depth of nested synchronous conditions in user-written condition handlers. (Asynchronous signals do not affect DEPTHCONDLMT.) |
| DYNDUMP | Provides a way to obtain IPCS-readable dumps of user applications that would ordinarily be lost due to the absence of a SYSMDUMP, SYSUDUMP, or SYSABEND DD statement |
| ERRCOUNT | Specifies the number of synchronous conditions of severity 2 or greater tolerated. (Asynchronous signals do not affect ERRCOUNT.) |
| HEAPCHK | Determines if additional heap check tests are performed. |
 HEAPZONES |
Activates user heap overlay toleration and checking. |
| INFOMSGFILTER | Filters user specified informational
messages from the MSGFILE. Note: Affects only those messages generated
by Language Environment and
any routine that calls CEEMSG. Other routines that write to the message
file, such as CEEMOUT, do not have a filtering option.
|
| INTERRUPT | Causes Language Environment to recognize attention interrupts. |
| MSGFILE | Specifies the ddname of the Language Environment message file. |
| MSGQ | Specifies the number of instance specific information (ISI) blocks that are allocated on a per-thread basis for use by an application. Located within the Language Environment condition token is an ISI token. The ISI contains information used by the condition manager to identify and react to a specific occurrence of a condition. |
| PROFILE | Controls the use of an optional profiler tool, which collects performance data for the running application. When this option is in effect, the profiler is loaded and the debugger cannot be loaded. If the TEST option is in effect when PROFILE is specified, the profiler tool will not be loaded. |
| RPTOPTS | Produces a report that shows the runtime options in effect; see Determining runtime options in effect . |
| RPTSTG | Generates a report of the storage used by an enclave; see Controlling storage allocation. |
| STORAGE | Specifies that Language Environment initializes all heap and stack storage to a user-specified value. |
| TERMTHDACT | Controls response when an enclave terminates due to an unhandled condition of severity 2 or greater. |
| TEST | Specifies the conditions under which a debugging tool assumes control. |
| TRACE | Activates Language Environment runtime library tracing and controls the size of the trace table, the type of trace, and whether the trace table should be dumped unconditionally upon termination of the application. |
| TRAP | When TRAP is set to ON, Language Environment traps routine interrupts and abends, and optionally prints trace information or invokes a user-written condition handling routine. With TRAP set to OFF, the operating system handles all interrupts and abends. You should generally set TRAP to ON, or your runtime results can be unpredictable. |
| USRHDLR | Specifies the behavior of two user-written condition handlers. The first handler specified will be registered at stack frame 0. The second handler specified will be registered before any other user-written condition handlers, once the handler is enabled by a condition. |
| XUFLOW | Specifies if an exponent underflow causes a routine interrupt. |