Add a "Last Active" Timestamp or number of elapsed seconds since the last activity for a Job to WRKACTJOB and QUSRJOBI API

While we know that interactive jobs have an inactivity timer on them, the Work Active Jobs (WRKACTJOB) and the corresponding API do not provide us with information on how long a user hasn't had an interaction with the 5250 session or a batch job has been "sitting on a wait".

We sometimes (as does everyone) have uses who sign on in the morning, and then during the day might start up secondary jobs and do other work, and also sign onto remote terminals and then walk way after finding that piece of info they needed. This is very common and happens everyday.

We would like to know how long specifically interactive jobs have been idle but all jobs would be great. Then we can take the appropriate action. 

So picture this. The Operation Manager of the Company walks into the back room and signs onto a 5250 app and does a few inquiries and may prints something they need. Then walks after to get what they need. But instead of returning to that terminal they simply go about the job and leave, never to return that day. But the terminal sits there signed on. No one else is back there, so it just sits. 

Now it is 10 PM and no one is in the building however the Operations Mgr is known to work late. So the Operator (remotely) views a query that shows the equivalent of WRKACTJOB. But since the QUSRJOBI has not "idle" information or anything that might be able to be used to calculate the idle time, we have to call the Operations Manage and ask them if they are actually working.  We could send a message "Please sign off" but in our environment knowing that the job has been sitting since 7:40 AM would evidence enough to cancel that job.