Subject: | |
From: | |
Reply To: | |
Date: | Fri, 18 Aug 2000 13:58:43 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Tracy writes:
> In the MPE 5.5 TurboImage manual posted at
> http://docs.hp.com/cgi-bin/doc3k/B3039190010.17091/41 under DBINFO mode 209,
> it says that "each element is a 32-bit Word" which is not only incorrect in
> and of itself, but conflicts with other specs presented. The elements noted
> are really 16-bit Words, which is actually redundant but nice for clarity (a
> Word is elsewhere defined to be 2 bytes or 16 bits)..
>
> My question here is "To what entity at HP should I present this (or more
> relevant current-release fixes?), and how?".
HP ESC. They should route the bug to the documentation people.
Here's the current DBINFO 209 layout, as I understand it:
:cseq dbinfo
CSEQ [2.9] - LPS Toolbox [A.07a] (c) 1995 Lund Performance Solutions
This product is licensed to: Allegro Consultants, Inc.
Procedure dbinfo (
base : anyvar int16 ; {R26, align 16}
qualifier : anyvar record ; {R25, @32 -> 128, align 16}
mode : anyvar int16 ; {R24, align 16}
status : anyvar record ; {R23, @32 -> 160, align 16}
buffer : anyvar record ) {SP-$0034, @32 -> 35200, align 16}
...
{ 209 32 Jumbo information }
{ 32 16-bit words (shown with #1 as first index): }
{ 1 1 if index (B-Tree) attached }
{ 0 if no index (B-Tree) attached }
{ }
{ 2 1 if the attached index (B-Tree) is dama }
{ 0 otherwise (including if no-index) }
{ }
{ 3 1 if attached B-Tree was opened ok }
{ 2 if attached B-Tree failed to open }
{ 0 if no attached B-Tree }
{ }
{ 4 upper 16 bits of last B-Tree intrnl err }
{ 5 lower 16 bits of last B-Tree intrnl err }
{ 6..31 reserved }
{ 301 3n+1 #paths:1, (dataset#:1, search_item#:1, }
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
|
|
|