John, >Would SMS for lpar-P get confused if SMS for lpar-D was allocating a file on those dasd at the same time she was? Does SMS from one lpar need to know what SMS from the other lpar is doing?
I don't know if this has changed but SMS tracks space allocations (tables it somewhere) for use in determining whether the volume can accommodate the allocation without exceeding the space threshold. If you have a separate SMS configuration for each lpar, you will mess up these statistics and the only way to correct the error(s) is to drop the volume(s) from the SMS configuration, active it, redefine the volume in the configuration and activate it. You do not have to be in a SYSPLEX to use a common SMS configuration. You can have up to 32 systems. SMS predates SYSPLEX. I have one SMS configuration for my production systems and a separate SMS configuration for the sysprog sandbox. I limit any SMS pool to one of the configurations and most of the support dasd is outside of SMS to avoid corrupting the volume statistics in SMS. 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
