Tablespace / Index Creation using ars.cfg DB2 Parameters

[hmed]

We used to use the arsutbl cobol exit in 9.5 to create tablespaces and index tables based on our shop standards.  After moving to 10.5 we are using the ars.cfg DB2 ARSMVS Parameters to accomplish most of the functionality.

One of the things that we'd like to do is direct the tablespace and index tables to their own separate storage groups. 
Another thing that we would like to do is add a 'with restrict on drop' condition to the create table DDL.

How have other shops accomplished this? 
or... Does anybody have any suggestions on how these things can be done?

Thanks.  Ed W.

[scottnys]

We work with our Storage unit and use SMS rules.  Naming conventions of the Database conforms to the SMS rules.  Same is true with OAM DBs for Retentions.  Other than the initial ARS* Tables, All the Index Data Tables are "automatically" controlled. 

[Ed_Arnold]

For applgrp data tables, CMOD will specify the STOGROUP associated with the database for its CREATE TABLESPACE/INDEX.  If there’s a database associated with a given applgrp, it will use the STOGROUP for THAT database when creating the tablespaces/indexes for that applgrp.  Create a STOGROUP CMOD, GRANT USE, ALTER DATABASE db STOGROUP CMOD. 
 
ARSUTBL can put a “restrict on drop” in the DDL.  Perhaps  “restrict on drop” is going to cause problems?   Not something we've ever used or thought out. 

I'm curious as to what the business reason for using "restrict on drop" is.

Ed