It's a good question. I don't think there's really any easy way to do this. The problem you have is that ISMF doesn't check when adding or removing volumes from storage groups whether the volume is empty, is initialized, or even if it exists. It has to do this since the configuration that's being updated may not even exist on this system but might be being built, for example, for another system altogether.
Unfortunately, this means that if you remove a volume from a storage group, then activate the configuration, and then try to allocate a new, non-SMS dataset on that volume, you get an allocation error (diag code 04160055 - trying to allocate a non-SMS dataset on a volume in which the VTOC/VTOCIX indicate the volume is SMS-managed), although any existing data on the volume is accessible. Other errors are possible if you add volumes to a storage group and don't ICKDSF INIT them as SMS-managed, etc. There aren't any exits to ISMF that might help with this, although you could try customizing the ISMF CLISTs and load modules. This might be a subject for a SHARE requirement. Steve Pryor Senior Software Developer DTS Software, Inc. 770-922-2444 x162 [EMAIL PROTECTED] ---------------------------------------------------------------------- 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
