Failing to FTP a large file from one NSK to another

[Ravikiran N]

I'm trying to FTP a large file (>90 MB) from one NSK machine to another. It is failing... The FTP response code from Source NSK is 550(Requested action not taken. File unavailable (e.g., file not found, no access)... and from that of Destination NSK is 552 (Requested file action aborted. Exceeded storage allocation (for current directory or dataset)... but it has a copied only a part of the file..

"fup info <filename>,detail" on both (source and Destination files) are as follows.
Source file :
TYPE U
FORMAT 1
CODE 800
EXT ( 84 PAGES, 84 PAGES )
ODDUNSTR
MAXEXTENTS 772
BUFFERSIZE 4096
OWNER 100,160
SECURITY (RWEP): NCCC
DATA MODIF: 6 Feb 2013, 7:46
CREATION DATE: 6 Feb 2013, 7:44
LAST OPEN: 6 Feb 2013, 7:46
FILE LABEL: 2386 (58.7% USED)
EOF: 91833138 (69.1% USED)
EXTENTS ALLOCATED: 534

Destination File (partially copied) :
TYPE U
FORMAT 1
EXT ( 4 PAGES, 28 PAGES )
ODDUNSTR
MAXEXTENTS 978
BUFFERSIZE 4096
OWNER 60,255
SECURITY (RWEP): NNNN
DATA MODIF: 7 Feb 2013, 17:06
CREATION DATE: 7 Feb 2013, 17:01
LAST OPEN: 7 Feb 2013, 17:01
FILE LABEL: 4062 (100.0% USED)
EOF: 54599680 (97.4% USED)
EXTENTS ALLOCATED: 953

Can you please help what I must be doing to ftp successfully...??
Thanks in advance.

[Keith Dick]

See the EXT(4,28) for the destination file? See the EXT(84,84) for the source file? Those extent sizes don't have to match, but the destination's extent sizes have to be large enough so that their size times MAXEXTENTS is large enough to hold the file.

There are parameters on NSK to NSK ftp that can set the destination extent sizes, but I don't have time right now to look them up. Check the manual and you'll find them.

[wbreidbach]

The correct manual is a bit funny to find, it is TCP/IP application...

As far as I remember the syntax is get <file1> <file2>,<filecode>,<primary extent>,<Sec. extent>,<maxextents>
The same is possible with put instead of get. This does not work with mput and mget. This way you can also transfer large files from another system to the NSK.
Please regard that there are no blanks allowed after the first comma, I am not sure if that is mentioned in the manual.

[Keith Dick]

Okay, I now had time to look it up. For an unstructured file, which yours is, GET and PUT both have a way to specify some of the file creation parameters. For PUT, the syntax is:

PUT local-file, remote-file, file-code, primary-extents, secondary-extents, maxextents

where all but the first parameter are optional. For GET the syntax is the same, except local-file and remote-file are interchanged.

So, for your case, something like:

PUT file,,,100,100,700

probably would work just fine.

However, looking more closely, I see in the INFO DETAIL for your destination file that it has stopped before quite reaching MAXEXTENTS. That could mean that the disk to which you are transferring the file is too full to take this additional file, or the disk's free space is so fragmented that there are no contiguous areas of the disk available to allocate another of your rather small extents for the file. You can check on the disk you are using for the destination with the commands:

DSAP $vol,SHORT
DSAP $vol,FREESPACE

DSAP is described in the "Guardian Disk and Tape Utilities Reference Manual", in case you want to see explanations of the output.

[Ravikiran N]

Thanks Keith and wbreidbach ... It really works..!! I actually created a file in NSK with primary, secondary and maxextents, before I FTPed the file.. but knowing ftp itself can do it for me is really simple and COOL...! Thanks for your help and time...!!

[Keith Dick]

You're welcome! We're happy to be able to help. Thanks for posting the follow-up to tell us how it turned out. Usually, we never hear whether what we suggest solves the problem.

[Bill Honaker]

The format for it is

put <source file> <space> <target file>

The <target file> parameter can contain the extra paremeters, but in
order for FTP clients to understand it, the entire file + parameters
can contain no spaces. The 'PUT' function in the server handles it.
For the Guardian FTP client, the same is true for the 'GET' target
file.

The manual also allows you to create a key-sequenced enscribe file as
part of the put operation, if I recall. Again, it's all described in
the manual.

For those of you that like to RTFM, Keith didn't say which manual
describes this, it's the 'TCP/IP Applicatoins and Utilities User
Guide'. The syntax of the commands (get, put, recv and send) is in
Chapter 7 (Communicating with the FTP server), under 'Transferring
Structured Files / Command Syntax. In the online version for
J-serise, it starts on page 97. Some examples and considerations
follow.

Big Data, indeed!

[Keith Dick]

Interesting -- the commands are also documented in the final section of chapter 6 of that same manual. primary and backup?

[Bill Honaker]

I think more like implemented in 2 places... although maybe in soruce
code shared between 2 executables.

Chapter 6 discusses the FTP client itself (which implements it on the
'get' and 'recv' commands) and Chapter 7 discussed the FTPSERV program
(which implements it for the 'put' and 'send' commands).

But that is an assumption.