Powerhouse feature with quad integers

[Deskin, Bob]

Regarding the index being INTEGER, you could always redefine it as a
character item for the purposes of the index. Of course you might have to
worry about bit order. Also, you'll have to specify NOGENERIC just in case
the last few bits make an at sign (@).

Bob Deskin              
PowerHouse Web Product Manager and Senior Product Advisor
Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


-----Original Message-----
From: Chris Sharman [mailto:Chris.Sharman@ccagroup.co.uk]
Sent: February 3, 2000 9:51 AM
To: Bob.Deskin@cognos.com
Cc: Barnaby.Cole@cognos.com; Chris.Sharman@ccagroup.co.uk;
powerh-l@lists.swau.edu
Subject: RE: Powerhouse feature with quad integers



(ref 1019430)

>2) I don't believe that the calculation is safe for all values.

Well, no, neither do I. But will it get the most significant 48+ bits right,
and reliably give zeroes in the rest ? That's what I need assurance on.
I'm hoping it's safe for numbers with only 48 significant bits (+ exponent),
but I'm not absolutely 110% certain, and we're already wearing enough egg
here:
for some reason the layman is amused by calculation errors from computers
...
those laymen that aren't demanding blood are anyway ...

I can see that the subtractive calculation is unreliable. I think that the
multiplicative should be safe, given that it's only 48 significant bits for
the
largest invoice-numbers (only about 38 at present).
Any number gurus care to comment ?

>3) I don't believe you can calculate an index value in this way. However,
>there's nothing stopping you from splitting it and using segments of an
>index or subitems. PowerHouse gives you the flexibility in retrieval
>specification. You can use the generalized linkage in QUIZ/QTP like this:
>
>ACCESS record1 LINK item1, item2, item3 ... VIAINDEX index
>  TO segment1, segment2, segment3 ... OF record2
>
>This should give you the flexibility of matching up calculated segment
>values. It does require that the index you're linking to has the same
>segment breakdown, but that should not be a problem.

But segmented keys are only supported for string keys aren't they, not
numeric?
I don't see how I'd do that.

Thanks,
Chris
_______________________________________________________________________
Chris.Sharman@CCAgroup.co.uk		http://www.ccastat.demon.co.uk/
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.