JCL exceution flow with typical requirement

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi,

Could anybody put a logic to below requiremet::

JCL is with 10 to 15 steps and return code of one steps governs the excecution of rest of the steps in the JCL for example

STEP1

-----

STEP 2
-----

.
.
.
.
.
.
Step 20.

Step 2 exceutes only if step 1 return 0 . and if step 1 return code is other then zero then none of the steps of the JCL will execute

similarly
Step 3 exceutes only if step 2 return 0 . and if step 2 return code is other then zero then none of the steps of the JCL will execute

and SO . If you append condition code for each steps and based on the previous steps at last step one can land with lots of condition codes .

So is we can do following in JCL to solve this problem
1. Some sort of GOTO type in JCL.
2. Can we find out whether a step executes or flused in JCL

Waiting for logics :-)))

expat · Posted: Fri May 18, 2007 4:38 pm

COND=(0,NE) on the jobcard

Job sysout will tell you FLUSH or RC

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi

Oops i forgot to mention that not all the steps return code is based "zero". So of the steps return code 1 4 or 8 is acceptable so we can't go with job card logic

Sorry for missing out the requiement :-(

Ples suggest

expat · Posted: Fri May 18, 2007 5:58 pm

WOW, a can of worms.

The only quick, and very dirty, idea I can come up with is that after each step you have a IEFBR14 step that will try to access a non existent dataset, and if the IEFBR14 is executed then the job will fail JCL error.

Apart from that ..............................................

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hey

But i dont want to loose the jobs return code in between :-(((

hey i need to code JCL like we calls user abend in between :-))) the cobol program :-)

Its like that to check the return code of previous step and based on it next steps need to execute and if it did not meet the acceptable Return code other down the line steps need to be flused ... I m really stucked

I m looking forward with only option left to use nested IF in my JCL.

Please suuugest if anbody have another approach

superk · Posted: Fri May 18, 2007 6:21 pm

Maybe I'm over simplifying the question, but wouldn't a set of OR conditions work:

expat · Posted: Fri May 18, 2007 6:32 pm

The way that I understood it ......... if STEP2 gets bypassed, then unless we have reams and reams of condition checks STEP3 would run.

So each step would have checks for all acceptable options for all previous steps, which would
a) probably exceed the allowed limit on cond= checks per step
b) be a complete nightmare to maintain

Is there a "NOT RUN" option/parm in IF / THEN / ELSE code ???

Mmmmmmmmmmmm, off to the manuals to see.

dick scherrer · Posted: Fri May 18, 2007 11:46 pm

Hello,

For my $.02, the programs and/or jobstream needs to be made more supportable.

Let's assume that there is a way to handle the myriad of possible codes - think of what this might be like to restart. . .

superk · Posted: Sat May 19, 2007 12:37 am

There seems to some doubt that my solution won't work.

I tested it. It does exactly what the OP specified.

dick scherrer · Posted: Sat May 19, 2007 12:48 am

Hello,

expat · Posted: Sat May 19, 2007 1:37 am

superk,

Not a doubt

just a question.

Unfortunately I didn't get a chance to peruse the documentation.

Let's face it, you have come up with some great solutions, but I only raised a valid question, (well I thought it was valid), with possible options.

Oh boy, not the birch twigs again ..........................................

expat · Posted: Sat May 19, 2007 1:42 am

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi

I am still trying to solve this problem. It has one more intricate factor that if you put the condition on the resturn code of some previous step it is possible that the refferrd step got flused

. So wht will be the fate of conditional coding ???

Thanks you all

dick scherrer · Posted: Sat May 19, 2007 8:27 am

Hello,

It may be time to explain what this job does rather than how you want to solve this condition code situation.

This kind of complexity usually causes many more problems than if solves.

If we understand what the various steps do, we should be able to offer suggestions on how to get your process to work and be supportable.

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi

I have analysed those ways also. IF we some how swaps the steps but the problem still remains the same. An I cant eliminate anay of the steps as they them selves are thr as part of some other requirement :-(

So really got in trouble or need to learn some more to sove it

dick scherrer · Posted: Sat May 19, 2007 7:17 pm

Hello,

It is unlikely that you have analyzed all of the suggestions you might get from folks here. . .

enrico-sorichetti · Posted: Sat May 19, 2007 7:29 pm

I just noticed that the IF/THEN/ELSE logic can be nested up to 15 levels,
so in this case it is just what is needed not top overcomplicate the jcl

expat · Posted: Sat May 19, 2007 8:46 pm

I think that superk's idea will work, with a little tweak.

Or ........ am I missing something (been desperate to say that for ages now

) .... because I think the run check against the previous step should be included too.

My interpretation of the logic is that STEP2 will run on condition of STEP1, so if STEP2 does run, STEP3 checks the return code, but if it doesn't run the STEP2.RUN=TRUE will not allow STEP3 to process, and by continuing the theme through to the end, each step checks its predecessor to (a) see if it did run and (b) if it did, what RC it issued.

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

Hi

Thanks everbody

Now just i need one more solution If i use

// IF (STEP2.RUN=TRUE & (STEP2.RC=0 | STEP2.RC=1 | STEP2.RC=4 | STEP2.RC=8)) THEN
//STEP3 EXEC PGM=PROG3
// ENDIF

And my job get abend in the step3 how to restart the job from Step 3.

Please suggest

expat · Posted: Mon May 21, 2007 11:48 am

Why not try to restart from STEP3 and let us know if

a) there are problems
b) if it works fine

sandeep1dimri · New User Joined: 30 Oct 2006 Posts: 76

If we try to restart the step 3 (when job abended in step 3) the step 3 can't execute as coditional coding stops its execution

I hve tested this