Re: CPU usage for QZDASOINIT

Thanks for the help.

You rock.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Buck Calabro" <Buck.Calabro@commsoft.net>
To: <midrange-l@midrange.com>
Sent: Thursday, August 29, 2002 3:32 PM
Subject: RE: CPU usage for QZDASOINIT


> >The following list contains the suggested primary and
> >secondary key fields:
> >POLICY0NUM.
> >
> >So does it say this because policy0num is NOT indexed?
>
> POLICY0NUM is not in any index.
>
> >It can't be a primary key because it
> >does not have unique values.
>
> If you use DDS to create logical files, don't specify UNIQUE.  If you use
> SQL, CREATE INDEX RUGR80DAT/index ON RUGR80DAT/PMSP0200 (POLICY0NUM).
> That's not unique, but that's OK.
>
> >RUGR80DAT/RUGL020002 17, RUGR80DAT/RUGL020001 11,
> >RUGR80DAT/PMSP02L0 17, RUGR80DAT/PMSL0207 11,
> >But what are all thsoe files?
>
> As the optimiser tries to figure out the best way to satisfy the query, it
> looks at existing logical files to see if they would help.  None of those
> logicals have an index on POLICY0NUM, so the optimiser discards them and
> tells you why.
>   --buck
> _______________________________________________
> 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.