At 11:15 AM 10/1/97 +0200, you wrote:
>Hi Everybody,
>
>Thanks for all the replies to my question on programmer authorities. 
>
>Here's a new one. How do you charge your user base for machine usage?
>We currently use a percentage of cpu time per company in the group, but I
>find this highly inaccurate as some companies use more at specific times of
>the year than they do for the remainder. One company closes down in
>December, so their percentage is lower due to 11 months usage over a 12
>month reporting period, even though their usage is quite high over the
>year. I want to change it to a combination of interactive transactions,
>batch jobs submitted and i/o requests to the data base. 
>
You can use AS/400 job accounting.  It's not complicated, although you will
have to read the chapter on it in the book at least twice to get it.  If
you bill by user, it required NO coding changes.  It gets tackier when you
try to bill out a user apportioned to multiple departments (e.g.:  a
programmer or operator).

OS/400 gives you everything you need to capture the data, but nothing to
report it.  There are some useful TAATOOLs to handle the reporting.

Al



Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].