Symptoms
This article is for a Windows operating system.
Whenever coredump files were generated, it was intended that they be written to a specified, target folder. However, the core files did not appear in the folder.
Here is an example:
The target folder is
C:\\microfocus\\stoproc_work\\coredump.
To configure this, these settings were used in a file named COBOPT.cfg: which was placed in a folder named C:\\ES\\cfg\\:
set core_on_error=131
set core_filename="C:\\microfocus\\stoproc_work\\coredump\\core_%d.%t_p%p_%f.dmp"
COBOPT.cfg was then placed at C:\\ES\\cfg\\
The value of the system environment variable COBCONFIG was then set to the path of the COBOPT.cfg file in the Configuration box of the Properties page of the JCL region:
COBCONFIG=C:\\ES\\cfg\\COBOPT.cfg
But the coredump files which were afterwards generated were found written to C:\\ES\\JCLTEST\\sys instead, which is the folder from which the JCL job is run, and not to the intended target folder C:\\microfocus\\stoproc_work\\coredump.
Diagnosis
There are two ways to address this on Windows platforms.
1. File paths in the COBOPT file should use forward slashes (/) instead of backslashes (\\)
set core_on_error=131
set core_filename="C:/microfocus/stoproc_work/coredump/core_%d.%t_p%p_%f.dmp"
2. This is also documented. To use the backslash in a path, you must precede it with the escape character, which is also a backslash; for example:
set core_on_error=131
set core_filename="c:\\\\temp\\\\core\\\\core.%p@%t_%d"
Solution
Once the changes were made to the COBOPT file, and the region restarted, once core files were generated the core files were written to the specified folder.
#MFDS
#EnterpriseDeveloper
