> For example, for a Physical Sequential file with > UNIT=(esoteric,6) > SPACE=(CYL,(1000,500)) > and 3390 geometry (3339 cylinders) > > we have observed DADSM pass over volumes with > plenty of space and instead allocate 3 volumes > that had preexisting files with 3000 cylinders. > > In other words, the most cylinders available > would be 3339-3000 = 339 yet with a secondary > of 500 cylinders DADSM would still pick the packs > with less than 339 and the file would end > up running out of space. > Brent, Do you have any product that is attempting to prevent x37 abends? You should always be using the secondary amount when you extend to a new volume. Your candidate list is built by taking the volumes in the esoteric that are mounted storage. The list is then passed to SRM along with a list of volumes that you already have allocated. SRM ranks the candidate list by putting the ones you already have to the bottom and the others by device delay where device delay is the sum of iosq time, pend time and disconnect time. The only real difference here between SMS and non-SMS is that SMS knows how much space is on a volume and will put only volumes with enough freespace to meet your allocation request without going over the space utilization threshold for the storage group on the primary candidate list. Regards, John
---------------------------------------------------------------------- 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
