At 10:24 -0500 on 05/26/2013, Paul Gilmartin wrote about Re: Really?
No FTP SITE RLSE?:
On Sat, 25 May 2013 22:23:17 -0400, Robert A. Rosenberg wrote:
Way 2 is that your requested space is overridden by the computed
needed space and only that amount is allocated. That is then used to
accept the transfer. To do this the amount of space used for the
source is used to tell how much space to allocate for the target.
That takes into account the LRECL/BLKSIZE of both files as well as
the DEVTYPEs of the devices and the size of the source file.
All this is presuming that both source and target are legacy data
sets. And even there, reblocking can introduce inaccuracies.
Particularly significant if the source was allocated with BLKSIZE=32720
and originally written with BSAM using track balancing, for example.
-- gil
I attempted to cover this situation to some extent in my description.
The only way to accurately handle the situation for a FB file would
be to get an accurate record count by doing a preliminary scan of the
source. Otherwise you would just need to look at the number of tracks
used in the source and assume that all tracks have BLKSIZE blocks
(and thus the number of records are equal to the product of the
number of records per block times the number of blocks per track
times the number of tracks). This under estimates the number of
records if the last block on each track is short (to allow extra
records to fit on the track).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
