Subject: | |
From: | |
Reply To: | |
Date: | Fri, 6 Dec 1996 10:02:13 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Paul H. Christidis asks ...
>I did not ever think that I'll be asking a question about
>PowerHouse but we have this job that takes *forever*
>to finish and if I want it not to interfere with my backup,
>I better do something about it. I've determined
>that much of the delay occurs within the following code.
ACC PCTRD0 LINK (TRD0-PACCOUNT[1:4]) TO PJM0-PROJECT OF PCPJM0
<more code snipped>
>If I was writing this using a 3GL I would determine the
>range of fiscal periods and then for each period I'd
>read down the corresponding chain within PCTRD0,
>getting the corresponding master record, and applying
>the other selection criteria.
>
>Is there a way of doing something similar in QUIZ?
How would you determine the "range of fiscal periods" in
the 3GL and why can't you do that in Quiz? I would guess
that there's a table of periods or some algorithmic way
of generating a list of the ones of interest. Write these
fiscal period codes out to a subfile in one Quiz pass and
then use this subfile to drive the second pass.
The noble Stan suggests ...
>You can use the bundled B-Trees in IMAGE (now in beta
>test), or the free (?) Superdex basic B-Tree product, or
>the full Omnidex or Superdex product, and attach an
>index / B-Tree to TRD0-FISCALNO. Then, Powerhouse
>could make use of that index to optimize the search...
>if it doesn't already, you can lobby for Powerhouse
>to utilize B-Trees.
Nice idea Stan but it is obvious that you have never asked
Cognos for an enhancement :-)
John Pickering
JWP Systems Inc
Toronto
|
|
|