Charles Mills wrote: > 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.
Is this a (relatively) new problem? As far as I know, OS/360 didn't allow BLKSIZE=0 so this should not happen. At some time later, the ability to specify BLKSIZE=0 was added, along with this problem. Also, is it still possible to open a new data set and read the existing data on the tracks? I know OS/360 would do it, but security requirements have changed since then. (I do remember once having the link editor read some data into SYSLIN that my program never wrote, and then processing it as control cards.) -- glen ---------------------------------------------------------------------- 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
