JCL not having loop capabilities has nothing to do with rewinding card readers. It has to do with variable substitution occurring as interpretation time. How would you get out of a loop except by using the CC? Except in extreme cases, would running the same program multiple times without a JCL change really do something useful.
As for complaining about JCL EXEC statement being first is unnatural, I have to laugh. Do C programmers have trouble placing local variables after the function prototype? C programmers typically place the MAIN() at the end of the source. It's ok once you get used to it but it's certainly not natural. I never understood why they did this but when in Rome, do as the Romans do. Placing JCL before or after the exec is a nit you easily get used to. Jon Perryman. >________________________________ > From: David Crayford <[email protected]> >To: [email protected] >Sent: Wednesday, November 6, 2013 7:40 AM >Subject: Re: Aging Sysprogs = Aging Farmers > > >> On 6 Nov 2013, at 11:32 pm, Paul Gilmartin <[email protected]> wrote: >> >>> On Wed, 6 Nov 2013 22:45:01 +0800, David Crayford wrote: >>> >>> Hey, how do I do a loop in this code? >>> >>> Forget it kid, they didn't have rewind on punch card readers. >> >> DOS, like TSO, places the data set allocations before the command >> ("phase"?), which seems more natural than the JCL convention. >> After all, which do you do first? Oops. I forgot: JCL is declarative >> rather than procedural. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
