core_on_error

Restriction: The following applies to native code only.

Syntax:

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

0	The run-time system never produces a core file on any signal 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 system signal is received that would normally produce a core file on the host system; for example, SIGBUS and SIGSEGV (which would usually produce a run-time system error 114). After writing out the core file the process terminates immediately. Warning: When this value is set, operating system security may prevent a core dump file from being created; refer to Preparing for a Core Dump for instructions on how to ensure that a core dump file is created.
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. Warning: When this value is set, operating system security may prevent a core dump file from being created; refer to Preparing for a Core Dump for instructions on how to ensure that a core dump file is created.
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.

Default:	0
IDE equivalent:	None

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.

Restriction:

The core_on_error=3 functionality has the following restrictions on some operating systems:

On HP-UX, it is only supported on version 11.31 or later, where the gcore utility is supported.
On Linux, it is only supported if gdb (GNU debugger) is installed and the creation of valid 32-bit core dumps is supported.
On AIX, it is only supported when the "fullcore" kernel tunable is set. To enable "fullcore" support, run the following command as root: chdev -l sys0 -a fullcore='true'.