Agreed. The answer to my question "how do you specify RLSE?" is "you can't; it's implicit." (And the answer to the corollary question "how do you specify 'NORLSE'?" is "you can't specify that either.")
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Joel C. Ewing Sent: Saturday, May 25, 2013 1:08 PM To: [email protected] Subject: Re: Really? No FTP SITE RLSE? 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
