{"id":352,"date":"2023-07-26T01:00:00","date_gmt":"2023-07-25T19:30:00","guid":{"rendered":"http:\/\/ibm-mainframes.com\/blog\/?p=352"},"modified":"2023-11-20T11:17:15","modified_gmt":"2023-11-20T05:47:15","slug":"understanding-stop-run-and-goback-in-cobol","status":"publish","type":"post","link":"https:\/\/zmainframes.com\/zlog\/understanding-stop-run-and-goback-in-cobol\/","title":{"rendered":"Understanding STOP RUN and GOBACK in COBOL"},"content":{"rendered":"

 <\/p>\r\n\r\n

\u00a0Understanding STOP RUN and GOBACK in COBOL: A Comprehensive Guide for Programmers<\/u><\/strong><\/h2>\r\n\r\n\r\n\r\n

Introduction<\/u><\/strong><\/p>\r\n\r\n\r\n\r\n

COBOL (Common Business-Oriented Language) is a widely-used programming language for business applications. Within COBOL programs, two important statements govern the program’s termination and return to the calling program: STOP RUN and GOBACK. In this article, we’ll explore the differences between these statements, their appropriate usage in called and calling programs, and provide examples\"\" to illustrate their functionality.<\/p>\r\n\r\n\r\n\r\n

STOP RUN Statement<\/strong><\/p>\r\n\r\n\r\n\r\n

The STOP RUN statement is used to terminate the current COBOL program gracefully. When this statement is executed, the program’s execution comes to an end, and the control returns to the operating system or the calling program. The STOP RUN statement also releases any resources held by the program, performs end-of-job processing, and closes any open files.<\/p>\r\n\r\n\r\n\r\n

Syntax:<\/p>\r\n\r\n\r\n\r\n

COBOL<\/span>\r\n
STOP RUN<\/span><\/span><\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
Considerations for STOP RUN:<\/p>\r\n\r\n\r\n\r\n
    \r\n
  1. Usage: The STOP RUN statement is primarily used at the end of the main program to conclude its execution. It is not recommended to use STOP RUN within called subprograms as it would terminate the entire program abruptly, leading to unexpected results.<\/li>\r\n\r\n\r\n\r\n
  2. File Handling: The STOP RUN statement ensures that any open files are properly closed before program termination, preventing data corruption or loss.<\/li>\r\n\r\n\r\n\r\n
  3. Error Handling: Since the STOP RUN statement ends the program abruptly, it may not allow for graceful error handling or cleanup of resources in case of exceptions. It is advisable to use GOBACK in most cases, which allows for better error handling and recovery.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
    Example 1: Using STOP RUN in the Main Program<\/p>\r\n\r\n\r\n\r\n
    COBOL<\/span>\r\n
    IDENTIFICATION DIVISION<\/span>.<\/span><\/span>\r\nPROGRAM-ID<\/span>. <\/span>MainProgram<\/span>.<\/span><\/span>\r\nDATA DIVISION<\/span>.<\/span><\/span>\r\nWORKING-STORAGE SECTION<\/span>.<\/span><\/span>\r\n01<\/span> NUM <\/span>PIC 9<\/span>(<\/span>3<\/span>) <\/span>VALUE<\/span> 100. <\/span><\/span>\r\n \r\nPROCEDURE DIVISION<\/span>.<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program has started.\"<\/span><\/span>\r\nMOVE<\/span> 200<\/span> TO<\/span> NUM<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program is ending now.\"<\/span><\/span>\r\nSTOP RUN<\/span>.<\/span><\/span><\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
    In this example, the MainProgram starts, displays a message, sets NUM to 200, and then ends using the STOP RUN statement.<\/p>\r\n\r\n\r\n\r\n
    GOBACK Statement<\/span><\/strong><\/p>\r\n\r\n\r\n\r\n
    The GOBACK statement is used to return control from a called program to the calling program. When a program executes a CALL statement to invoke a subprogram, it temporarily suspends its execution and passes control to the called program. Once the called program completes its execution or encounters a GOBACK statement, control is transferred back to the next statement after the original CALL statement in the calling program.<\/p>\r\n\r\n\r\n\r\n
    Syntax:<\/p>\r\n\r\n\r\n\r\n
    COBOL<\/span>\r\n
    GOBACK<\/span><\/span><\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
    Considerations for GOBACK:<\/p>\r\n\r\n\r\n\r\n
      \r\n
    1. Usage: GOBACK is primarily used within called subprograms to indicate the successful completion of the subprogram’s tasks and return control to the calling program.<\/li>\r\n\r\n\r\n\r\n
    2. Resource Management: Unlike STOP RUN, GOBACK allows the called program to release resources and perform cleanup operations before returning control to the calling program. This makes it suitable for structured error handling and resource management.<\/li>\r\n\r\n\r\n\r\n
    3. Nested CALLs: In scenarios where multiple programs are called in a nested manner, GOBACK ensures that control returns to the appropriate calling program in the correct order.<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
      Example 2: Using GOBACK in a Called Subprogram<\/p>\r\n\r\n\r\n\r\n
      COBOL<\/span>\r\n
      IDENTIFICATION DIVISION<\/span>.<\/span><\/span>\r\nPROGRAM-ID<\/span>. <\/span>SubProgram<\/span>.<\/span><\/span>\r\nDATA DIVISION<\/span>.<\/span><\/span>\r\nWORKING-STORAGE SECTION<\/span>.<\/span><\/span>\r\n01<\/span> SUB-NUM <\/span>PIC 9<\/span>(<\/span>3<\/span>) <\/span>VALUE<\/span> 50. <\/span><\/span>\r\n \r\nPROCEDURE DIVISION<\/span>.<\/span><\/span>\r\nDISPLAY<\/span> \"SubProgram has started.\"<\/span><\/span>\r\nADD<\/span> 100<\/span> TO<\/span> SUB-NUM<\/span><\/span>\r\nDISPLAY<\/span> \"SubProgram is ending now.\"<\/span><\/span>\r\nGOBACK<\/span>.<\/span><\/span>\r\n<\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
      In this example, the SubProgram starts, displays a message, adds 100 to SUB-NUM, and then ends using the GOBACK statement.<\/p>\r\n\r\n\r\n\r\n
      Example 3: Calling SubProgram from Main Program<\/p>\r\n\r\n\r\n\r\n
      COBOL<\/span>\r\n
      IDENTIFICATION DIVISION<\/span>.<\/span><\/span>\r\nPROGRAM-ID<\/span>. <\/span>MainProgram<\/span>.<\/span><\/span>\r\nDATA DIVISION<\/span>.<\/span><\/span>\r\nWORKING-STORAGE SECTION<\/span>.<\/span><\/span>\r\n01<\/span> NUM <\/span>PIC 9<\/span>(<\/span>3<\/span>) <\/span>VALUE<\/span> 100. <\/span><\/span>\r\n \r\nPROCEDURE DIVISION<\/span>.<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program has started.\"<\/span><\/span>\r\nPERFORM<\/span> 2000-TASK<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program is ending now.\"<\/span><\/span>\r\nSTOP RUN<\/span>.<\/span><\/span>\r\n2000-TASK.<\/span><\/span>\r\nDISPLAY<\/span> \"Performing Task 2000.\"<\/span><\/span>\r\nCALL<\/span> \"SubProgram\"<\/span><\/span>\r\nDISPLAY<\/span> \"Task 2000 completed.\"<\/span><\/span>\r\nEXIT<\/span>.<\/span><\/span>\r\n<\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
      In this example, the MainProgram starts, performs a task (2000-TASK) which calls the SubProgram. After the SubProgram completes using the GOBACK statement, the control returns to the next statement after the CALL “SubProgram” statement in the MainProgram.<\/p>\r\n\r\n\r\n\r\n
      Combining GOBACK with Conditional Statements:<\/p>\r\n\r\n\r\n\r\n
      COBOL<\/span>\r\n
      IDENTIFICATION DIVISION<\/span>.<\/span><\/span>\r\nPROGRAM-ID<\/span>. <\/span>MainProgram<\/span>.<\/span><\/span>\r\nDATA DIVISION<\/span>.<\/span><\/span>\r\nWORKING-STORAGE SECTION<\/span>.<\/span><\/span>\r\n01<\/span> NUM <\/span>PIC 9<\/span>(<\/span>3<\/span>) <\/span>VALUE<\/span> 100. <\/span><\/span>\r\n \r\nPROCEDURE DIVISION<\/span>.<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program has started.\"<\/span><\/span>\r\nPERFORM<\/span> 2000-TASK<\/span><\/span>\r\nDISPLAY<\/span> \"Main Program is ending now.\"<\/span><\/span>\r\nSTOP RUN<\/span>.<\/span><\/span>\r\n2000-TASK.<\/span><\/span>\r\nDISPLAY<\/span> \"Performing Task 2000.\"<\/span><\/span>\r\nIF<\/span> NUM <\/span>><\/span> 50<\/span><\/span>\r\nDISPLAY<\/span> \"Task 2000 completed successfully.\"<\/span><\/span>\r\nELSE<\/span><\/span>\r\nDISPLAY<\/span> \"Task 2000 failed.\"<\/span><\/span>\r\nGOBACK<\/span><\/span>\r\nEND-IF<\/span>.<\/span><\/span>\r\n<\/code><\/pre>\r\n<\/div>\r\n\r\n\r\n\r\n
      In this example, the MainProgram starts, performs a task (2000-TASK), which calls the SubProgram. Based on a condition (NUM > 50), the SubProgram either completes successfully or fails using the GOBACK statement.<\/p>\r\n\r\n\r\n\r\n
      Conclusion<\/span><\/strong><\/p>\r\n\r\n\r\n\r\n
      In COBOL, the STOP RUN and GOBACK statements serve distinct purposes in program execution. STOP RUN is used to terminate the entire program, releasing resources and closing files. It is typically employed in the main program. On the other hand, GOBACK is utilized in called subprograms to return control to the calling program, allowing for structured error handling and resource management.<\/p>\r\n\r\n\r\n\r\n
      Understanding when and where to use STOP RUN and GOBACK is essential for designing efficient and robust COBOL programs. With proper usage and consideration of these statements, COBOL developers can ensure smooth program execution and maintainability in business applications.<\/p>\r\n","protected":false},"excerpt":{"rendered":"
      Understanding when and where to use STOP RUN and GOBACK is essential for designing efficient and robust COBOL programs. With proper usage and consideration of these statements, COBOL developers can ensure smooth program execution and maintainability in business applications.<\/p>\n","protected":false},"author":515,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[306,405,37,404,406],"class_list":["post-352","post","type-post","status-publish","format-standard","hentry","category-cobol","tag-cobol-2","tag-goback-in-cobol","tag-mainframes","tag-stop-run-and-goback-in-cobol","tag-stop-run-in-cobol"],"amp_enabled":true,"rttpg_featured_image_url":null,"rttpg_author":{"display_name":"zMainframes","author_link":"https:\/\/zmainframes.com\/zlog\/author\/zmainframes\/"},"rttpg_comment":1,"rttpg_category":"Cobol<\/a>","rttpg_excerpt":"Understanding when and where to use STOP RUN and GOBACK is essential for designing efficient and robust COBOL programs. With proper usage and consideration of these statements, COBOL developers can ensure smooth program execution and maintainability in business applications.","_links":{"self":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/users\/515"}],"replies":[{"embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/comments?post=352"}],"version-history":[{"count":6,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/352\/revisions"}],"predecessor-version":[{"id":1981,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/posts\/352\/revisions\/1981"}],"wp:attachment":[{"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/media?parent=352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/categories?post=352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zmainframes.com\/zlog\/wp-json\/wp\/v2\/tags?post=352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}