Time every IBM i session from the history log with one SQL query
IT Jungle's Guru column pairs job-start CPF1124 and job-end CPF1164 messages from QSYS2.HISTORY_LOG_INFO on job number and user, then uses TIMESTAMPDIFF to show how long each session ran. Point the same query at the profiles your agents and service jobs run under, and land the rows in a table you keep, because the history log only reaches back as far as your cleanup settings allow.
Built In.
The best of the log, every two weeks. One idea, one proof, one next step.
Built In.
The best of the log, every two weeks. One idea, one proof, one next step.
References do not imply endorsement. The link goes to the original source; the words are ours. Silver Lake Financial Group and Alder & Pine Home, where mentioned, are fictitious demonstration companies.