Sign on and off time

[David Abramowitz]

One way would be to associate an <u>Initial Program</u> with the user profile. That program would keep track of user logons. Dave

[Guest.Visitor]

Another way you can check this (I think) is to look at the System History file. It is called QHST. I am pretty sure it has the date and time, as well as userid for each session on the system. The entry contains the beginning and ending timestamp for each session. I haven't looked at it in awhile, but I'm pretty sure QHST has what you need. Doug

[Guest.Visitor]

2ndTim wrote: > We are having an issue with reported overtime. I would like to help > that issue by providing the times a user signed on and off the > system. > > Signing on would be easy, using sign on programs and log something > there. Signing off would not be as easy. > > Is there a better way of logging signing on and a way of logging when > a user signs off? I believe you can use Job Accounting for this, see the Work Management manual for more details. Bill

[Guest.Visitor]

The job start and end messages are logged to the QHST* files. But they have an incrementing alphanum suffix which probably prevents you reading them directly in a program. Direct access to the log is via the DSPLOG command. You could limit your search for specific job/device names, time periods and message id's (e.g. CPF1124 for start and CPF1164 for end). The main problem with this, though, would probably be that you can only send the output to screen or printer. You could read back the spooled output and process that, or perhaps there is an API for retrieving the history log messages?

[G.Gaunt]

Why not just register an exit program for the SIGNOFF command under the QIBM_QCA_RTV_COMMAND exit point. Write the code in the exit program to calculate job duration. Search the web for QIBM_QCA_RTV_COMMAND for examples.

[Guest.Visitor]

I use Activation Schedules (CHGACTSCDE) for account access which sets up job scheduled entries. Manager's supply me with the scheduled hours/days and I set them up. The jobs will enable and disable the accounts as designated in the setup. Depending on how many users you have, it may take a bit of time initially, but from then on it's simply part of the account setup. I actually have the scheduled hours/days as part of my Account Request Form. This has totally eliminated overtime not previously approved. In addition, quite often a manager will request I modify the access schedule. At that point, I make the changes via CHGJOBSCDE.

[Guest.Visitor]

Kim, THANKS FOR THAT TIP!!! I subscribe to e-mail updates to this column, and read your answer. I did not even know that command existed. Has it been around for a long time? Thanks again! Doug.

[2ndtim]

We are having an issue with reported overtime. I would like to help that issue by providing the times a user signed on and off the system. Signing on would be easy, using sign on programs and log something there. Signing off would not be as easy. Is there a better way of logging signing on and a way of logging when a user signs off? Thanx!

[Guest.Visitor]

I think this will do it for getting the info you are looking for out of the history logs.

code.txt (http://www.mcpressonline.com/images/fbfiles/files/6ae7fc03_code.txt)