WebSphere® MQ accounting
information can be collected for three subtypes:
- 0
- Message manager accounting records (how much of the central processing
unit (CPU) was spent processing WebSphere MQ
API calls and the number of MQPUT and MQGET calls). This information
is produced when a named task disconnects from WebSphere MQ. The information contained
within the record might cover many hours.
- 1
- Accounting data for each task, at thread and queue level.
- 2
- Additional queue-level accounting data (if the task uses more
queues than can fit in the subtype 1 record).
Subtype 0 is produced with trace class 1. Subtypes 1 and 2 are
produced with trace class 3.