HP3000-L Archives

May 2003, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Atwood, Tim (DVM)" <[log in to unmask]>
Reply To:
Atwood, Tim (DVM)
Date:
Fri, 16 May 2003 18:22:32 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (100 lines)
This got me thinking. Which is a dangerous thing....

Is there any way to implement a "logoff" UDC or command file? Similar to how
you can specify "OPTION LOGON". But instead the UDC or command file would
only be executed when the session/job terminated. It would need to be
executed even when the session was aborted or otherwise terminated without
the "bye" command.

If you can do this, then tracking user CPU is simple. Simply write the
variables HPUSER (or maybe HPSTREAMEDBY) along with HPCPUMSECS to a file or
database at logoff time.

-----Original Message-----
From: Atwood, Tim (DVM) [mailto:[log in to unmask]]
Sent: Friday, May 16, 2003 6:10 PM
To: [log in to unmask]
Subject: Re: CPU usage


The "Workload Group" function in Lund SOS could be configured to track this
information and report it.

I have never configured a workload group for more than a small portion of
users on a system though. And I have never run the SOS monitor job all the
time with the shorter cycle times I suspect might be needed to get accurate
information. So I do not know what kind of system impact would result from
defining each user as a separate workload and then running the SOS monitor
all the time.

I would guess the Lund's follow on tool Meta-View Performance Manager has
similar capabilities. You would need to check directly with Lund to know for
sure.

-----Original Message-----
From: Gilles Schipper [mailto:[log in to unmask]]
Sent: Friday, May 16, 2003 5:21 PM
To: [log in to unmask]
Subject: Re: CPU usage


I don't believe it is possible - unless an optional tool such as Glance or
SOS offers that capability via the measurement interface.

However, you may be able to achieve your ultimate goal if you were to
overcome one of your stated objections - forcing users to log into unique
groups.

Unless you are constrained by some specific application software over which
you have little control, it may not be as difficult nor cumbersome as you
imagine it to be - although there would certainly be some additional
administrative overhead.

It really depends on your HP3000 computing environment and the exact nature
of your objective.




At 07:33 PM 2003-05-16, Newton, Ernie wrote:
>Greetings,
>
>We currently use REPORT to track CPU usage for
>individual GROUPS.  I have been asked if it's
>possible to track CPU usage for individual
>USERS.  I know I can do it if I have them log
>into unique GROUPS, but that's not an option.
>
>I don't need to look in the past, this is for
>future usage.
>
>I am perusing my VESOFT manual as I type...
>
>Thanks,
>
>Ernie,
>Yolo County Office of Education
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

----------------------------------------------------------------------------
---------------------
Gilles Schipper
GSA Inc.
HP System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
email:  [log in to unmask]  web: http://www.gsainc.com
----------------------------------------------------------------------------
---------------------

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2