Determines whether or not the profiler automatically generates a debug listing files for the ABL code being profiled. Requires access to source code, not intended for use in production systems. The default value is FALSE.
Data type: LOGICAL
Access: Readable/Writable
Applies to: PROFILER system handle
The profiler generates a debug listing file the first time that a procedure is executed. Therefore, if PROFILER:LISTINGS attribute is FALSE the first time a procedure is executed, then setting it to TRUE at a later time does not cause the profiler to generate the listing file for that procedure. In other words, the profiler only registers a module, using a unique identifier, the first time the module executes. The profiler only generates debug listing files for modules that are external procedures. If PROFILER:LISTINGS is FALSE when a procedure first executes, then the profiler never tries to generate a debug listing file for that procedure. It fails if the source files are not accessible. The source files that make up a procedure must be in the PROPATH in order for the profiler to generate a debug listing file. If the profiler cannot generate a debug listing file for a given procedure, then the profiler treats the procedure as though the PROFILER:LISTINGS setting was FALSE when that procedure first executes. The only way to get a Progress session to try again to generate the debug listing for a procedure is to disable and then re-enable the profiler by setting PROFILER:ENABLED to FALSE (which causes Progress to discard its profiler registry of procedures) and then set it to TRUE again.