Resolution:
: In general we should always explicit define databases and tablespaces in DB2. This can be achieved by coding the database clause in the tablespace create statement and a tablespace clause in the table create statement.  If not coded, DB2 will implicitly create the tablespace in the default database -DSNDB04. Objects created in the DSNDB04 are hard to maintain and track. DB2 will create an implicit tablespace for new tables and set all tablespace parameters to the default values if the table create statement does not specify a tablespace clause. DB2 system default values are not always optimal to applications.
There are other reasons for the prompts. First, we want to give our users flexibility to name the objects according to the shop naming standards. When DB2 is required to generate names for objects, it is usually done in a randomize fashion which at times a nightmare for the DBA. Secondly, we allow our users to distribute objects according to their DBA strategy such as one table per tablespace.

For DB2: Why do we want to prompt for Database and Tablespace for each publishing and exception table?