It works everything well except SORT procedure.
.
Before I learn SPL,  COBOL code is lot like FORTRAN
code with bunch of GO TO
After using SPL and COBOL code is more like SPL
Perform until / end-perform instead of GOTO..
Evaluate when instead of IF then Else...

I missed SPL It has indentation when you compile nested logic
like level 1, 2,3,4,5 more than 4 or 5 usually call another procedure.

Peter C.

Jeff Kell <[log in to unmask]> wrote in message
news:F4B1826B1A21D211AEC5006008207AF402114026@dogbert.csillc.com...
> Tom wrote:
> >
> > I perform SECTIONs instead of PARAgraphs. The only fall-through I
> > would use is a "trap-door" type of construct.
>
> I fully concur.  This methodology tends to keep sections shorter and
> more akin to pure procedures in other languages.  I further suggest
> that GO TO's (prior to scope terminators almost impossible to avoid)
> be restricted to the current section, or common error-handling code
> (using a PERFORM IMAGE-ERROR to avoid a goto to an error trap is not
> eliminating a GOTO but merely masking it).
>
> Sections came into vogue for us back in the classic days when you
> could segment your code using section level numbers.  It is no longer
> such a strong concern other than promoting some code locality.
>
> In more recent days I have advocated nested subprograms and global
> variables.  This simplifies the complexity of using lengthy linkage
> sections when using subprograms.
>
> Jeff Kell <[log in to unmask]>
>