Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!wucs.UUCP!berkley
From: berkley@wucs.UUCP (Berkley Shands)
Newsgroups: mod.computers.vax
Subject: Accounting on the VAX/VMS
Message-ID: <8609251254.AA10434@wucs.UUCP>
Date: Thu, 25-Sep-86 08:54:46 EDT
Article-I.D.: wucs.8609251254.AA10434
Posted: Thu Sep 25 08:54:46 1986
Date-Received: Sat, 27-Sep-86 18:31:15 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Keywords: Accounting, VMS
Approved: info-vax@sri-kl.arpa

Accounting? Not under 4.X of VMS.  Right now you can rack up 72 seconds
of runtime in a 60 second period (USE MONITOR/RECORD/MODES).  This is because
"The granularity of the VMS scheduler allows this." (A DEC developer).

Now for the good news.  The latest "Dr. Tops" article in the DECUS SIG 
newsletter (under the LS Sig) claims that the VMS developers are working
hard on "BEAN COUNTING" for version 5.0 of VMS.  I would bet that this
would be a full blown accounting (accurate/repeatable) system.  CPU
and DISK and SPOOLING etc. would be covered.
	If you looked back a few issues, "Dr. Tops" provided a few nice
utilities for dealing with the current VMS accounting system. Look at the code,
it contains some things that will help anyone trying to avoid 3rd party
accounting packages (that suffer the same fate :-). 

Mr. Berkley Shands
Large Systems SIG
Special Projects Coordinator

Flames to BERKLEY@WUNET.UUCP or BERKLEY@WUCS.UUCP.WUSTL or something like that!