SQL0904N and SQL30081N while using DB2-Connect driver

Question

Scenario:
Application program : Java on Unix
Database : DB2 on Mainframe
Database driver : IBM's DB2 connect
Usage : A number of connections are taken by the program and are used as long as the program is alive
(Life time of the program is variable. It can be as long as many days -- in a sense the program acts like a daemon process that runs as long it is not stopped).
Scenario:
-To one of the table using a load utility, such as BMC, data is loaded
-Database goes to copy-pending status
-Database is started by using the following command : "START DATABASE(database name) SPACENAM(table space name) ACCESS(FORCE)"
Doubts:
1. What happens to the connections that the program has opened to the database?
2. Does the database relinquish all the resources (like the sockets it would have opened for the communication with the driver) held by it during restarting?
(at least before restarting, it is evident that no query on the table in question is possible. A typical SQL0904N, which is non-availability of resources, is thrown)
3. Can the above scenario cause a SQL30081N, which is resetting of connection by peer i.e. database in this case?

Answer 1

Yes, there is a high probability for such things, you may want to consider using a connection pool instead of opening 2 connections once at the start of the program and using them all for days.
Have a look at the following link to get an idea on how to implement a simple connection pool.
http://developer.java.sun.com/developer/onlineTraining/Programming/JDCBook/conpool.html