On Fri, 7 Jan 2022 20:30:03 +, Seymour J Metz wrote:
>> Would it be a favor to programmers to make misiplacing IF, etc.
>> within a job step, or SET within IF ... ENDIF a syntax error? The
>> effect is probably not what the programmers intend.
>
>IMHO, the current behavior is a bug, but it mi
Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Friday, January 7, 2022 12:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL IF-THEN-ELSE-ENDIF Re: ... Re: Top 8 Reasons for using Python
instead of REXX for z/OS
On Fri, 7 Jan 2022 04:29:52 +, Nash, Jonathan S. wrote:
>
&g
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Hobart Spitz [orexx...@gmail.com]
Sent: Friday, January 7, 2022 1:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL IF-THEN-ELSE-ENDIF Re: ... Re: Top 8 Reasons for using Python
I think it's worth mentioning that the reason that SET must be
unconditional is that JES has to issue ENQs after, AFAIK, the initial JCL
scan and before execution starts. If a dataset has an embedded symbolic,
doing the correct ENQ when the value might change at execution time could
cause all kind
On Fri, 7 Jan 2022 04:29:52 +, Nash, Jonathan S. wrote:
>
>... I was just
>working on some JCL and I had just assumed that I
>could set symbolics using IF THEN ELSE ENDIF:
>
>// IF (STEP1.RC = 0) THEN
>// SYMB=GOOD
>// ELSE
>// SYMB=BAD
>// ENDIF
>
>but I found out that BOTH SET stateme
@LISTSERV.UA.EDU
Subject: JCL IF-THEN-ELSE-ENDIF Re: ... Re: Top 8 Reasons for using Python
instead of REXX for z/OS
Its funny you should mention that now. I was just
working on some JCL and I had just assumed that I
could set symbolics using IF THEN ELSE ENDIF:
// IF (STEP1.RC = 0) THEN
// SYMB=GOOD
Its funny you should mention that now. I was just
working on some JCL and I had just assumed that I
could set symbolics using IF THEN ELSE ENDIF:
// IF (STEP1.RC = 0) THEN
// SYMB=GOOD
// ELSE
// SYMB=BAD
// ENDIF
but I found out that BOTH SET statements are executed
no matter what the retur
