It is an event, not an interrupt.
    
    sh
    
    At 06:26 PM 2/11/01 -0500, you wrote:
    >When a job goes fom Job Scheduler to Process Scheduler, to my knowledge, no
    >event is generated.
    >
    >
    >Chad Waldman wrote:
    >
    > > So, you are saying that C should be put on the ready queue before A is
    > > put back on? This means the external event arrives before the internal
    > > event gets finished processing (What I mean by finished processing is
    > > its placement back on the ready queue). This breaks the rule of internal
    > > event first. It also unfortunately breaks my program.
    > >
    > > Chad
    > >
    > > ----- Original Message -----
    > > From: "sallie henry (Sallie Henry)" <henry@CS.VT.EDU>
    > > To: <CS3204_11372@LISTSERV.VT.EDU>
    > > Sent: Sunday, February 11, 2001 2:25 PM
    > > Subject: question
    > >
    > > > If processes A and B are on the ready queue (A is running), and C
    > > arrives
    > > > (external event causing A to be interrupted before the end of its
    > > > timeslice).  After processing, the ready queue looks like:
    > > >
    > > > B C A (with B running).
    > > >
    > > > sh
    > > >