--------------------------------------<snip>----------------------------------
I'm afraid I disagree.
Because you are confusing the DSCB with the blocks written in the
dataset.
We are arguing semantics ...
----------------------------------<unsnip>------------------------------------
NOT HARDLY!
--------------------------------------<snip>----------------------------------
What it proves is not that the DCB on DASD was overwritten by the
one in the JCL, but that the DCB in the JCL was
incorrect/incompatible with the one on DASD.
Why would you get an I/O error if the DCB information on the DD
statement did not take precedence over that in the DSCB?
Why would a square peg not fit in a round hole if the round hole did
not take precedence over the square peg?
----------------------------------<unsnip>----------------------------------
If the attributes in the JCL are equally wrong, you'll still get that
I/O error.
Read up on the handling and formats of FIXED vs. VARIABLE vs. UNDEFINED
records. What you apperantly don't know CAN hurt you!
Rick
----------------------------------------------------------------------
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
