  Setting detached process CPU time limit? 
 The Question is:
 
Prior to VMS 7.1 a detached process that gets started from a batch process
did not have a cpu time limit. In 7.1, when a batch job was submitted, which
also starts a detached process as part of it (or at the end of the batch),
it seems to inherit the cpu
time limit from the batch queue on which the job was submitted. Is this the
desired behaviour and something was changed in  7.1? Why was this not
happening in prior versions. Also, is there a work around besides getting
rid of /cpumaximum=
on the batch queue that is used to submit the job that starts the detached
process. Some one susggested a /authorize qualifier with run/detached
command. This work around we might have to do in a lot of places (wherever
the detached process is being start
ed).
 
Thanks - Sri
email :  Sridharan.Varadharajan@intel.com
 
 The Answer is:
 
  The VAX/VMS Internals and Data Structures manual (V4.4 Edition)
  indicates that the process CPULIM value for the created process
  is inhereted from the creating process.
 
  Use of RUN/DETACH/TIME_LIMIT would be one of the more typical ways
  to set the process CPU quota.
 
