Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-08 Thread Bernd Oppolzer
The PASCAL compiler on the RS/6000 (with AIX) allowed the file names to be specified by the use of environment variables. IIRC: if you had environment variables that matched the names in your program statement, that is program anyname (FILE1, FILE2, FILE3); you could specify the final file

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-08 Thread Bernd Oppolzer
Just an idea: if this was possible on today's Linux and C, too, the migration of mainframe C programs to Linux, which open files using dd:somename would be much easier. ( I have this problem sometimes, because management decides that some of our mainframe based test supporting C programs should

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-08 Thread Shmuel Metz (Seymour J.)
In 7701653492190617.wa.paulgboulderaim@listserv.ua.edu, on 11/07/2013 at 02:04 PM, Paul Gilmartin paulgboul...@aim.com said: When I said a couple weeks ago that alternate DDNAMES should be handled by ATTACH, transparent to the application, someone asked, What about programs that scan the

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-08 Thread Paul Gilmartin
On Fri, 8 Nov 2013 10:58:46 +0100, Bernd Oppolzer wrote: ( I have this problem sometimes, because management decides that some of our mainframe based test supporting C programs should be moved to Linux 64 on Intel). For now, the solution is #ifdef MAINFRAME fopen /* this way */ #else

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Ze'ev Atlas
Let me add another complains about JCL, it allows changing source code meaning in run time and sometimes this is hairy: //XXX DD DSN= // DCB=(LRECL=80,R //... The above is legit although I would fire anybody who doed it. R could be resolved to: // EXEC YYY,R='BLKSIZE=8000)' or it

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Mitch
, Legacy Modernization Consultant www.lcmg.us -Original Message- From: Ze'ev Atlas zatl...@yahoo.com To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU Sent: Thu, Nov 7, 2013 8:39 am Subject: Re: JCL (was: Re: Aging Sysprogs = Aging Farmers) Let me add another complains about JCL, it allows changing

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Richard Pinion
? --- mitc...@aol.com wrote: From: Mitch mitc...@aol.com To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JCL (was: Re: Aging Sysprogs = Aging Farmers) Date: Thu, 7 Nov 2013 12:34:39 -0500 Ze'ev, I work with a product that would prevent this type of thing from happening

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Gerhard Postpischil
On 11/7/2013 12:41 PM, Richard Pinion wrote: And to throw another twist to this thread, some people say the LRECL and RECFM should not be coded in the JCL. That way when a change is made to the program source, that affects LRECL and/or RECFM, the corresponding JCL doesn't have to be updated.

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Paul Gilmartin
On Thu, 7 Nov 2013 09:41:40 -0800, Richard Pinion wrote: And to throw another twist to this thread, some people say the LRECL and RECFM should not be coded in the JCL. That way when a change is made to the program source, that affects LRECL and/or RECFM, the corresponding JCL doesn't have to

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Tony Harminc
On 7 November 2013 12:41, Richard Pinion rpin...@netscape.com wrote: And to throw another twist to this thread, some people say the LRECL and RECFM should not be coded in the JCL. That way when a change is made to the program source, that affects LRECL and/or RECFM, the corresponding JCL

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Mitch
Consultant www.lcmg.us -Original Message- From: Paul Gilmartin paulgboul...@aim.com To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU Sent: Thu, Nov 7, 2013 10:23 am Subject: Re: JCL (was: Re: Aging Sysprogs = Aging Farmers) On Thu, 7 Nov 2013 09:41:40 -0800, Richard Pinion wrote: And to throw another

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Martin Packer
...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: Paul Gilmartin paulgboul...@aim.com To: IBM-MAIN@listserv.ua.edu Date: 07/11/2013 18:23 Subject:Re: JCL (was: Re: Aging Sysprogs = Aging Farmers

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Paul Gilmartin
On Thu, 7 Nov 2013 13:37:54 -0500, Tony Harminc wrote: Taking that to the extreme one could say that nothing should be coded on DD statements, i.e. that programs should deal with DSNAMEs rather then the intermediary of DDNAMEs. Which is indeed how most non-z/OS systems work. In UNIX, I see the

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-07 Thread Clark Morris
On 7 Nov 2013 10:38:24 -0800, in bit.listserv.ibm-main you wrote: On 7 November 2013 12:41, Richard Pinion rpin...@netscape.com wrote: And to throw another twist to this thread, some people say the LRECL and RECFM should not be coded in the JCL. That way when a change is made to the program

JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread Pew, Curtis G
On Nov 6, 2013, at 8:45 AM, David Crayford dcrayf...@gmail.com wrote: Hey, how do I do a loop in this code? Forget it kid, they didn't have rewind on punch card readers. I think much of the disdain for JCL comes from inaccurate expectations set by calling it a “language”. JCL is *not a

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread Pommier, Rex
, November 06, 2013 10:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JCL (was: Re: Aging Sysprogs = Aging Farmers) On Nov 6, 2013, at 8:45 AM, David Crayford dcrayf...@gmail.com wrote: Hey, how do I do a loop in this code? Forget it kid, they didn't have rewind on punch card readers. I think much

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread John Gilmore
Many organizations of linguists discourage, even forbid generic discussions of the origins of language on the ground that these discussions produce only acrimony. Perhaps we should avoid discussions of JCL, good or bad? in the same spirit. John Gilmore, Ashland, MA 01721 - USA

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread Mitch
@austin.utexas.edu To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU Sent: Wed, Nov 6, 2013 8:15 am Subject: JCL (was: Re: Aging Sysprogs = Aging Farmers) On Nov 6, 2013, at 8:45 AM, David Crayford dcrayf...@gmail.com wrote: Hey, how do I do a loop in this code? Forget it kid, they didn't have rewind on punch card

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread David Andrews
On Wed, 2013-11-06 at 16:15 +, Pew, Curtis G wrote: JCL is *not a programming language*. I might have made the same claim on the basis that JCL isn't Turing-complete, but a minimal amount of googling informs me that programming languages need not be Turing-complete. JCL is a language. You

Re: JCL (was: Re: Aging Sysprogs = Aging Farmers)

2013-11-06 Thread Paul Gilmartin
On Wed, 6 Nov 2013 12:35:37 -0500, Mitch wrote: ..., there are a number of tools on the market for managing JCL and a couple that can actually manipulate and create JCL. For money!? I build most of my JCL with either Rexx EXECs or POSIX shell (plus sed and awk) scripts. It relieves me of the