Date: 05/09/2021 12:28 PM
Subject: [EXTERNAL] Re: Database monitor (V7R2) 5005 entries:
meaning and QQ1000L
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Many thanks for your input Vern and Timothy.
Timothy, I can't use the nice ACS screens, unfortunately, because the
of the Query being run is not logged anywhere in the Database Monitor,so I
am having to use various bits of locally meaningful SQL to match monitoreasily
output against specific Queries. I don't suppose there is any way of
identifying the SQL for a specific panel (like you can in thePerformance
navigation screens in iNav)? That would be really useful.processing
(I have given up on the 5005 entries for now!)
Anyway I've now got a bit further.
Am I right Vern (I think this was your point?) that Query Sort
has no specific information logged in the DBMON output, and iseffectively
entirely unpredictable in its results?predictable.
This is absolutely what I am finding - everything else seems
In particular, if there are no sort fields at all and the optimisationThe
matches across SQE and CQE, then the output seems to match every time.
only exception to this relates to the handling of Report Breaks wherethere
are no sort fields (it is clear that SQL GROUP type processing is notbeing
used, either in SQE or in CQE).identifying
Finally, another question (sorry): what is the 'proper' way of
SQE vs CQE in the DBMON output? I am usingQQSMINTF/Plan_Iteration_Number,
treating null as CQE and everything else as SQE - this seems to work,but am
I missing a more formal/accurate method? Not all the record typesinclude
the query options library name, or I'd use that.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.