× 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.



How do I tell what fields are indexed?

The 3600 is how many times it has run that query, not the time it has been
running.

I am now up to 7700 requeries.  It has been runnign for 2 hours.  WRKACTJOB
says it is now up to 46.5% CPU usage.

I got about 12000 more requeries to go.

The select statement I am using is:

SELECT symbol FROM RUGR80DAT.PMSP0200 WHERE policy0num = '<this is the value
that changes on each query>';

There are 148,543 records in this file.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Walden H. Leverich" <WaldenL@TechSoftInc.com>
To: <midrange-l@midrange.com>
Sent: Thursday, August 29, 2002 12:42 PM
Subject: RE: CPU usage for QZDASOINIT


> Depends on the select clause, the where clause, the number of rows in the
> table(s) and the available indexes. Also, is that 3600 3600ms? That's only
> 3.6 seconds, could be normal.
>
> -Walden
>
>
> ------------
> Walden H Leverich III
> President
> Tech Software
> (516) 627-3800 x11
> (208) 692-3308 eFax
> WaldenL@TechSoftInc.com
> http://www.TechSoftInc.com
>
> Quiquid latine dictum sit altum viditur.
> (Whatever is said in Latin seems profound.)
>
>
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Thursday, August 29, 2002 12:15
> To: midrange-l@midrange.com
> Subject: CPU usage for QZDASOINIT
>
>
> I am runnign that query now (it has currently requeried over 3600 time).
>
> Should it be runnign this hard for a simple select/where statement?
>
>       QZDASOINIT   QUSER       PJ     30.9                   RUN
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company http://www.rutgersinsurance.com
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com To subscribe,
unsubscribe,
> or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.