Maybe it is INSTANCE(s) I'm looking for. Can there be more than one
instance on the same server ?? And how do I create these ??

In a perfect world, you should like to have a separate server for
production and test systems. If that is not currently feasible, then
I would recommend creating a separate instance of DB2 for your test
databases.  It can be a single server and single software installation.
A separate instance is a separate running copy of the DBMS server, listening
on a separate port for connections, and managing its own databases.

This will allow you to stop and start the test and production systems
separately, and also to test changes in the database manager configuration
on the test system isolated from your production databases.  It will also
allow you to enforce different security policies in your test and production
systems-- for instance, where I work, all of our DBAs have SYSADM authority
on test instances, but only the DBAs with primary responsibility for DB2
administration have SYSADM on the production instances.  You also can
do things like give DBAs SYSCTRL on production systems instead of SYSADM
if the data is sensitive and should be kept confidential from system
administrators.

Hope that helps,

Joseph

Given answers in other notes, build an instance for each db.  Each
instance can be started and stopped independently of each other.
When you create the db, I'd create one (prod or test, doesn't matter)
and define it completely.
Once defined and before you populate, backup the db and restore it as
new in the other instance.
You will have to redirect each tablespace container definition as they
cannot coexist in the same defined targets.
HTH,  Pierre.

Thanks a lot - I'm getting closer.

Now I succeded making a new INSTANCE. But I can't create a new
database. It says DB2START not performed. Stop/start makes no
difference.

How do I Start/Stop these instances seperately?? Using the manual on
DB2START mentions node's ?? But what I expected is Instances!

/Jep