I am using the REUSE option when I build the KSAMXL files (OPTMBLK  also).

Before I issue the Cobol WRITE verb I am moving spaces to the  first two
bytes of the record.

Before I DELETE a record I move "**" to the first two bytes, do a  REWRITE
and then DELETE.

My question really is -- does the DELETE overwrite the "**" I just rewrote
to the record or not.

After all the deletes were done, I did an FCOPY with a subset="**" and it
returned zero records. So I am just very curious as to what is being put into
the first two bytes of the record.

I am using KSAMXL files as index files for data stored in sets of a
TurboIMAGE data base so
that I can do partial lookups to retrieve data.

In my original posting regarding this issue I had used BTREEMODE1=ON with a
mode4 DBFIND which didn't really give me what I wanted. Several people had
suggested using KSAMXL files as index files for retrieving data. As Omnidex and
Superdex were out of the question I opted for KSAMXL to create my own
indexed file system.

The initial load of the indexes was/is extremely slow,  updating indexes
inside the Vplus application is extremely slow but the  retrieval lookup part
seems to be fast enough compared to  the adding/updating/deleting portions......

Now I remember exactly why I have avoided KSAM all these  years.....


Brian.

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