🚀 go-pugleaf

Don't know if this helps:

1) You can set the initial RC to 0 by executing IEFBR14.
If you test RC before a program has been executed, it is null.

2) You can nest your conditional JCL. I think 15 levels is the max.

3) There is also an ELSE condition which you can Use

4) You can break your job stream up into several jobs, and use the
internal reader to start them.

5) I don't know of any way to reset the RC for a JOB.

Denis <grossnou@antispam.skynet.be> wrote in message
news:8c1rst$dnl$1@hardcopy.ny.jpmorgan.com...
> (I know that this question is off-topic but I do not know in which
newsgroup
> to post-it)
> I have a JCL question: Is it possible to reset the RC system
variable in a
> JCL ? for example, with a statement like:
> // SET RC=0
> Obviously this statement does not work as RC it is not a normal
"variable"
>
> The goal is to have a JCL like the following:
>
> file://S1 EXEC PGM=P1
> ...
> //  IF (RC GE 8) THEN   <--- start of the "does not work"
construction
> //   SET RC=4                 <--- does not work the idea is to
"reset" the
> RC variable to 4
> // ENDIF                          <--- end of the "does not work"
> construction
>
> // IF (RC GE 4) THEN  <--- want to test with RC = 4 even if S1 ended
with
> RC=8
> file://S2 EXEC PGM=P2
> ...
> // ENDIF
>
> This JCL is generated via FTINCL statements from a REXX/ISPF proc
and has a
> (quite large) variable number of steps after the step S2. The idea
is to
> avoid to have to generate very complex IF/THEN/ENDIF construction
for the
> steps that follow S2 (for example by qualifying each test of RC with
the
> step name...)
>
> Any idea?
>
> Many thanks in advance
>
>