Multiple choice technology mainframe

What if you code GO BACK instead of STOP RUN in a independent COBOL program

  1. What's the problem in it? Will go fine!

  2. Program goes in infinite loop.

  3. Program will not execute.

  4. Compiler throws error.

Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

In an independent COBOL program (not called by another program), GO BACK functions identically to STOP RUN - it terminates the program and returns control to the operating system. It will not cause infinite loops (B), prevent execution (C), or cause compiler errors (D).

AI explanation

In an independent (main, standalone) COBOL program, GOBACK behaves exactly like STOP RUN: since there is no calling program to return to, control simply passes back to the operating system and the program ends normally. The 'infinite loop' claim is a persistent piece of COBOL folklore, but IBM's Enterprise COBOL documentation confirms GOBACK is safe to use in place of STOP RUN in a standalone program.