After thinking about it, I like Tim Atwoods suggestion better.
Set up a BYE, EXIT udc that does somthing like this
*********************
IF HPINTERACTIVE = TRUE THEN
SETVAR ESCAPE CHR(27)
SETVAR CPUMIN !HPCPUSECS
SETVAR CONNMIN !HPCONNSECS
SETVAR LBLOG LFT("!HPJOBNAME ",9) + LFT("!HPUSER ",9) + LFT("!HP
ACCOUNT ",9) + "!HPDATEF !HPTIMEF " + RHT("0000000!CPUMIN ",9) + RHT("00
00000!CONNMIN ",9) + RHT("LOGOUT",9)
WRITE CPULOG.DATA.SYS,"!LBLOG"
ELSE
SETVAR ESCAPE CHR(27)
SETVAR CPUMIN !HPCPUSECS
SETVAR CONNMIN !HPCONNSECS
SETVAR LBLOG LFT("!HPJOBNAME ",9) + LFT("!HPUSER ",9) + LFT("!HP
ACCOUNT ",9) + "!HPDATEF !HPTIMEF " + RHT("0000000!CPUMIN ",9) + RHT("00
00000!CONNMIN ",9) + RHT("LOGOUT",9)
WRITE CPULOG.DATA.SYS,"!LBLOG"
ENDIF
ECHO
IF !HPINTERACTIVE
ECHO !ESCAPE&dJ[!LBLOG]!ESCAPE&dBLog.
ELSE
ECHO [!LBLOG]Log.
ECHO
ENDIF
************************
It's not fully tested but it is a start.
-Craig
Gavin Scott <[log in to unmask]> wrote:
Craig suggests:
> It may be possible to turn on logging event 104; Process
> Termination which contains CPU information by user.
I believe you need Job Initiation to tell who people are, then you can
either use Job Termination which includes CPU usage rounded to seconds, or
Process Termination which has it in milliseconds. If you can live with the
"seconds" resolution then you save a tiny bit of overhead and some disk
space by not needing the more voluminous Process Termination logging.
Of course you then need a program to scan the log files an accumulate this
information, dealing with issues like logons that happen in one log file but
the log off or process information may be in a subsequent log file, etc.
There are (were?) commercial (and possibly contributed?) tools to do this
sort of thing.
G.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|