[Info-vax] difference in files being copied by scp from Unix to VMS

JF Mezei jfmezei.spamnot at vaxination.ca
Tue Apr 21 17:33:57 EDT 2009


Sumir wrote:

> Meanwhile, the issue that was being faced has been averted by ignoring
> this particular file that was causing the problem, and hence i am not
> pursuing it further.

It would be nice for the community to put some closure on this though.

The fact that you have one file whose transfer is dubious would mean
that this problem could surface with any other file.

And finding the real problem would help others in this newsgroup should
they ever encouncter a similar problem.


In particular, I would be concerned about preservation of the end of
file marker for the last block.

DUMP/HEADER gives you some information about that:

>   VAX-11 RMS attributes
>         Record type:                      LF-terminated stream
>         File organization:                Sequential
>         Record attributes:                Implied carriage control
>         Record size:                      32767
>         Highest block:                    1464
>         End of file block:                1463
>         End of file byte:                 471     <=============
>         Bucket size:                      0


AKA, the last byte is byte 471 in block 1463, with bytes 472 to 512
being beyond end of file.

It is possible that your source file was like this, but when copied back
to VMS, the end of file byte was 512 (or is it 511 ?) which would add
some 30 bytes to the file, probably all nulls (which would explain your
extra line).




More information about the Info-vax mailing list