×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Here's something for checking the engine - the rec ID 1000 has the info
in the field QQSMINT5 shown below -
OPTIMIZER_USE QQSMINT5 Which optimizer was used for the 1000 null =
monitor predates this option
* 0 = Does not apply for this statement
* 1 = SQE was used (SQL Query Engine)
* 2 = CQE was used (Classic Query Engine)
* 3 = CQE direct was used (statements like INSERT W/VALUES)
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzajq/t1000.htm
has the full SELECT statement for reading 1000 record - that's basically
a header record for each statement.
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzajq/lofdds.htm
lists a whole bunch of SELECT statements for various kinds of information.
There are a couple fields that are used to join all the formats for a
statement - QQJFLD (unique to a job) and QQUCNT (unique to a statement).
At least, that's what the docs describe.
HTH
Vern
On 3/4/2014 1:40 PM, rob@xxxxxxxxx wrote:
CQE ain't dead yet.
I think at 7.1 OPNQRYF, Query/400 and what not still ran on CQE. But I
was hoping to avoid that tangent and just monitor/check.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.