HP3000-L Archives

July 2000, Week 2

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:
Bill Cadier <[log in to unmask]>
Reply To:
Bill Cadier <[log in to unmask]>
Date:
Thu, 13 Jul 2000 14:36:13 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
Rollie wrote:

>
>Wait... there's got to be more to it than this. Its possible they've
>created a "logical" delete marker that's part of the data record. In this
>case you can do...
>
>fcopy from=.... ;subset="your delete marker",column #, exclude
>
>people used to do this because (among other things) they did not know how
>to read "deleted" records from a ksam/V file, as in
>
>fcopy from=...;nouserlabels;subset=#%377,%377#,,exclude
>
>My question now is: How do you resurrect "deleted" records in ksam/XL ?
>

AFAIK there is no way to extract _just the data_ from a KSAM/XL file and
this is due to the way we block the records internally. I think the Response
Center had some engineering notes on how to do this but I do not think
they produced just the data. I hope I'm not wrong here, it's been awhile!

Many years ago I wrote a program called KSDELEXT that will extract just
the data from deleted records in a KSAM/XL file and write them to another
flat file. It comes with a "README" file loaded with details and the usual
caveats.

There has actually not been alot of request for this and its original intent
was
to be built into "KSCHKIX" the Ksam/XL file checker program and I just never
did that.

Presently the only way to get this program, should you want it, is from the
Response Center. However, if there is some general need for this program I
can see about getting it onto Jazz.

Hope this helps.

Bill Cadier
HP/Commercial Systems Div.

ATOM RSS1 RSS2