Try OpenEdge Now
skip to main content
Debugging and Troubleshooting
Troubleshooting Resources : Log Entry Types Detail : File access logging

File access logging

Specifying the file access (FileID) log entry type turns on logging of file access operations (opening and closing files) and file access error messages that do not include the filename. Information is logged at logging level 2 (Basic) and higher.
Some file access error messages do not include the filename in the message; they show only the file ID, which can make it difficult to diagnose the problem. When you turn on file access logging and such an error occurs, OpenEdge includes both the file’s name and ID in the log entry. File access logging is also useful in identifying file access errors or inefficiencies in your code (for example, you might be opening or closing a file unnecessarily, setting PROPATH or PATH incorrectly, or exceeding some file limit).
Log entries generated for this type contain the tag FILEID. An example of FileID logging messages (with headers suppressed) is shown:

FILEID Open d:\temp\program.r ID=30
FILEID Close d:\temp\program.r ID=30
FILEID Open d:\temp\srt01934 ID=31
FILEID Error 219 for file d:\temp\srt01934 ID=31
You can also turn on this logging at run time, by using the LOG-MANAGER system handle. For example, you can include the following line in the ABL code:

You can turn off this logging in the ABL application by resetting the attribute. For example: