>When searching the MLA-L logs (on IUBVM), I frequently
>get zapped with a message about CPU limit exceeded. This happens
>even when I'm searching logs for an interval of one month.
>Is this CPU limit fixed by ldbase or something that can be changed
>locally?
 
Assuming no problem with the database itself (maybe a "REFRESH list"
might need to be done?), try adding CPULIM= to your JOB card:
 
  The CPULIM keyword
 
  The amount of CPU time that a database  search  job  may  use  is,  by
  default,  limited  to 60 seconds.  The amount of work that can be done
  in this time depends on the CPU model of course.   You  can  raise  or
  lower  this  limit by means of the CPULIM= keyword, whose exact syntax
  is:
 
                              CPULIM=<mm:>ss
 
  The search job is aborted (with a partial  output  being  returned  to
  you) if this limit is exceeded.
 
 
It appears that the MLA-L for November had 12.8 k lines.
 
--  co-owner INFOSYS, TQM-L, CPARK-L, ERAPPA-L, JANITORS, LDBASE-L, et -L
[log in to unmask] "Helping U fulfill your e-mail needs"  +1 814 863 1843
31 Shields Bldg. -- Penn State Univ -- University Park, PA 16802-1202 USA