On Thu, 29 Jun 2006 20:23:21 -0500, Joel C. Ewing <[EMAIL PROTECTED]> wrote:
>Of course what makes the "AVGREC" parameter non intuitive is that it
>performs two functions, neither of which is to supply the average record
>length: It
>(1)changes interpretation of the "SPACE" parameter to allocate based on
>an AVeraGe RECord length and number of records as specified in the
>"SPACE" parameter and
"Changes the interpretation"? Does this mean that AVGREC=U has a
semantic distinct from omitting the AVGREC parameter? I.e. does
SPACE=(1000,100)
have an effect different from
SPACE=(1000,100),AVGREC=U
... ? If so, what? If not, have I overlooked some other case where
AVGREC=U has a nontrivial effect?
>(2)supplies a multiplier to be applied to the requested primary and
>secondary record counts (U=1, K= Ki (2**10), M= Mi (2*20) ).
>Those familiar with my postings already know my views on the abuse of
>"K" and "M" in this context!
>
And what ever was the rationale for this counterintuitve mickeymouse,
as opposed to the relatively intuitive alternative:
SPACE=(1000,100K)
Rather than
SPACE=(1000,100),AVGREC=K
and:
SPACE=(1000,100M)
Rather than
SPACE=(1000,100),AVGREC=M
... ?
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
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
