SSL tasks
Example data for the SSL tasks, and information about how to interpret the data.
Example data
Task, Type, Requests, Busy %, CPU used, CPU %, "avg CPU", "avg ET", longest, date, time , , , , Seconds, , uSeconds, uSeconds, uSeconds, , 0, SSL, 3112, 1.2, 0.248538, 0.3, 80, 362, 8864, 2014/03/18, 12:46:40.237697 1, SSL, 3070, 1.2, 0.245433, 0.3, 80, 359, 4714, 2014/03/18, 12:46:18.938022 2, SSL, 3170, 1.2, 0.255557, 0.3, 81, 362, 7273, 2014/03/18, 12:46:35.358145 3, SSL, 3060, 1.2, 0.246542, 0.3, 81, 365, 13164, 2014/03/18, 12:46:44.514045 4, SSL, 3120, 1.3, 0.251927, 0.3, 81, 373, 22438, 2014/03/18, 12:46:22.134123 Summ, SSL, 15532, 1.2, 1.247998, 0.3, 80, 364, 22438, 2014/03/18, 12:46:22.134123
This example data shows that the average request took 364 microseconds. The longest request was for SSL task 4, took 22,438 microseconds, and occurred at 12:46:22.134123 local time.
The fields are calculated from:- Duration: qwhs.qwhsdurn
- Requests : qctreqn
- Busy %: qcteltm and duration
- CPU used: qctcptm
- CPU %: qctcptm and duration
- Average CPU: qctcptm and qctreqn
- Average ET: qcteltm and qctreqn
- Longest: qctlsdu longest at: qctlstm
If the SSL tasks are busy for a significant proportion of the interval, increasing the number of SSL tasks might help. If the SSL tasks are waiting for external resources such as a coprocesor, increasing the number of SSL tasks has little effect.
We can use the ALTER QMGR SSLTASKS() command to change the number of SSL tasks used. Any changes come into effect the next time the CHINIT is started.