hello dear friends

which states of process isn't in multiprogramming systems ?

states of process : " ready to run" to "running" or "running" to "ready to run" or "running" to "waiting (blocked)" or "waiting" to "ready to run" .

i need a complete answer with clear reason please

Dani AI

Generated

Short answer: the only transition that is not guaranteed in a pure multiprogramming design is the OS-forced preemption that takes a running process off the CPU and returns it to the ready queue. In strictly non-preemptive multiprogramming the CPU is released only when the running job voluntarily blocks (for I/O) or terminates, so a forced switch back to ready does not occur.

Why that matters: "Multiprogramming" just means several jobs are kept in memory so the CPU can be kept busy when one job waits. Preemption (time-slicing) is a separate capability that requires a timer interrupt and a preemptive scheduler; that capability produces the forced running->ready behavior and is characteristic of time-sharing or multitasking systems. If the multiprogramming system is implemented with preemption, the forced switch exists; if it is non-preemptive, it does not.

Practical note for exams and writeups: state the scheduling assumption. If "preemptive" is not specified, many textbook questions expect non-preemptive multiprogramming and answerers should say that only voluntary context switches (block/exit) plus dispatches occur; if the OS is preemptive, explicitly include the forced switch. See Multiprogramming - Wikipedia and Process state - Wikipedia for diagrams and formal definitions.

Comment on the thread: listed the common state changes in the original post; 's suggestion to research was appropriate—the key point that needed clarification was whether the scheduler is preemptive.

Recommended Answers

All 2 Replies

Is it for your homework, or similar course work? It really isn't that difficult, my friend. It's quite elementary stuff, and researching this will give you a more rounded out understanding of the subject. Honestly, on this occasion, and others may think differently, if you come back to us with what you think the answer is and why, I would be happy to give guidance. (please don't see me as any sort of authority here, I'm just thinking about what's best for you)

ok thankx . you'r right .

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.