Re: Stop Run vs GoBack
- From: "Charles Hottel" <chottel@xxxxxxxxxxxxx>
- Date: Tue, 26 Jun 2007 00:53:08 GMT
"Howard Brazee" <howard@xxxxxxxxxx> wrote in message
news:oenv731931gr8c1uol2iaot9m5ai17d97m@xxxxxxxxxx
On Sun, 24 Jun 2007 22:57:25 -0700, Richard <riplin@xxxxxxxxxxxx>
wrote:
ie:
EXIT PROGRAM
.
STOP RUN
.
That syntax always bothered me. Logically, if we exit a program at
EXIT PROGRAM, subsequent statements would be meaningless.
Long ago I worked on a CDC 6400 computer with the Scope 3.2 operating
system. My very first COBOL assignment in that environment was to write a
simple subroutine that read a record from a file and did an EXIT PROGRAM.
Someone gave me the Scope statments to compile and instead of a short cpu
time limit it had IIRC all 9's for unlimted amount of cpu time. IIRC the
EXIT PROGRAM occurred in an IF or some other conditional so I coded it
without a period at the end. Unfortunately for me on that COBOL compiler the
official EXIT PROGRAM ends with a period and at least in this particular
code the COBOL went into an infinite loop with not job time limit to stop
it. One particular error meassage was repeated a huge number of times.
.
- References:
- Stop Run vs GoBack
- From: William M. Klein
- Re: Stop Run vs GoBack
- From: Pete Dashwood
- Re: Stop Run vs GoBack
- From: William M. Klein
- Re: Stop Run vs GoBack
- From: Richard
- Re: Stop Run vs GoBack
- From: Howard Brazee
- Stop Run vs GoBack
- Prev by Date: Re: COBOL record length on z/series
- Next by Date: Re: Stop Run vs GoBack
- Previous by thread: Re: Stop Run vs GoBack
- Next by thread: Re: Stop Run vs GoBack
- Index(es):