1753448 Members
5840 Online
108794 Solutions
New Discussion юеВ

FTP

 
SOLVED
Go to solution
Graham Moss
Occasional Contributor

FTP

%TCPIP-E-FTP-OUTPUPROCF error processing output file SYS$ROOT:[SYSMGR]ASKV11.BCK
RMS-W-RTB 36864 byte recod to large for users buffer 426 connection closed: transfer aborted
5 REPLIES 5
Robert Gezelter
Honored Contributor
Solution

Re: FTP

Graham,

I would say that you will be able to transfer the file if you specify BINARY.

Which IP stack is being used? What version?

- Bob Gezelter, http://www.rlgsc.com
Bojan Nemec
Honored Contributor

Re: FTP

Graham,

The file has records larger than maximal RMS record size (32767 bytes).

Try to use binary transport.

Bojan
Bojan Nemec
Honored Contributor

Re: FTP

Graham,

One more thing, from the file name I assume that this is a backup save set. If this is right the save set will be corrupted (the file attributes, not the content). You can use a command procedure from the freeware CD to fix the problem. There is the link:
http://h71000.www7.hp.com/openvms/freeware/backup.html

Bojan
John Gillings
Honored Contributor

Re: FTP

re: broken savesets

>You can use a command procedure from the
>freeware CD to fix the problem

True, but from V8.3 there is a supported mechanism: BACKUP/REPAIR. It hasn't made it into the HELP yet, but is possibly in the release notes. Here's an example of use:

SS.SAV has the wrong file attributes.

$ backup/log ss.sav/save [.restore]
%BACKUP-F-NOTSAVESET, DISK_USER0:[OM_PROD]SS.SAV;1 is not a BACKUP save set
$ backup/log/repair ss.sav/save/select=nofiles [.restore]
%BACKUP-I-REPAIRED, saveset attributes changed to RFM=FIX, MRS=32256
%BACKUP-W-NOFILES, no files selected from DISK_USER0:[OM_PROD]SS.SAV;

Note that since BACKUP insists on an output directory, and you can't say "just fix it, don't restore any files", I've used /SELECT to avoid the restore.
A crucible of informative mistakes
Jon Pinkley
Honored Contributor

Re: FTP

VMS 8.3's backcup/repair also works with /list, so that's another way to avoid restoring files.

$ sho sys/nopro
OpenVMS V8.3 on node OMEGA 18-FEB-2008 02:23:54.75 Uptime 0 21:29:53
$ DW TEST*.BCK

Directory ROOT$USERS:[JON]

TEST.BCK;1 32/32 8-APR-2007 06:21:58.39
TESTFTPBIN.BCK;1 32/32 18-FEB-2008 02:15:13.83

Total of 2 files, 64/64 blocks.
$ SHO TIME
18-FEB-2008 02:15:42
$ BACKUP/LIST TESTFTPBIN.BCK/SAVE
Listing of save set(s)

%BACKUP-E-POSERROR, error positioning ROOT$USERS:[JON]TESTFTPBIN.BCK;1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERR, error reading ROOT$USERS:[JON]TESTFTPBIN.BCK;1
-BACKUP-E-BLOCKCRC, software block CRC error
%BACKUP-E-INVBLKSIZE, invalid block size in save set

End of save set

$ BACKUP/LIST TESTFTPBIN.BCK/SAVE/REPAIR
Listing of save set(s)

%BACKUP-I-REPAIRED, saveset attributes changed to RFM=FIX, MRS=16384
Save set: TEST.BCK
Written by: JON
UIC: [000002,000016]
Date: 8-APR-2007 06:21:58.34
Command: BACKUP TEST.TXT TEST.BCK/SAVE/BLOCK=16384/GROUP=0/COMMENT=Demo of dumping backup saveset
Operating system: OpenVMS Alpha version V7.2
BACKUP version: AXP72R001
CPU ID register: 80000000
Node name: _SIGMA::
Written on: _$4$DKA200:
Block size: 16384
Buffer count: 2040

[JON]TEST.TXT;3 1 24-SEP-2001 20:11
[JON]TEST.TXT;2 1 21-MAY-2001 10:38
[JON]TEST.TXT;1 1 5-MAY-1997 14:00

Total of 3 files, 3 blocks
End of save set

$
it depends