On Thu, 19 Sep 2013 15:01:58 +0200, nitz-...@gmx.net wrote: >> IIRC the (pseudo) eof is only written for SMS managed PS datasets, so a PO >> dataset could well be allocated over old data which will then be readable. >> Can you force the problem PO dataset to anther place by making sure the >> space for the 66000 dataset is still in use when the problem PO dataset is >> allocated. > >We're dealing with SMS-managed data sets here. I used this job > ... By surmise, I'll add another piece to the puzzle. Since the specified directory blocks is 0, allocation does not format a directory, and does not write the terminating EOF. Later, allocation sees that DSORG=PO, and does not write an EOF (which would be real, not pseudo) at the beginning lest it destroy the directory had it created one. Subsequent behavior depends on the residual content of the first allocated track.
Is the EOF written only if the data set is SMS-managed, or is this one of those thingys that requires only that the SMS STC/ASID be active at the time of creation? I say the EOF (had it been written) must be real, not pseudo, to protect programs that carelessly read without checking DS1LSTAR. This is not to be regarded as a security feature; it's too easy to read beyond EOF with EXCP or BSAM. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
