It saves it directly to the target file, as becomes obvious if primary
and secondary provide inadequate space and FTP transfer blows with a
partial file left, or if you transfer a multi-GB file you can actually
observe the target file increasing in extents during the transfer.
I think a more technically correct description based on empirical
evidence would be that the target file is allocated, and possibly
extended, based on the usual z/OS allocation rules for the primary and
secondary space values currently in effect for the FTP session, and at
the end of the transfer the RLSE attribute will be used to release any
allocated but unneeded space in a sequential target dataset. After a
failed FTP transfer that blew up with the target dataset at max extents,
the target dataset must be deleted before a retry with corrected SPACE
values, or the new attempt will just attempt to reuse the
inadequate-sized existing dataset and blow again.
Even if the FTP sender knew the size of the dataset and communicated
that to the receiver, the FTP receiver would have to assume any value
sent was informational only and not to be fully trusted.
Joel C. Ewing
On 05/25/2013 11:50 AM, Mike Schwab wrote:
Does it save it to memory or a temporary file until the transfer is complete?
On Sat, May 25, 2013 at 11:28 AM, Charles Mills <[email protected]> wrote:
Interesting. Thanks. That's from the Configuration Reference. I was looking at
IP Commands, which is subtly different:
For allocating sequential data sets this is the maximum amount of space
that is allocated for the primary extent. If a smaller amount of space is
needed to hold the data being transferred, only the amount actually
needed to hold the data is allocated.
1. Not really apropos of my question, but why are the two different?
2. What you quoted is very plausible. The quote above does not sound technically accurate. How
would the FTP server "know" the "actually needed" amount of space to allocate?
3. The quote above explains why I did not find anything searching on "release"
(but would have found your quote).
I did confirm that space is released. I did QUOTE SITE PRI=100 TR and uploaded
a 6K file. After the transfer completed, the dataset was 1 track.
So that answers my question. More precise documentation would certainly be a
help. Thanks again.
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Norbert Friemel
Sent: Saturday, May 25, 2013 8:55 AM
To: [email protected]
Subject: Re: Really? No FTP SITE RLSE?
On Sat, 25 May 2013 08:44:08 -0700, Charles Mills wrote:
Am I missing something? Is it really true that z/OS FTP server SITE
does not support space release (RLSE)?
I sure don't see it in the documentation but it seems odd, with all the
options that are there.
Did I miss something? Is there a way to get the FTP server to release
excess dataset space?
Charles
Space is always released (for seq. datasets).
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1b4b1/18.102
"For allocating sequential data sets, amount is the maximum quantity that is
allocated for the primary extent. If a lesser amount is needed to hold the data being
transferred, the unused amount is released after the transfer is complete."
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
