1 ASSETS
  The ASSETS command displays the contents of the resource utilization
  record in the accounting data base for your account.  It reveals how
  closely the rate at which you are using system resources matches the
  maximum "threshold" rates set for your account.  When you use system
  resources faster than your threshold rates your account will be load
  regulated temporarily, which means that response time will be slower
  than if you were not regulated.  The objective of load regulation is
  to permit you to continue to use resources if they're free, but pri-
  ority will be given to those who have not exceeded their thresholds.  
  The ASSETS output is broken up into several different displays which
  may be selected as desired.
  
  Format:
 
    ASSETS
 
  By default, the /REGULATION screen is displayed.

2 Qualifiers
 
/ALL

  /ALL

  Displays all of the information screens in alphabetic order.

/DAILY_HISTORY

  /DAILY_HISTORY

  Displays the daily history information screen.  This display gives
  some information about the past history of your account.   Namely, 
  it shows you what your last 5 day's activity has been and how many
  days out of the last 32 you've been over your cpu threshold.

/LIFE_HISTORY

  /LIFE_HISTORY

  Displays the life history information screen.   This display gives
  some information about total usages for your account since date of
  creation, and since the beginning of the academic quarter.

  The term "raw" refers to cpu time in minutes native to the machine
  before being adjusted for off-shift discounts or normalized to VAX
  11/780 equivalents.

/OUTPUT
 
  /OUTPUT=[output-file-spec]
 
  Re-directs the output into the file "output-file-spec."  Output is
  directed to the screen by default (SYS$OUTPUT).
 
/PRIORITY

  /PRIORITY

  Displays the priority chart screen.  This display demonstrates how
  load regulation values are calculated for over threshold users.

  Your regulation value is based on how many out of the last 32 days
  your cpu usage exceeded your threshold,  and how much your average
  cpu usage is over that threshold.   Unregulated processes normally
  run at priority 4.  The maximum regulation priority, 2 will reduce
  your response time drastically.

/REGULATION

  /REGULATION (default)

  Displays the regulation information screen.  This display gives an
  overview of your regulation history and current status.

  The last use and last update fields are updated whenever a process
  running under your account terminates.  These may include terminal
  sessions, batch jobs, subprocesses, ect..  The retention period is
  the date at which your account will be deleted through lack of use
  if you quit using it today.  As long as your account is used, this
  date will continue to advance. Your account may also be deleted if
  your are no longer affiliated with the University.

  The connect time is an indication of how long your account is con-
  nected to the system via interactive sessions.  Batch jobs are not
  charged for connect time. The CPU time is the amount of processing
  time accumulated.  The 5-day averates are calculated by taking the
  last 4 days' activity plus the current day's activity and dividing
  by five.  The definition of a day is from 8 am until 8 am the next
  day.  The break down of this information is displayed in the daily
  history display.

  The term normalized refers to thresholds and CPU usages which have
  been converted to VAX 11/780 equivalent minutes. The normalization
  factor is displayed on the header line.

  The term adjusted refers to discounts that are given for off-shift
  processing.   Usage between 10 pm and 8 am is given a 50% discount
  before being added into the accumulators.  In addition, batch jobs
  are given another 50% discount.  Batch jobs are those submitted to
  the VMS batch queue(s).  

  The daily non-batch CPU quantum is the amount of non-batch CPU you
  can use each day before your non-batch processes are  subjected to
  regulation, even if your average usage exceeds your threshold. The
  daily non-batch quantum starts accumulating at 8 am.   The purpose
  of this quantum is to allow you to perform CPU intensive processes
  overnight, or as batch jobs, without having it affect your "light"
  usage (such as reading your email) the next day.

/TERSE

  /TERSE

  Displays the terse information screen.   This display provides the
  same information as the other displays but in a condensed format.
