Log files - Large number of empty log files with 8.0.0 runtime

0 Likes

Problem:

In Version 8.0.0 of the ACUCOBOL-GT runtime a log file is created each time the runtime is executed. This may result in a large number of empty log files in the format of

wrun32.process_id.log

Resolution:

The A_REMOVE_EMPTY_ERROR_FILE configuration variable can be used to remove these empty files.

Use this variable to prevent the accumulation of 0 byte files when using format specifiers such as "%p" (to include the process id) in the error file name.  When this variable is set to "1" (on, true, yes), the runtime deletes its error file if the runtime has never written to that file.

Note that on some operating systems, if your error file is shared by multiple processes (i.e., the file name does not include the process id or some other unique session information), setting A_REMOVE_EMPTY_ERROR_FILE to "1" may cause error messages to be lost.

For example, on UNIX if the error file is empty when one runtime exits, that runtime would delete the file. The file will remain deleted even if another runtime process subsequently writes a message to it.

The default value for this variable is "0" (off, false, no).

Old KB# 2663
Comment List
  • If you need to avoid these files to be created at all, you may redirect your runtime output in one of the following ways:

    1. create a real customized error file: "-e mytrace.log"

    2. on Windows systems, redirect all the information to the NULL device driver: "-e NUL"

    3. on Linux/UNIX boxes, redirect all the information to "-e /dev/null"

    Claudio Contardi
    Product Support Engineer, Senior
    Micro Focus

Related
Recommended