Generating Profiling Data for a 4GL Application
For Versions 9.0A and higher
There are two ways to generate profiling data for an application
run:
generically using:
Using profiler configaration file as follow:
On WINDOWS:
prowin32 -profile proconfigfile.txt
-pf startup.pf -p test.p ...
On UNIX:
_progres -profile proconfigfile.txt -pf
startup.pf -p test.p ...
When -profile is specified, PROFILER:ENABLED will be initialized
to True.
The configuration file
proconfigfile.txt may contain any or none of the following options.
A ‘#’ is the comment marker. Everything to the end
of the line after a ‘#’ is disregarded.
Note that all of the options here are described
in terms of
the PROFILER system handle:
- COVERAGE
# Initialize PROFILER:COVERAGE to True
- DESCRIPTION
description # Initializes PROFILER:DESCRIPTION to description (if more than one
token, it should be a quoted string).
- FILENAME
filename # Initialize PROFILER:FILE-NAME to filename
LISTINGS
[directory] # Initialize PROFILER:LISTINGS to True; if directory is specified,
initialize PROFILER:DIRECTORY to directory.
- PROFILING
[yes | no] # Initialize the PROFILER:PROFILING to yes or no.
If yes or no is not specified, the default is yes.
If –PROFILING is not specified, the default is also yes.
- TRACE-FILTER
patterns # Initialize PROFILER:TRACE-FILTER to patterns (if more than one token,
it should be a quoted string).
- TRACING
entries # Initialize PROFILER:TRACING to entries. This
should be a quoted string.
Any error in the profile-configuration-file will result
in Profiling being not enabled.