core_on_error

Restriction: The following applies to native code only.

Syntax:

>>-----set core_on_error=---.-0-.-----------><
                            +-1-+
                            +-2-+
                            +-3-+
                            +-129-+
                            +-130-+
                            +-131-+

Parameters:

0	The run-time system never produces a core file on any exception or run-time system error. This is the default behavior of the run-time system.
1	The run-time system produces a core file when any exception is received that would normally produce a core file on the host system; for example, a run-time system error COBRT114, and so on.
2	The run-time system produces a core file when any run-time system error occurs. After writing out the core file the process terminates immediately.
3	The run-time system produces a snap shot core file when any run-time system error occurs. After writing out the core file the process continues as normal; for example, to display an RTS error message.
129	Same as `core_on_error=1`, except no message box is displayed after the core file is created.
130	Same as `core_on_error=2`, except no message box is displayed after the core file is created.
131	Same as `core_on_error=3`, except no message box is displayed after the core file is created.

Properties:

Default:	0
IDE equivalent:	Use the Application.config file of the project - right-click the file in Solution Explorer and click Open, then select the Run-time Configuration tab.

Comments:

You can debug core files to determine the cause of the problem if you have the appropriate dictionary (.idy) files. When a core file is produced, using core_on_error=1 or core_on_error=2, the run-time system itself cannot clean up COBOL file buffers or free system resources. This could lead to data file corruption that might not have occurred if no core file was produced.
On Windows, if debug_on_error is also set, the setting of core_on_error is ignored.