Bill Degnan posted Q. State the four divisions of a COBOL program A: earth air fire water: the 4 elements that make everything :-)
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close. A. (if you look at the code you see the "bugs" ( * ) asterisk characters that have these sections like headers sort of. Anyway, here is what I have: Identification Division: to identify the program, author, and state remarks. Environment Division: identifies within the configuration section the type of comuter used within the input-output section; the files which are accessed. Data Division: identifies the record layouts of the files and any other data elements used within the program. Procedure Division: Contains the logic of the program. Bill P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
Sorry I touched COBOL in like 1991. Back then I determined I couldn't program for squat. On Tue, Apr 14, 2020 at 3:00 PM Bill Degnan via vcf-midatlantic <vcf-midatlantic@lists.vcfed.org> wrote:
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close.
A. (if you look at the code you see the "bugs" ( * ) asterisk characters that have these sections like headers sort of. Anyway, here is what I have:
Identification Division: to identify the program, author, and state remarks.
Environment Division: identifies within the configuration section the type of comuter used within the input-output section; the files which are accessed.
Data Division: identifies the record layouts of the files and any other data elements used within the program.
Procedure Division: Contains the logic of the program.
Bill
P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
I learned Pascal, FORTRAN, and C back in the day. Never saw any COBOL but definitely interested. On Tue, Apr 14, 2020 at 3:05 PM Christian Liendo via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Sorry I touched COBOL in like 1991.
Back then I determined I couldn't program for squat.
On Tue, Apr 14, 2020 at 3:00 PM Bill Degnan via vcf-midatlantic <vcf-midatlantic@lists.vcfed.org> wrote:
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close.
A. (if you look at the code you see the "bugs" ( * ) asterisk characters that have these sections like headers sort of. Anyway, here is what I
have:
Identification Division: to identify the program, author, and state remarks.
Environment Division: identifies within the configuration section the
type
of comuter used within the input-output section; the files which are accessed.
Data Division: identifies the record layouts of the files and any other data elements used within the program.
Procedure Division: Contains the logic of the program.
Bill
P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
Last time I did any COBOL was 1987. Never looked back. On Tue, Apr 14, 2020 at 3:12 PM Chris Fala via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
I learned Pascal, FORTRAN, and C back in the day. Never saw any COBOL but definitely interested.
On Tue, Apr 14, 2020 at 3:05 PM Christian Liendo via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Sorry I touched COBOL in like 1991.
Back then I determined I couldn't program for squat.
On Tue, Apr 14, 2020 at 3:00 PM Bill Degnan via vcf-midatlantic <vcf-midatlantic@lists.vcfed.org> wrote:
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close.
A. (if you look at the code you see the "bugs" ( * ) asterisk
characters
that have these sections like headers sort of. Anyway, here is what I have:
Identification Division: to identify the program, author, and state remarks.
Environment Division: identifies within the configuration section the type of comuter used within the input-output section; the files which are accessed.
Data Division: identifies the record layouts of the files and any other data elements used within the program.
Procedure Division: Contains the logic of the program.
Bill
P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
Never touched COBOL, looked at it once and determined I'd never see it on a microcontroller. Besides isn't COBOL a heavy element? ;-) It's radioactive. Much too dangerous for most people. -- Linux Home Automation Neil Cherry ncherry@linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog Author of: Linux Smart Homes For Dummies
On Tue, 14 Apr 2020, Neil Cherry via vcf-midatlantic wrote:
Never touched COBOL, looked at it once and determined I'd never see it on a microcontroller.
I took three classes in COBOL in the mid-80s. That's the last time I ever wrote a line of COBOL code. Mike Loewen mloewen@cpumagic.scol.pa.us Old Technology http://q7.neurotica.com/Oldtech/
-----Original Message----- From: vcf-midatlantic <vcf-midatlantic-bounces@lists.vcfed.org> On Behalf Of Bill Degnan via vcf-midatlantic Sent: 14 April 2020 20:00 To: vcf-midatlantic <vcf-midatlantic@lists.vcfed.org> Cc: Bill Degnan <billdegnan@gmail.com> Subject: Re: [vcf-midatlantic] COBOL wise-guy
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf- midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close.
A. (if you look at the code you see the "bugs" ( * ) asterisk characters that have these sections like headers sort of. Anyway, here is what I have:
Identification Division: to identify the program, author, and state remarks.
Always an interesting section to read, but usually full of useless junk. If you got one where the author was recorded as "Rasputin the Mad Monk" or "Muffin the Mule" you knew you were in trouble... Worse if there was a list of contributors longer than the cast lists of all the Star Wars films appended end to end, you were in deepest dodo.......
Environment Division: identifies within the configuration section the type of comuter used within the input-output section; the files which are accessed.
Generally the same in every program...
Data Division: identifies the record layouts of the files and any other data elements used within the program.
yes
Procedure Division: Contains the logic of the program.
Well yes, but we did have one program that had more "ALTER" statements, that dynamically altered every "GOTO" to go elsewhere, than conventional logic... ... It was worth the trouble maintaining it. It was a replacement for a previous, conventional program that ran in about an hour... ... it ran so quickly that the first time we ran it we didn't believe it worked, and ran it again....
Bill
Dave
P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
Recently received some DECtape images that have PDP-8 COBOL compiler and COBOL source files. Helps if you read German. http://www.pdp8online.com/images/images/Wullenweber.shtml On Tue, Apr 14, 2020 at 02:59:50PM -0400, Bill Degnan via vcf-midatlantic wrote:
On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
Close.
A. (if you look at the code you see the "bugs" ( * ) asterisk characters that have these sections like headers sort of. Anyway, here is what I have:
Identification Division: to identify the program, author, and state remarks.
Environment Division: identifies within the configuration section the type of comuter used within the input-output section; the files which are accessed.
Data Division: identifies the record layouts of the files and any other data elements used within the program.
Procedure Division: Contains the logic of the program.
Bill
P.S. This is a vintage computer club. I would think there is at least one COBOL guru here? I barely know anything other than running jobs TSO/JCL. By the time I worked at DuPont, the only professional COBOL environment I worked and everything was in production, we used to make changes to existing code.
On 4/14/20 1:56 PM, Jeffrey Jonas via vcf-midatlantic wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
All I know is that the purpose of the COBOL compiler on RSTS/E was to teach how to spell the word environment. You wouldn't believe how long the compilation error listing was if you missed the middle 'N'. BK
On Tue, Apr 14, 2020, 6:01 PM Barry L. Kline via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
On 4/14/20 1:56 PM, Jeffrey Jonas via vcf-midatlantic wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
All I know is that the purpose of the COBOL compiler on RSTS/E was to teach how to spell the word environment. You wouldn't believe how long the compilation error listing was if you missed the middle 'N'.
BK
What I liked was the classic green screen terminals. The code was all body, lots of lines of asterisks separating each section. Code was very structured and exact. You had to think in terms of columns, not rows. Very apt to the punch card B
On 4/14/20 6:00 PM, Barry L. Kline via vcf-midatlantic wrote:
On 4/14/20 1:56 PM, Jeffrey Jonas via vcf-midatlantic wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
All I know is that the purpose of the COBOL compiler on RSTS/E was to teach how to spell the word environment. You wouldn't believe how long the compilation error listing was if you missed the middle 'N'.
I would not have been a good COBOL programmer! To this day I know that n is there yet I can't seem to type it without extra effort. -- Linux Home Automation Neil Cherry ncherry@linuxha.com http://www.linuxha.com/ Main site http://linuxha.blogspot.com/ My HA Blog Author of: Linux Smart Homes For Dummies
How To Geek even did a writeup on COBOL and the governor's request: https://www.howtogeek.com/667596/what-is-cobol-and-why-do-so-many-institutio... On Tue, Apr 14, 2020 at 1:57 PM Jeffrey Jonas via vcf-midatlantic < vcf-midatlantic@lists.vcfed.org> wrote:
Bill Degnan posted Q. State the four divisions of a COBOL program
A: earth air fire water: the 4 elements that make everything :-)
-- ========================================= Jeff Brace Vice President & Board Member, VCF East Showrunner Vintage Computer Federation http://www.vcfed.org/ jeffrey@vcfed.org
participants (13)
-
Barry L. Kline -
Bill Degnan -
Chris Fala -
Christian Liendo -
Dave Wade -
David Gesswein -
Dean Notarnicola -
Douglas Crawford -
Jeffrey Brace -
Jeffrey Jonas -
jsalzman＠gmail.com -
Mike Loewen -
Neil Cherry