[vcf-midatlantic] COBOL wise-guy

Dean Notarnicola dnotarnicola at gmail.com
Tue Apr 14 15:36:58 EDT 2020


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 at 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 at 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 at lists.vcfed.org> wrote:
> > >
> > > On Tue, Apr 14, 2020 at 1:56 PM Jeffrey Jonas via vcf-midatlantic <
> > > vcf-midatlantic at 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.
> >
>


More information about the vcf-midatlantic mailing list