[HECnet] "illegal record size" in RSX?

[Jordi Guillaumes i Pons]

El 15/04/2015, a les 12:33, Johnny Billquist <bqt at softjar.se> va escriure:
> On 2015-04-15 06:58, Dave McGuire wrote:
>> On 04/14/2015 12:24 PM, Johnny Billquist wrote:
>>> On 2015-04-14 04:53, Dave McGuire wrote:
>>>> 
>>>>    Hey folks.  I'm moving some text files to an RSX system via DECnet
>>>> under Linux.  The files on the RSX system are not readable; I get
>>>> "illegal record size" when trying to type them.
>>>> 
>>>>    Has anyone hit this?  I assume there's a simple solution..
>>> 
>>> I have never had any luck at all transferring files from Linux to RSX.
>>> 
>>> That said, what do you see if you do a DSP <file> under RSX?
>> 
>>   Just got back from road trip #1, only have a moment, will get back to
>> this in the morning.  Here is the DSP output:
>> 
>> $ dsp forth.mac
>> 
>> DU:[10,1]FORTH.MAC;1
>>                         Size:    139./144.       Created: 15-APR-2015 00:54
>>                         Owner:   [001,010]       Revised: 15-APR-2015 00:55
>>                         File ID: (5601,10,0)     Expires: <none_specified>
>>   File protection:      System:RWED, Owner:RWED, Group:RWED, World:R
>>   File organization:    Sequential
>>   File attributes:      Allocation=144, Extend=0
>>   Record format:        Stream, maximum 255 bytes
>>   Record attributes:    Carriage return
> 
> Cool. So the first, and most obvious, problem, is that the file is indeed in stream format. So no ordinary RSX tool will touch it with a five foot pole...
> 
> Had you been pulling it from Linux to RSX, and initiated to transfer from the RSX side, you can tell NFT exactly what format you want for the file on the local side, when the remote side is a stream format file. Not sure Linux can do that if you do the transfer from the Linux side.

The dncopy command takes a -r switch where you can specify the remote format:

-r {fix|var|vfc|stm} Sets the record format for files copied to a VMS system. The default is stm. In fact the default is STREAMLF as this corresponds to the format of files on Unix systems and so is the least likely to result in file corruption. If you are sending a pure text file then var or vfc may be more appropriate for your application. fix may be useful for block-structures files and data files.

That is the verbatim text of the man page. It refers just to VMS and I'm not sure about the differences between the RSX and VMS versions of RMS, but it looks like it could fix the problem.



> My next suggestion is to read up on RMSCNV, on how to convert the file. I can never remember exactly how to use it, so I have to read every time I want to, but it can convert the file to another format for you.
> 
> Of course, it might also be that the actual file contents are "funny", but I think not.
> 
>    Johnny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20150415/2dbc69ea/attachment.html>