application folks have a data set that is allocated as: //DD1 DD DSN=app.data, // DCB=(LRECL=567,BLKSIZE=27783,RECFM=FB), // SPACE=(CYL,(1,10)),DISP=(,catlg)
later on, they use this data set as output to a syncgener step as: //COPY1.SYSUT2 DD DSN=app.data, // DCB=(LRECL=567,BLKSIZE=27783,RECFM=FB), // SPACE=(CYL,(300,50)),DISP=OLD,UNIT=(SYSDA,59) aside from the obvious things you may comment on, when this data set is accessed in the second step, allocation wise, isn't the only thing that gets a temporary bump the secondary allocation from 10 to 50 ? The primary will still be 1, yes ? They had an SB37-04 last night on a volume that only had 280 free cylinders, I think they had already hit 16 extents on the data set not that the primary couldn't be filled. No way to check since they deleted it and reallocated it at (400,100) ---------------------------------------------------------------------- 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
