Tuning Garbage collection with the 1.4.2 Hotspot JVM

• For many applications garbage collection performance is not significant
• Default collector should be first choice

There are essentially two GC threads running. One is a very lightweight thread which does "little" collections primarily on the Eden (a.k.a. Young) generation of the heap. The other is the Full GC thread which traverses the entire heap when there is not enough memory left to allocate space for objects which get promoted from the Eden to the older generation(s).
If there is a memory leak or inadequate heap allocated, eventually the older generation will start to run out of room causing the Full GC thread to run (nearly) continuously. Since this process "stops the world", Resin won't be able to respond to requests and they'll start to back up.
Read More on Tuning Garbage collection with the 1.4.2 Hotspot JVM

DB/DBM configuration in DB2 on Z/OS, OS/390 or AS/400

Question:
I could connect to DB2 database on AS/400, but cannot> see any DBM or DB configuration. Is database or database manager> configuration available for DB2 on Z/OS, OS/390 or AS/400?
Solution:
Most of the config parms for DB2 for z/OS are in the zparms. The zparms arenot closely related to either the db or dbm configuration parms on DB2 forLinux, UNIX, and Windows. Usually only the DB2 systems programmer (not theDBA) can change the zparms.