Open topic with navigation
WTSupported in traditional Synergy on Windows
WNSupported in Synergy .NET on Windows
USupported on UNIX
VSupported on OpenVMS
The DBG_SELECT environment variable turns on debugging for the Select class.
One of the following:
1 = Log optimization details.
2 = Log optimization details and add display of the Select opcode stream to the log.
When it’s enabled, two events cause Select debugging to output information: the creation of a Select object and the destruction of the AlphaEnumerator created from a Select object.
DBG_SELECT should never be used on multiple threads at the same time.
The environment. DBG_SELECT can be reset by the SETLOG routine, and the runtime interprets the new setting.
The logged content might look something like this:
[Select debugging at MAIN$APMAIN:93] Where(D(7:5).EQ.23) Optimized key: 2 Head key length: 5 Key range: 7:5 Tail exit condition: (7:5)EQ [Select debugging at MAIN$APMAIN:120] Where(Keynum(1).AND.A(1:2).EQ."90".AND.A(3:4).EQ."0097".AND.D(15:1).EQ.0.AND.D(21:1).EQ.1) Optimized key: 1 Head key length: 6 Key segment ranges: (1:2) (3:4) Tail exit conditions: (1:2)EQ (3:4)EQ [Select debugging at MAIN$APMAIN:120] Optimization effectiveness: 98% Total rows fetched: 13871 out of 487055 [Select debugging at MAIN$APMAIN:93] Optimization effectiveness: 100% Total rows fetched: 1 out of 11049
The first part of the output (the first two sections) shows each Select that was executed, the module and line number of that Select, the query string, whether the Select is optimized, which key will be used for optimization, the key length to be used plus the key range (which can be matched back to fields in the query string) when Head optimization is used, and the exit conditions when Tail optimization is used. (The exit condition reflects the field(s) and comparison operator(s) being used to continue enumerating. When the comparison result is false, the exit condition has been met, thus terminating any further I/O.)
In the example,
The second part of the output (the last two sections) shows the result any optimization may have had on the file itself, post operation. Optimization effectiveness shows a percentage of rows/records checked vs. the total number of rows/records in the file. The higher the percentage, the better the optimization. Optimization effectiveness is not supported on OpenVMS or to an OpenVMS server. The “Total rows fetched” (supported on all systems) shows the total number of rows/records that were read. OpenVMS users can figure out the effectiveness of the optimization using this number and the number of records in their file. Note that if an AlphaEnumerator wasn’t created or was never used, this information will be suppressed.