Created On: 06 September 2010
Problem:
Enterprise Server is not honouring the location of the core dump file that I placed in the core_filename variable.
Resolution:
If you include a location (path name) in the core dump file name variable, core_filename, using backslashes as part of the location (e.g. "C:\\my_dumps\\etc."), then the location specification will be ignored, and the dumps will be written to the first path in your JES Program Path concatenation.
It appears that the general processing of strings for Enterprise Server RTS tunable values gives a special meaning to the "\\" (backslash) character and ends up simply stripping them out. A workaround, therefore, is to use a Unix style path delimiter "/" (forward slash) in the core_filename tunable setting, as this will work on Windows (e.g. "C:/my_dumps/etc.").
This variable is specified in the text file pointed to by the COBCONFIG environment variable, like this:
SET CORE_ON_ERROR=131
SET CORE_FILENAME="C:/Incidents/2472838/core.%p@%t_%d"
It appears that the general processing of strings for Enterprise Server RTS tunable values gives a special meaning to the "\\" (backslash) character and ends up simply stripping them out. A workaround, therefore, is to use a Unix style path delimiter "/" (forward slash) in the core_filename tunable setting, as this will work on Windows (e.g. "C:/my_dumps/etc.").
This variable is specified in the text file pointed to by the COBCONFIG environment variable, like this:
SET CORE_ON_ERROR=131
SET CORE_FILENAME="C:/Incidents/2472838/core.%p@%t_%d"
Incident #2472838
Old KB# 31683
#EnterpriseDeveloper
#MFDS
