[Info-vax] RMS internals?
Arne Vajhøj
arne at vajhoej.dk
Mon Aug 10 18:39:58 EDT 2009
Arne Vajhøj wrote:
> Bob Koehler wrote:
>> In article <howard-E4439F.13574308082009 at news.newsguy.com>, Howard S
>> Shubs <howard at shubs.net> writes:
>>> In article <0076b30e$0$7155$c3e8da3 at news.astraweb.com>,
>>> JF Mezei <jfmezei.spamnot at vaxination.ca> wrote:
>>>
>>>> If a VMS native file didn't have CRLF at the end, but Windows added
>>>> them, then it is likely the original VMS->Windows transfer mucked
>>>> the file.
>>> Original was Windows->VMS, as the file was created on Windows.
>>>
>> Sounds like it simply should have been transfered as a text file.
>> Are you trying to compensate for all the mistakes the user could
>> make? It isn't really an RMS function to fix those, you're kind of
>> rolling on your own.
>
> He is trying to solve the problem that most non-VMS files has valid
> text files with rec len > 32K, but VMS does not.
Give the size of data today and the need for moving files between
VMS and various non-VMS systems, then what about:
- changing the 32K limit to a 16M limit
- have VAR and VFC use 4 byte length both before and after data
- if there are any compatibility issues then keep the existing
RFM's and add BIGVAR, BIGVFC, BIGSTM, BIGSTMLF, BIGSTMCR and BIGFIX
?
Arne
More information about the Info-vax
mailing list