If you FCOPY with NOKSAM as an option you shoul see all the data...the first two bytes of deletes are set to low-values for a logical delete...so if there was any meaningful data in those positions...arghh..



-----Original Message-----
From: Brian Donaldson [mailto:[log in to unmask]]
Sent: Friday, December 18, 2009 5:51 PM
To: [log in to unmask]
Subject: [HP3000-L] KSAM Problem/Question

Can anyone tell me how I can read the records in a KSAM file that have been logically deleted?

I have tried the FPOINT/FREADC combo intrinsics. When I do an FPOINT on a record marked for deletion it returns a 170 error code. This is close to what I need. If I hit a 170 then I want to be able to FREAD/FREADC/FREADDIR the deleted record.


Unfortunately, after reviewing what is documented in the "Using KSAMXL"
manual page 6-3 ("Deleting A Record") it states "Although the data still occupies record space in the file, it is no longer possible to access the record through standard read operations."

Ok, so what "non-standard" read operations can I use to get the data from these logically deleted records?

TIA,

Brian Donaldson.

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

CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication.

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