Tuning tips for JDBC?

We have a lot of JDBC connections to the iSeries due to people testing various 
parts of a large Java application. Sometimes there are hundreds of active 
QSQSRVR and QZDASOINIT jobs. This can be quite a load on the system. Response 
time increases dramatically, however WRKSYSSTS usually doesn't indicate that 
CPU or DB utilitization is extremely high. I sometimes see a lot of paging in 
the base pool when so many jobs are active, and I try to give it as much memory 
as possible.

Is there anything I can do at the system tuning level to improve our ability to 
handle all these JDBC connections? The JOBD has *NOLIST to eliminate the SPOOL 
files. 

The prestart entry for QZDASOINIT looks like: 

 Subsystem description:   QUSRWRK        Status:   ACTIVE       
                                                                
 Program  . . . . . . . . . . . . . . . . . . . . :   QZDASOINIT
   Library  . . . . . . . . . . . . . . . . . . . :     QSYS    
 User profile . . . . . . . . . . . . . . . . . . :   QUSER     
 Job  . . . . . . . . . . . . . . . . . . . . . . :   QZDASOINIT
 Job description  . . . . . . . . . . . . . . . . :   QDFTSVR   
   Library  . . . . . . . . . . . . . . . . . . . :     QGPL    
 Start jobs . . . . . . . . . . . . . . . . . . . :   *YES      
 Initial number of jobs . . . . . . . . . . . . . :   1         
 Threshold  . . . . . . . . . . . . . . . . . . . :   1         
 Additional number of jobs  . . . . . . . . . . . :   2         
 Maximum number of jobs . . . . . . . . . . . . . :   *NOMAX    
 Maximum number of uses . . . . . . . . . . . . . :   200       
 Wait for job . . . . . . . . . . . . . . . . . . :   *YES      
 Pool identifier  . . . . . . . . . . . . . . . . :   1         

Thanks,
-Marty