I keep forgetting about that one bit called Dataset Key Type in the Data Set
Control Block area of the root file.  Regardless of the data type, if that
bit is on, IMAGE hashes the key.

The trick is to flip the proper bit in the root file and then load up the
dataset hoping that your favorite database utility looks at that bit and
doesn't just trigger on the item type.  You must also remember to verify the
bit is set properly if/when you change the database or set at some point in
time.  I suspect that is what Alfredo is alluding to and I am sure he has a
(?) solution for that.

Well done, Alfredo.  Thanks for the memory.  Now, can you help me figure out
how to keep my .224 bullet supersonic at 1000 yards in cold weather before
the next competition?:-)  

Denys

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of F. Alfredo Rego
Sent: Thursday, January 04, 2007 8:51 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Full synonym chain (really ugly)

At 11:50 AM -0600 1/2/07, Denys Beauchemin wrote:

...
>So, big deal you say.  How do I fix this?  Well, changing the data type is
>the solution. 

Beware of anything that includes the phrase "the solution" ;-)

I am sure Denys meant "a solution".


>IMAGE does not care what you put in the various fields.  So,
>if you wanted to use hashing, where IMAGE uses all 64 bits for address
>calculation, you could simply redefine the data item as an X8 and let
>whatever tool you use to do the trick recalculate all the record based on
>hashing instead of just modulo.  Your programs would not know the
difference
>as long as they are not interrogating IMAGE with DBINFO to find out what
>type of data is ostensibly in the field.  In other words, let's say you are
>using BASIC; if you do a DBGET of the item using a REAL buffer to receive
>the data, it will go right in there and be usable by the program as is.
>
>This will defeat Query and other similar programs to which you cannot apply
>a dictionary of some type.  These programs will interrogate IMAGE and get
>told the data is X and they will expect that and be surprised.
>
>On further thought, I would probably change it from R4 to P16.  That will
>still hash.

The key [did I really write this?] to the solution is the word "hash".

Do you have Adager, Ray?

If you do, I have "a" good (i.e., an "a" as in "Adager") solution for you
that will NOT "defeat Query" (and will not defeat ANY standard accessor,
in fact).

Had you attended the recent GHRUG meeting in Houston, you would have
enjoyed my mini-dissertation on the crucial difference between "the" and
"a".
We missed you there.


Your "A" friend,

  _______________
 |               |
 |               |
 |            r  |  Alfredo                  http://www.adager.com

 |          e    |                            
 |        g      |  F. Alfredo Rego                   
 |      a        |  Manager, R & D Labs           
 |    d          |  Adager Corporation
 |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
 |               |
 |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *