Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!AC.UK!SYSMGR%UK.AC.KCL.PH.IPG
From: SYSMGR%UK.AC.KCL.PH.IPG@AC.UK.UUCP
Newsgroups: mod.computers.vax
Subject: Segmented keys from FORTRAN
Message-ID: <8702231236.AA09150@ucbvax.Berkeley.EDU>
Date: Mon, 23-Feb-87 07:37:26 EST
Article-I.D.: ucbvax.8702231236.AA09150
Posted: Mon Feb 23 07:37:26 1987
Date-Received: Wed, 25-Feb-87 06:37:52 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: info-vax@sri-kl.arpa

I have successfully manipulated a file with segmented keys using FORTRAN.
Provided the file exists, you do not need to tell FORTRAN about the
segmentation, RMS finds this out for itself and copes. I would hope that
other HLLs behave similarly.
 
I created it using EDIT/FDL to set up the correct structure, followed by
CONVERT/FAST to load a file of sequential data. The segmented key approach
saved having to re-structure many Mbytes of data, efficiency wasn't
important (not that I noticed any degradation compared to an ordinary
indexed file). Incidentally not only were 3 keys segmented, but they overlapped
as well!
 
Documentation in the RMS manual is sparse, but all I found that I needed
to know was that the facility was available --- everything else worked.
 
 
Nigel Arnot (Dept. Physics, Kings college, Univ. of London;  U.K)
 
Bitnet/NetNorth/Earn:   sysmgr@ipg.ph.kcl.ac.uk (or) sysmgr%kcl.ph.vaxa@ac.uk
       Arpa         :   sysmgr%ipg.ph.kcl.ac.uk@ucl-cs.arpa