I usually just look at the user name in the detailed job log entries, although what shows up there can vary depending on user registry type and whether or not credential mapping is used.
Choose a job you love, and you will never have to work a day in your life. - Confucius
We are handing over the project to different team to monitor the production jobs, rerun if job aborts. In case if they mishandle(like run job unnecessarily) and any issue occurs, it would be helpful if we can identify the user.
As noted, you can identify the user by simply looking in the log. Of course at some point the logs will purge and that information will be gone. I was looking for more specifics as to what you need to do with it - 'track' is a far too generic term. Do you need to store it somewhere, in say something like a run history table? Include it in a failure email? Something else entirely?
-craig
"You can never have too many knives" -- Logan Nine Fingers