Resolution:
Temporary destinations are usually created by applications in a request-reply scenario.  For example, a requestor sends a request message to a static queue, creates a temporary queue and waits for a reply on this temporary queue. The replier can receive the request message from the static queue and send a reply message to the temporary queue. If both requestor and replier are connected to the same EMS server, it is the responsibility of the application (requestor) to delete the temporary destination after it finishes using it. If a requestor and replier are connected by two EMS servers which are connected by a route, on the replier side, EMS will delete the temporary destination after the reply message is routed to the requestor EMS server. EMS deletes these every 3 minutes.

"TmpQ" or "TmpT" column in the output of "show connections full" shows the number of temporary destinations created by individual connections during the lifetime of this connection (i.e., including those already deleted and the current ones). For example,

L  Version   ID        FSXT  S  Host                     IP address     User                ClientID                                                                                        Sess Prod Cons TmpT   TmpQ Uncomm UncommSize     Uptime
 

J  7.0.0 V12  2 ---C  +  host                 xx.xxx.xxx.xxx  user                                                                                                                              31    0   15    0 112000    0     0.0 Kb   1:30:17


For the number of temporary destinations currently in the server, refer to the output of "info"/"show server".  For example,

Topics:                   308 (0 dynamic, 0 temporary)

Queues:                   2100 (20 dynamic, 755 temporary)

The commands below can show the name and more information of temporary destinations:

show queues/show topics
show queue <temp_queue>/show topic <temp_topic>