[Info-vax] CRTL and RMS vs SSIO

[Greg Tinkler]

<snip>
>>> The optional parameter might be a "lock type", and if not present,
>>> existing logic would be used, and if present, new code could be executed
>>> to process the new lock type.  Stuff a couple of quadwords into the
>>> resource name for the numeric range.  It would add one new piece of data
>>> to the DLM data structure(s). 

What would be useful is a name space for the lock e.g. RMS ...

Well there is the group id from UIC, and there is $set_resource_domain(), both can be useful but not a solution.

Having a name space that can be local machine or cluster wide could be very useful for some applications.  But that is a much longer term idea.

At present the resource name is limited to 31 char, ok in the 32 era but in 64 bit era and looking at GFS2 for peta byte moving into the exabyte and possibly the Zettabyta range, if VMS is to survive the next 40 years it needs to prepare.

First lets move onto X86_64.   Yes it would be good to have easier building of open source code, and the main issues as I understand it are

    file IO, moving to RMS will fix most if not all of that
    fork
        for fork/exec - spawn is fine, no modern systems a bit of CPU...
        for file access more of problem, but not often used
    directory and filenaming
        some work is in place for this

So the main issue is file IO, so change CRTL to use RMS.

gt