You cannot have two 'logic sets' - one for output and another for input.
If output hits no I/O error then input hits no I/O error. Otherwise your
single assertion, applicable both to output and input, is flawed -
because it has two possible outcomes. It is 'along the lines of'
asserting that: if apples then 2 + 2 = 4, if oranges then 2 + 2 = 6.
Tom Marchant wrote:
On Wed, 3 Aug 2011 15:41:56 +0100, CM Poncelet wrote:
But I should get *no* I/O error at all on read if the DCB precedence
rules for output apply also to input, as is asserted (... not by me).
Of course you should get an I/O error on read if you specify a
blocksize that is inconsistent with the data on DASD. The same
as you would get if it was inconsistent with the data on tape or
any other medium.
I notice that you totally ignored my question about what happens
if the blocksize in the DCB is incompatible with the data on an
unlabeled tape. Here is another one. What if your program wants
to read 70 byte blocks from a card reader by specifying BLKSIZE=70
in the DCB in the program?
You would get an I/O error. Do you assert that the blocksize on
the card reader overrides the blocksize in your DCB?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
