HP3000-L Archives

November 2004, Week 1

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:
Re: KSAMXL Delete Question
From:
Cathlene Mc Rae <[log in to unmask]>
Reply To:
Cathlene Mc Rae <[log in to unmask]>
Date:
Wed, 3 Nov 2004 12:58:03 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines) 
Ksam Btrees

All KSAM files use B-trees and that's the real penalty of a load
or update, balancing those trees.

XM Overhead

Fcopying to a new KSAM 64 file avoids the XM overhead.  So to avoid
XM overhead the customer must do the following;

File myfile;REC=,,,,KSAM 64;,,etc
Fcopy from=KSAM/XL;to=(*myfile);NEW

Building a file and then copying to it does not avoid the XM overhead.
The following would have XM overhead.

Build myfile;REC=,,,;KSAM 64,,,,etc
Fcopy from=KSAM/XL;to=(myfile)

Use OPTMBLK (better performance?)  All this option would really do is
more efficiently use disk space

Image btree option:
>SET database name [/maintword] BTREEMODE1=ON

C.09.11 uses ksamxl for the btree indices, c.10 uses ksam64 (available on
c.75.00).

Best Regards
Cathlene Mc Rae

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

ATOM RSS1 RSS2