What happens to the original job after a JUMP JOB instruction is executed?

• A. The controller will not return to the original job after jumping.
• B. The controller returns to the original job after jumping.
• C. The controller terminates both jobs.
• D. The controller queues the original job to resume later.

Answer: (A)

The main idea is how control flows between programs. A JUMP JOB instruction hands execution from the current program to another separate job. This is a one-way transfer: once you jump, you don’t automatically come back to where you left off. The controller starts executing the target job, and any code that followed the jump in the original program won’t run unless there’s an explicit mechanism to return to it. If you need to resume the original program later, you’d have to insert a return or another control flow construct that explicitly brings execution back. Because of that, the behavior described—not returning to the original job after jumping—is the expected result.