MAINFRAME - TIP OF THE DAY :
When you specified V for RECFM parameter, LRECL value is largest record in the file plus 4 bytes. These four bytes contain the actual length of each variable length record in the file

I never tried this before. But, after the first STOP RUN executed, there will be no statements executed. But, DO NOT USE STOP RUN in your COBOL coding.... IT IS NOT ADVISABLE... Instead of this, you can use GOBACK._________________Arun

If you use STOP RUN in a CALLed module of a Batch Rununit, the rununit will stop.
that is why usage of GOBACK is always perfered._________________Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

I agree with Arun: STOP RUN is an old instruction from back in the days when we did not code modularly. you can code GOBACK instead of STOP RUN anywhere. It is considered good practice now-a-days not to use STOP RUN._________________Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

main modules coded with GOBACK, that acquire their input and output from other than linkage, could be used as submodules.

a lot easier to just always use GOBACK, and not rely on the coder to make the differentiation;
looking thru these forums and experience in the field has lead me and others to insist on GOBACK.
Just one less problem to deal with.

Besides, how many main modules are written in comparision to CICS or submodules?

But if you want to code STOP RUN all the time, that is your business.
you just have to remember to use GOBACK when appropriate._________________Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

The GOBACK statement functions like the EXIT PROGRAM statement when it is coded as part of a called program and like the STOP RUN statement when coded in a main program.

One might ask , Does any version of COBOL support STOP RUN anymore?

While the compiler still supports STOP RUN, many organizations do not allow it to be used. One of the things checked in the promotion process is that GOBACK is used and there is no STOP RUN in the code._________________Regards,
Anuj

Is there any specific reason for suggesting GOBACK instead of STOP RUN , even in normal cobol programs ( i am not talking about sub programs, cics programs )

Other exception here can be IMS-COBOL program. IMS programs run under the control of batch initilization module DFSRRC00.If you code Stop Run the control is return to OS instead of DFSRRC00. So code GOBACK to give the control back to the called module its DFSRRC00._________________Regards,
Anuj