[Info-vax] Copying savesets over DECnet

[Stephen Hoffman]

On 2020-08-26 15:15:06 +0000, Antonio Carlini said:

> On Wednesday, 26 August 2020 15:57:05 UTC+1, Stephen Hoffman  wrote:
>> 
>> I presume there's a reason why IP isn't being tried here, so... poke at 
>> SET RMS/NET. Maybe SET RMS /NET=100. Maybe HELP SET RMS.
>> 
> 
> It didn't occur to me that IP was an option. I don't recall ever doing 
> a VMS-to-VMS copy using IP from the DCL command line. But I'm willing 
> to try if you can remind me of the syntax.

FTP, if TCP/IP Services has been installed and configured, and the FTP 
client and server are enabled on the systems involved.
OpenVMS VAX V5.5-2 can have FTP.
VAX with TCP/IP Services lacks sftp, scp, and ssh.
So FTP and telnet it is. Security? What security?
zip "-V" was suggested, but you'll need a current zip (zip 3.0, unzip 
6.0) as the earlier versions cannot deal with files larger than ~4 GB.
Process Software process.com has a current zip and unzip in their 
OpenVMS resources area.
I wouldn't bother with extra compression within zip "-9", etc, as I've 
seldom found that to save appreciably more storage, and the transfer 
timing difference for a network file transfer is negligible.
And using zip means more storage on your hardware to buffer the 
intermediate file.
BACKUP savesets corrupted by FTP can usually be resolved by the 
Freeware RESET_BACKUP_SAVESET_FILE_ATTRIBUTES.COM or some such tool, in 
the 000TOOLS area of the Freeware.
Though that reset tool won't work here, because your OpenVMS VAX 
version is too old.
You'll have to rummage a different tool to reset the saveset file attributes.
Or scrounge a recent zip that'll run that far back, and that'll protect 
the saveset file attributes.
Or find a SCSI dongle or somebody with a newer DLT, and have them load 
the contents.
I dislike old versions.
OpenVMS is more work than it should be, and old versions further 
increase the effort.

-- 
Pure Personal Opinion | HoffmanLabs LLC