Re: Where is SET allowed in JCL?

Still waiting for a reply on my requesting the sources from some 2+ months ago. Vince On 23/12/15 23:54, Clem Clarke wrote: > Gil, if you hate JCL, why not look at Jol? With simple English like > syntax. > > It does more than JCL, run in backgound/batch or you can execute jobs > under TSO. > > I

Re: Where is SET allowed in JCL?

Gil, if you hate JCL, why not look at Jol? With simple English like syntax. It does more than JCL, run in backgound/batch or you can execute jobs under TSO. It has a simple PANEL instruction to make interactive screens. You can pass Symbolic Parameters from job to job. It has a Scheduling Fa

Re: Where is SET allowed in JCL?

In , on 12/23/2015 at 12:55 PM, "Hardee, Chuck" said: >Make sense? No. That would explain failing on a // SET anywhere in the contatenation, but not failing only after the first // DD. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: Where is SET allowed in JCL?

W dniu 2015-12-23 o 16:00, Paul Gilmartin pisze: Just curious: why do you need to insert SET into DD concatenation? Reversing the rhetoric, why does IBM need to prohibit SET between the first and second DD statements in a concatenation while it's allowed between any two others? You are right

Re: Where is SET allowed in JCL?

I hate JCL! You're working in z/OS... Deal with it! This email � including attachments � may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message.

Re: Where is SET allowed in JCL?

On Tue, 22 Dec 2015 21:59:19 -0600, Paul Gilmartin wrote: >Aargh! It's documented!: > >Location in the JCL >z/OS MVS JCL Reference >SA23-1385-00 >... >It cannot appear immediately after the first DD statement within a > concatenation. > >YTF!? Does anyone believe it was specified that w

Re: Where is SET allowed in JCL?

I hate, eschew, despise, software that is so poorly documented that I have to hack at it for hours or days to finally figure out, it's broken. And then, I have to battle some bug reporting system to report the bug, and then it is 2 or more years before it gets fixed (assuming it gets fixed).

Re: Where is SET allowed in JCL?

: Re: Where is SET allowed in JCL? There are many "why doesn't IBM" cases (why don't they uppercase my JCL when I forgot to do so? I guess it was tons of work more to make this enhancement 10 years ago in 60 year old code, than to document not to do so. At least it is well

Re: Where is SET allowed in JCL?

>>> Just curious: why do you need to insert SET into DD concatenation? Regards Radoslaw Skorupka Lodz, Poland >>> To override a value of a symbol from this point on? -- For IBM-MAIN subscribe / signoff / archive

Re: Where is SET allowed in JCL?

y of other software/platforms: "something went wrong". Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: 23 December, 2015 16:00 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where is SET allowed in JCL? On W

Re: Where is SET allowed in JCL?

In <5763936936315627.wa.paulgboulderaim@listserv.ua.edu>, on 12/22/2015 at 09:59 PM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> said: >YTF!? ITYM "WTF?". >Does anyone believe it was specified that way, C2H5OH. I coined the term Broken As Desiged (BAD); ISAGN for "B

Re: Where is SET allowed in JCL?

On Wed, 23 Dec 2015 07:41:15 -0700, Lizette Koehler wrote: >Gil, >For the DD * statement, have you tried this? > >//DD2 DD * >/* >// SET >// DD PATH= > >Maybe the terminator /* after a DD * might work? > It makes no difference. >> On 2015-12-23, at 05:44, R.S. wrote: >> >> >> >> I

Re: Where is SET allowed in JCL?

in > Sent: Wednesday, December 23, 2015 7:13 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Where is SET allowed in JCL? > > On 2015-12-23, at 05:44, R.S. wrote: > >> > >> I hate JCL! > > Just curious: why do you need to insert SET into DD concatenation? >

Re: Where is SET allowed in JCL?

On 2015-12-23, at 05:44, R.S. wrote: >> >> I hate JCL! > Just curious: why do you need to insert SET into DD concatenation? > No "need" just style for clarity. I could have put all my SET statements a hundred lines earlier, immediately after JOB. Instead I thought my JCL would be easiest to re

Re: Where is SET allowed in JCL?

please inform the sender and delete all copies. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, December 23, 2015 7:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where is SET allowed in JCL? W dniu 2015-12-23 o

Re: Where is SET allowed in JCL?

W dniu 2015-12-23 o 04:41, Paul Gilmartin pisze: Sometimes within a DD concatenation; sometimes not. For example: 3 //STEP EXEC PGM=IEFBR14 //* 4 //DD1DD * 5 // DD PATH='/dev/./null' 6 // SET V1=WOMBAT 7 // DD PATH

Re: Where is SET allowed in JCL?

s documentation. To verify, you could change the DD * to a dataset and see if it still fails. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Paul Gilmartin > Sent: Tuesday, December 22, 2015 8:41 PM > To:

Re: Where is SET allowed in JCL?

On Tue, 22 Dec 2015 21:41:21 -0600, Paul Gilmartin wrote: >Sometimes within a DD concatenation; sometimes not. For example: > >3 //STEP EXEC PGM=IEFBR14 > //* >4 //DD1DD * >5 //

Where is SET allowed in JCL?

Sometimes within a DD concatenation; sometimes not. For example: 3 //STEP EXEC PGM=IEFBR14 //* 4 //DD1DD * 5 // DD PATH='/dev/./null' 6 // SET V1=WOMBAT