HP3000-L Archives

December 2009, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Craig Lalley <[log in to unmask]>
Reply To:
Craig Lalley <[log in to unmask]>
Date:
Fri, 18 Dec 2009 15:14:39 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
Brian,

I am just guessing here, but if you change the file code with MPEX, it may be possible to extract the data using FCOPY.  Just define your fields right....

-Craig



--- On Fri, 12/18/09, Brian Donaldson <[log in to unmask]> wrote:

From: Brian Donaldson <[log in to unmask]>
Subject: KSAM Problem/Question
To: [log in to unmask]
Date: Friday, December 18, 2009, 4:50 PM

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 *

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

ATOM RSS1 RSS2