Actually with the image b-trees you can use DBFIND on master datasets and
do chained reads.  It's a great way to get a sorted list of the key values,
and it's fast.






Tom Renz <[log in to unmask]> on 08/04/99 12:52:11 PM

Please respond to Tom Renz <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:  Re: Master dataset synonym chains




Gary,

Please note: You cannot use a DBFIND call on a master data set!!

You can do a Mode-8 DBGET to return the Primary entry for the specified
key.  It may or may not be the same record as the key you specified but is
always the Primary record.  Then in status array elements 5 & 6 you will
receive the number of entries in the synonym chain.  From this you should
be able to do a DBGET Mode-5 to read down the chain.  I learned about this
a long time ago (a few years).

Another alternative is that you could do a serial read of the data set and
check status elements 5 & 6 and when you find a number greater than zero,
this is a primary record and you can write it to a temp file and if needed
use this temp file as input to some other processes that give you a
percentage of primaries vs secondaries or what ever you want to do.

These are a couple off the top methods.  I'm sure the other members of the
list can shed more light on the subject if there are contributed or other
utilities available to accomplish your desired goals.

Enjoy.

Tom Renz

>>> "Paveza, Gary" <[log in to unmask]> 08/04/99 12:59PM >>>

I am currently working on a project to analyze a database.  I am looking
for
a method of returning the synonym chains from a master dataset, so they may
be transversed, either forward or backward.  From looking at DBFIND and
DBGET, the status area only returns the chain information, not synonym.
Yet,
under the section of the documentation that shows internal structure of
media records, it clearly shows that synonym chain information is also
there.

Is there a way to access this information using HP intrinsics?

-------------------------------
Gary L. Paveza, Jr.
Technical Support Specialist
All opinions are mine and not those of my employer