[Info-vax] OpenVMS on X86-64, whats next

[Dave Froble]

On 7/20/2022 7:32 PM, Johnny Billquist wrote:
> On 2022-07-20 07:59, Greg Tinkler wrote:
>> I had previously posted about not using SSIO, rather fixing CRTL.  I then
>> wrote from sample 32bit code as a proof of concept.  This code has now been
>> altered use RAB64, i.e. cc/point=64.  Well that was a whole heap of fun, and
>> underlined for me as to the importance of OpenVMS becoming a PROPER 64 bit
>> OS.  It also made be realize that call RMS a record manage system is
>> incorrect, it has 3 parts (read the doco) file handling, record management,
>> RAW IO.  A much better name to avoid confusing the lx/Ux group is VMSIO.
>
> Admittedly, my RSX knowledge is going to shine through here again. But actual
> file handling is, I believe, part of the Files-11 ACP (and XQP). Not RMS. Now, I
> don't know if you can do things totally dodging RMS under VMS. But in RSX, you
> certainly can. The QIO interface to deal with files is rather different than
> what RMS gives you, but this is where actual file processing takes place. RMS
> depends on that layer, and are just operating on files as such. The actual
> handling of the file is done outside of the file (things like managing
> protection, access, allocating blocks to files, or free them, and so on...).

Long ago when implementing a database product, we used the RMS routine(s) for 
parsing a filespec. Hey it was already there, why re-invent it?  But that was 
all of the usage of RMS.  The file I/O was totally QIO.  Another thing that was 
available is the DLM, and of course we used that, even though we already had 
some locking software based sort of on RSTS locking.


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486