Adam,

Yes there are a few RLD, ESC, etc records and they are LE 256 bytes. However
this does not affect the blocking of the text blocks. 

If, after writing a few small records a track has space remaining for a text
block up to the Max block size then it will use the max block size.

If the remaining space will fit a text block less than the Max block size,
but greater than the Min block size then it will write a short block in
order to fill the track.

Using this sort of smart blocking COPYMOD does not leave any unnecessary
empty space on the track.

Looking at a few random samples of modules in SYS1.LINKLIB (only 5), my
observation is that while there are only a few text blocks, they are usually
around 90% of the size of the module.

There have been numerous recommendations over the last 20 years to reblock
load libraries with SAS PROC PDSCOPY, and then later IEBCOPY with COPYMOD.
For me empirical evidence counts a lot. Choose a few of your well loved
loadlibs that have a 6KB blocksize and make a copy with COPYMOD using 32760
BLKSIZE. I'll bet The Sydney Harbour Bridge to a dollar that they the used
space is less than the source loadlib.

Ron

> 
> I agree and I believe I stated as much when I said that the only element
> in a load library that could take advantage of the blocksize was the TXT
> records.  However, my issue is that the significant number of ESD, RLD,
> etc records which are NOT blocked and therefore will continue to "waste"
> space on DASD regardless of the overall blocksize.  In addition, since
> most load module CSECTS are NOT 32K in size, they would also be written
> as short blocks.  As a consequence, my point is that all this discussion
> about optimum blocksizes for load libraries seems a bit over-stated.
> 
> Thanks for your response
> 
> Adam
> 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to