> I can't think of a reason to need separate ACS code for them. I beg to differ, Tom. Once I set up DASD allocation rules for the SAS databases in my shop, especially the large ones that tended to grow to multi-volume, the number of past-midnight phone calls from Operations "Job XXX failed, not enough disk space" went down to next to zero.
The OP may have a real valid reason for trying to control SAS databases. Allocation of large datasets, including SAS databases, is much more likely to succeed if directed to a disk pool with large amounts of free disk space per volume. The general user pool may be too cluttered up for large dataset allocations to succeed all the time. Regards, Ulrich -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Kelman, Tom Sent: Monday, August 20, 2007 11:09 AM To: [email protected] Subject: Re: Identifying SASDBs in SMS ACS routines Bob brings up a good point here Jennifer. Is there some reason you want ACS code specifically for SAS DBs? There was a time when SAS did not go multi-volume nicely, but since SAS v7 it has followed the rules in that regard. I can't think of a reason to need separate ACS code for them. Tom Kelman Commerce Bank of Kansas City (816) 760-7632 ---------------------------------------------------------------------- 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
