The TIOT concern is related to the DVC value rather than the volume count value. The DVC total is counted whether or not the dataset extends to that count total. Whereas the volume count is recorded in the catalog as candidate volumes.
Terry Traylor charlesSCHWAB TIS Mainframe Storage Management Remedy Queue: tis-hs-mstg (602) 977-5154 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ted MacNEIL Sent: Tuesday, June 23, 2009 1:00 PM To: [email protected] Subject: Re: SMS Dataset Allocation Problem >It was not DB2 that had a problem. It was CICS and a few batch jobs. Okay. I stand/sit corrected. >I don't have a problem with multi-volume datasets at all, and in fact I >design SMS to allocate large datasets on as many volumes as possible. I didn't think you did have a problem. The issue is not multi-volume; it's number of volumes. >It was simply having so many candidate volumes for every dataset, 1 track or 1 pack, was excessive and we started having TIOT blow outs. Were you using the max TIOT size? I believe it's 64K. >I think we were using 20 for the unit count when the problem happened. While I've said we've used 59, usually I've used 20, but that's for Batch. For online, we left it up to apps/DBA, except for DB2, since it uses a different method. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
