On Mon, 18 May 2009 11:03:05 -0500, Paul Gilmartin <[email protected]> wrote:
>On Mon, 18 May 2009 17:48:44 +0200, Gilbert Saint-Flour wrote: > >>On Friday 15 May 2009 04:47, Clark Morris wrote: >> >>> .... I submitted a SHARE requirement back in the 1990's to have >>> a compile option that the default be BLOCK 0. .... >> >>Great idea, and I wish IBM added that option to the compiler. >>What a stupid necessity that programmers have to code BLOCK CONTAINS 0 ! >> >What happens if the programmer pre-allocates the data set? It's >still a stupid necessity, but it might help in dealing with >situations where recompilation is impractical. I am unsure as to the issue. BLOCK CONTAINS 0 works fine with pre-allocated datasets. And in fact, as I mentioned before, with a pre-allocated dataset it appears to not even matter what BLOCK CONTAINS specifies, or if it is even present. The file can still be written to. It seems to take the blocking from the dataset label. Perhaps I have misunderstood your concern? Frank ---------------------------------------------------------------------- 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
