IIRC the originator of this thread stated that they had MPEX.

Do an %ERASE <ksamxlfilename> instead of doing a PURGE and BUILD. The
advantage of this method is that you would not have to modify the
DISC=<maxrecords> parameter in the build if you have done an %ALTFILE on it.

regards,

Robert W.Mills
Systems Development Manager
Windsong Services
(01689) 870622 x3005


Tracy Pierce <mailto:[log in to unmask]> wrote on 25 November 2003
18:06:

> OOPS, yes, you are correct.  instead of
> KSAMUTIL > ERASE,
> try
> PURGE FLATFILE
> FCOPY FROM=KSAMFILE;TO=FLATFILE;NEW
> PURGE KSAMFILE
> BUILD KSAMFILE;KSAMXL;REC=-96,8,F,ASCII;KSAMXL;KEY=(B,3,6);REUSE
> FCOPY FROM=FLATFILE;TO=KSAMFILE
>
>
>> -----Original Message-----
>> From: Jay Willis [mailto:[log in to unmask]]
>> Sent: Tuesday, November 25, 2003 9:41 AM
>> To: Tracy Pierce
>> Subject: Re: Removing deleted recs from KSAM/xl file
>>
>>
>> Tracy, I didn't think that ksamutil could be used on nm ksam files.
>> Is that correct?
>>
>> Tracy Pierce wrote:
>>
>>> reasonable KSAM maintenance includes, IMHO, an occasional
>>> reorganization, which will make the file run more efficiently by
>>> placing records in physical sequence.  this simple procedure
>>> doesn't care if your ksam is xl or classic, and doesn't address the
>>> issue of fullness...
>>>
>>>> FCOPY FROM=KSAMFILE;TO=FLATFILE;NEW
>>>> KSAMUTIL
>>>> ERASE KSAMFILE
>>>> EXIT
>>>> FCOPY FROM=FLATFILE;TO=KSAMFILE
>>
>
> * 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 *