Section: BSIT 3E
Case Study #: 6
Using the process state diagram, explain why there is no transition:
• From the READY to WAITING.
• From the WAITING to RUNNING.
From the READY to WAITING
Ready when the processor becomes free so it is happen that in this case ready state is occupying the part of processing unit when a running process is interrupted by the processor after completing its allotted time, its state is saved in its process control block, its process state changed to ready and its priority adjusted. A ready state process is runable but temporarily stopped running to let another process run. But never the Ready state will go directly to waiting state. There may be many "ready" processes at any one point of the systems execution - for example, in a one processor system, only one process can be executing at any one time, and all other "concurrently executing" processes will be waiting for execution. Ready to Waiting will happen when the process is already on the running state that needs to be fixed to trouble shoot the any problem of that running process.
From the WAITING to RUNNING
A process is said to be blocked if it is waiting for some event to happen such that as an I/O completion before it can proceed; a process is unable to run until some external event happens; a process that is blocked on some event (such as I/O operation completion or a signal). When a process blocks, it does so because logically it cannot continue, typically because it is waiting for input that is not yet available. Formally, a process is said to be blocked if it is waiting for some event to happen (such as an I/O completion) before it can proceed. In this state a process is unable to run until some external event happens. When the Ready state is not occupied the waiting state process will be on the ready state while waiting for the Running process to be executed and will be manipulated and be processed. But never the waiting will move directly to the running state.
