[comp.os.vms] Causes For A Process To Go From CURrent To COMputable State...

CLAYTON@xrt.upenn.EDU ("Paul D. Clayton") (07/06/87)

Information From TSO Financial - The Saga Continues...
Chapter 7 - July 5, 1987

Todd Warnock of Clemson University asks the following question.

	What, other than reaching quantum, can cause a process to go 
	from CURrent to COMputable ?

There are two causes for a process to go from the CURrent state to the 
COMputable under VMS. 

The first as Todd had stated was the expiration of quantum for the process, 
resulting in the process being scheduled for another quantum the next time 
around.

The second reason is caused by a process with a higher, or equal, software 
priority level resuming and the schedular determines that the new process
becomes the CURrent process. The priority level here is not the device 
INTERRUPT levels but the 0 to 31 software levels that are defined in VMS. The
0 to 15 levels being those dedicated to 'timesharing' users, while 16 through
31 are for 'real' time.

Hope this helps.

F.Y.I.
During the Spring Symposium, 1987, the DECUS store had for sale a PRELIMINARY,
and PARTIAL, updated version of the 'VMS Internals And Data Structures' manual.
The 4.4 version of VMS is the baseline for the book. There was no date given 
for the release of the full edition, or the COMPLETE table of contents.


Paul D. Clayton - Manager Of Systems
TSO Financial - Horsham, Pa. USA
Address - CLAYTON%XRT@CIS.UPENN.EDU