How to Troubleshoot - SQL1226N due to many db2agent processes attached to the instance

Question: On a DB2 LUW 9.7 instance , I’m getting these error messages. What commands can I use to investigate and troubleshoot SQL1226N due to many db2agent processes attached to the instance?

I’ve read the post ADM7519W DB2 could not allocate an agent. The SQLCODE is "-1225" , but require some method to extract db2agent information and work with application owners.

SQL1226N due to many db2agent processes attached to the instance
ADM7009E  An error was encountered in the "TCPIP" protocol support.  A possible
cause is that the maximum number of agents has been exceeded.

Answer: It is sometimes difficult to find the root cause of these error messages. A good place to start when gathering information is to use the db2pd utility. Use the information returned from these dbpd   examples to investigate further

---Example 1 : returns informations about the agents 
db2pd –agents
--- Example 2 :  view active statements
db2pd -db  -activestatements
--Example 3 : Find db2agent  with high cpu consumption. Use the EDU ID to locate the application through the db2pd –app –dyn 
db2pd –edu

 Read More on DB2 reorg and analyzing trap files

How to monitor a DB2 REORG - DBA DB2

Analyzing a DB2 trap file - DBA DB2

DB2 - SQL1035N The database is currently in use - DBA DB2