
salespoint. Also, setting the verbosity to 5 for all salespoints can create performance issues, as the EZ struggles to
write all that text to a disk file.
With filtered logging, it is possible to leave the VerbosityLevel setting in the EZ.INI at zero and still get a
verbosity 5 logging from selected salespoints, operators or even for specific calls. Here is the content from a sample
_LogDirectives.txt file:
<StandardLogFilter>left(.cCurrentSalespoint, 3) = "RES"</StandardLogFilter>
<CapturePerformance>YES</CapturePerformance>
<PerformanceLogFilter>not empty(.cCurrentSalespoint)</ PerformanceLogFilter>
<TruncatePerformanceLogLines>NO</TruncatePerformanceLogLines>
The four tags that are supported are:
This must be a valid Visual FoxPro expression that
evaluates to True or False. If this expression
evaluates to True, then the verbosity is set to 5
for the duration of that call.
There are several variables available for you to
reference. They start with a dot and need to be
used that way in the filter expressions. Here are
the variables with some sample expressions:
The six character operator
log-in name
The six character salespoint
name
The function being called
in the EZ
Sample expressions:
.cSalespoint = "MLRN03"
.cOperator = "BART"
.cFunction = "SQLPASSTHROUGH"
LEFT(.cSalespoint, 4) = "MLRN"
INLIST(.cOperator , "BART",
When this setting is set to YES, the EZ will create
the Performance log file. The name will include
the date – like
SaleEZ_Performance_20110121_Log.
txt. This is described in more detail below,
under Performance Logging
Similar to the StandardLogFilter tag, it must be a
valid FoxPro expression. When that expression
evaluates to TRUE, then an entry will be made
into the Performance log.
<TruncatePerformanceLogLines>
When set to YES, Log lines in the Performance log
will not include the full call for APPENDRECS
Comentarios a estos manuales