Channel accounting data records
Use this topic as a reference for channel accounting data records.
The format of the channel accounting data record is described in assembler macro thlqual.SCSQMACS(CSQDQCST). The format is also described in the C programming language header file thlqual.SCSQC370(CSQDSMFC). Note that the field names in C are all in lowercase, for example, qcst.
The channel accounting data gives you information about the status and statistics of each channel instance, including:
- Average network time (qcstntav)
- Average time on exit (qcstetav)
- Channel batch data limit (qcstcbdl)
- Channel batch interval (qcstcbit)
- Channel batch size (qcstcbsz)
- Channel dispatcher number (qcstdspn)
- Channel disposition (qcstchdp)
- Channel name (qcstchnm)
- Channel state (qcstchst)
- Channel started time (qcststrt)
- Channel status collected time (qcstcltm)
- Channel stopped time (qcstludt)
- Channel type (qcstchty)
- Common name (CN) from SSLCERTI (qcstslcn)
- Compression rate (qcstcpra)
- Connection name (qcstcnnm)
- Current shared conversations (qcstcscv)
- DNS resolution time (qcstdnrt)
- Effective value of STATCHL parameter (qcststcl)
- Last message time (qcstlmst)
- Maximum network time (qcstntmx)
- Maximum time on exit (qcstetmx)
- Minimum network time (qcstntmn)
- Minimum time on exit (qcstetmn)
- Name of the remote queue manager or application (qcstrqmn)
- Number of batches (qcstbatc)
- Number of bytes for message data (qcstnbyt)
- Number of bytes for persistent message data (qcstnpby)
- Number of bytes received for both message data and control information (qcstbyrc)
- Number of bytes sent for both message data and control information (qcstbyst)
- Number of full batches (qcstfuba)
- Number of messages, or number of MQI calls (qcstnmsg)
- Number of persistent messages (qcstnpmg)
- Number of put retries (qcstptrc)
- Number of transmission queue becoming empty (qcstqetc)
- Number of transmission buffers received ( qcstbfrc )
- Number of transmission buffers sent (qcstbfst)
- Serial number from SSLPEER (qcstslsn)
- SSL CipherSpec (zero means TLS not used) (qcstslcs)
- The date and time of maximum network time (qcstntdt)
- The date and time of maximum time on exit (qcstetdt)
Note, that for the channel accounting field qcstetmn (Minimum time on exit) and qcstntmn (Minimum network time) these two fields will be initialized to the hexadecimal value of 8FFFFFFF when unused.
We can use this information to see the throughput of a channel, if the actual batches are approaching the limit, the latency of the network, information about the remote end, performance of user exit, and so on.
Here is an example of the channel accounting data which has been formatted with IBM MQ SupportPac MP1B.
The fields available are based on the display channel status command (DIS CHS) and channel statistics by IBM MQ on platforms except z/OS, with some additional fields.The data and time of the start and end of the record in local time, and the duration SMF interval start 2014/03/26,02:30:00 SMF interval end 2014/03/26,02:45:00 SMF interval duration 899.997759 seconds Information about the channel Connection name 9.20.4.159 Channel disp PRIVATE Channel type RECEIVER Channel status CLOSING Channel STATCHL HIGH Start date & time 2014/03/26,02:44:58 Channel status collect time 2014/03/26,02:45:00 Last status changed 1900/01/01,00:00:00 Last msg time 2014/03/26,02:44:59 Batch size 50 Messages/batch 3.3 Number of messages 1,102 Number of persistent messages 1,102 Number of batches 335 Number of full batches 0 Number of partial batches 335 Buffers sent 337 Buffers received 1,272 Message data 5,038,344 4 MB Persistent message data 5,038,344 4 MB Non persistent message data 0 0 B Total bytes sent 9,852 9 KB Total bytes received 5,043,520 4 MB Bytes received/Batch 15,055 14 KB Bytes sent/Batch 29 29 B Batches/Second 1 Bytes received/message 4,576 4 KB Bytes sent/message 8 8 B Bytes received/second 28,019 27 KB/sec Bytes sent/second 54 54 B/sec Compression rate 0 The name of the queue manager at the remote end of the connection Remote qmgr/app MQPH Put retry count 0Parent topic: Interpreting IBM MQ for z/OS accounting data