Ok, John, there's that risk. A pity you cannot use the built-in facility
for forcing idle users (FC FORCEUSR command) since that will
take action right after recomputing the monitor data. But it is going
to do a FORCE LOGOFF and not a FORCE DISCONNECT, and
a FORCE LOGOFF is not really adequate for the IDLE case. Sorry
about that: I really implemented FORCEUSR for throwing out
looping users on my system and added the IDLE option for others.
And 15 years ago the real storage taken up by hundreds of idle
users was still a concern, it wasn't just a security problem.
But you might ask Endicott to spend a few hours and implement
a FORCE DISCONNECT option for the IDLE case ..
Eginhard Jaeger
----- Original Message -----
From: "Romanowski, John (OFT)" <[EMAIL PROTECTED]>
To: <IBMVM@LISTSERV.UARK.EDU>
Sent: Friday, March 24, 2006 2:40 PM
Subject: Re: Performance Toolkit -how to RECOMP?
Thank you Eginhard, you've given me the info I need, 'Q MON'.
PerfKit is a wonderful tool, thank you also for developing it.
The IDLEUSER report is accurate and up-to-date as of its timestamp.
But I'm using it to implement a security policy to disconnect userids
(people) that have been idle more than a specified number of minutes.
So I need to look at the IDLEUSER report immediately after it's
generated otherwise I could mistakenly use a 59 seconds old (stale)
report to disconnect people that were actually very active between the
time the report was generated and when I used the report.
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or
otherwise legally protected. It is intended only for the addressee. If you
received this e-mail in error or from someone who was not authorized to
send it to you, do not disseminate, copy or otherwise use this e-mail or
its attachments. Please notify the sender immediately by reply e-mail and
delete the e-mail from your system.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Eginhard Jaeger
Sent: Friday, March 24, 2006 2:15 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Performance Toolkit -how to RECOMP?
I can use Performance Toolkit's IDLEUSER command to display a list of
idle userids and how many minutes they were idle, BUT, the info can be
stale depending on how long it's been since the timestamp shown on the
IDLEUSER report.
Stale? The screen should be updated automatically at the end of each new
CP monitor sample interval, i.e. every 60 seconds if you work with the
default setting. If this doesn't happen on your system then you should
report a bug (but it worked correctly when I just tried).
Have you set a longer sample interval on your system?
Is there a PerfTK command to force it recompute the IDLEUSER report?
(like RealTimeMonitor's RECOMP command?)
No, not for the screens based on CP monitor data. As mentioned above,
they should all be AUTOMATICALLY refreshed whenever new data
becomes available. No need to tell PerfKit to do so manually!
Recomputing the information before new data becomes available doesn't
make much sense since it would yield exactly the same output you
already see on the screen ..
(The screens are rebuilt without new data only after changing the
sorting
sequence.)
The few screens that obtain data directly from CP control blocks using
diagnose x'04' (e.g. user and device details) can be forced to refresh
by simply hitting ENTER.
or lacking that, is there a command to display info I could use to
predict the next time at which PerfTK will update its IDLEUSER report?
That period is the interval set for the CP monitor sample interval.
Use the command 'Q MON' to display it.
Eginhard Jaeger
