  Philosophy of EXQUOTA? 
 The Question is:
 
 
        Does EXQUOTA, process quota exceeded mean:
 
                An error, but I won't tell you which one ?
 
 
        Usually exeeding a quota results to an proper error message or RWAST
        or similar, depending if the process resource wait state bit is set
        or not.
 
 
        According to the VMS source listings EXQUOTA means exceeding one
        of the following quotas:
 
        - AST count
        - Byte count
        - Open file count
        - Buffered I/O count
        - Direct I/O count
        - CPU time limit
	- Common event flag block creation
	- Pagefile quota
        - CXB Buffers (NETDRIVER)
        - PORT$W_xBUF_MAX (PEDRIVER)
        - Too many Watch Points (WPDRIVER)
 
 
        There are propably more reasons as the VMS source listings kit does
        not contain all of the sources.
 
 
        Any plans to fix this ?
 
 
 The Answer is:
 
  Yes, SS$_EXQUOTA does in fact mean "An error, but I won't tell you
  which one?".  Unfortunately.
 
  No, there are no plans to fix this.  There is far too much existing
  internal and customer software to allow any change here.  Numerous
  discussions have occured among engineering to see if there could be
  any reliable way to supplement or replace this error message with a
  better and more specific one -- there are more specific quota error
  messages allocated and available -- but no mechanism has been found
  that would not also have the potential to unduly perturb existing
  applications.
 
