-----------------------<snip>-------------------------
1. It IS on SMS DASD. This is not a theoretical problem -- it happens in
real life. The problem is ***not*** with DS1LSTAR or EOF markers. The
problem is that the BLKSIZE in the DSCB is zero, QSAM picks that up,
puts it in a CCW, falls on its face, and diagnoses the situation with a
message that it takes a CCW expert to decode -- rather than diagnosing
an easily diagnosable situation with a simple explanation.
2. It's a very specific situation. The dataset is not allocated by a
user. It's allocated by a cooperating (semi-cooperative?) automated
process -- so Gil's point is correct, but does not apply in my specific
situation.
----------------------<unsnip>------------------------
IIRC, from the beginning of this thread, the LRECL was specified as 0.
Why in blazes don't you specify a legal LRECL for a FB dataset, plus
DSORG=PS? Then the BLKSIZE won't BE set to zero by SDB and the whole
problem goes away?
----------------------------------------------------------------------
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
