How to bypass a step always.

sashi · New User Joined: 14 Sep 2005 Posts: 54 Location: Chennai

Hi
I have a job with 5 steps.

and I want to skip the Step No: 5 always.
I don't want to execute the Step No:5 even previous steps fails or successfully executed.

How a can get this using COND CODE?

Thanks

expat · Posted: Thu May 06, 2010 7:26 pm

I would say "easily", but that depends on the complexity of the JCL structure.

Is this step contained in instream JCL, a PROC, a nested PROC

What did you find confusing in the JCL reference manual when you read it for the COND parameter ?

sashi · New User Joined: 14 Sep 2005 Posts: 54 Location: Chennai

expat · Posted: Thu May 06, 2010 7:43 pm

Is the step in question, the step that you do not want to process, contained in instream JCl, a PROC or a nested PROC.

I did not ask what the step did, merely asked in which state that the JCL is in.

sashi · New User Joined: 14 Sep 2005 Posts: 54 Location: Chennai

expat · Posted: Thu May 06, 2010 7:54 pm

OK, let me try and put this in a simple manner that you may better understand.

The job that you submit, what does it look like

Is it instream JCL, i.e. that each and every step is shown as an EXEC card that has PGM= on it and then followed by its DD statements , or is it a PROC which has only one EXEC card without PGM= coded and has very few if any DD statement visible.

Anuj Dhawan · Posted: Thu May 06, 2010 7:58 pm

I'll also give a try to this riddle (with lots of assumptions):

1. Make another JCL, which does not have this step altogther, till you get the server up.

2. Comment out this step from teh existing JCL/PROC/JOB.

3. Create another job using IEBEDIT, execute the steps of your choice.

4. Because it's the last step, you might include the "null-indicator" (//) in the JCL stream.

Ronald Burr · Posted: Thu May 06, 2010 8:25 pm

If it is only pure JCL and NOT a PROC, then it is just as easy to comment out the step as it would be to add a COND parameter. However, if adding a COND parameter is really what you want to do, then try COND=(4095,GT) - this will cause STEP5 to be bypassed unless a) no abend occurred, and b) a previous step executed successfully and set an RC of 4095 or greater ( highly doubtful ).

sashi · New User Joined: 14 Sep 2005 Posts: 54 Location: Chennai

Thanks for replays…....friends..

I got my answer..
just simply put a IF condition...

//IF RC < 0 THEN
//STEP5
//ENDIF

it will never execute step5.

dbzTHEdinosauer · Posted: Thu May 06, 2010 11:24 pm

never understand why the necessity of using a COND code,
when commenting out the step is

so easy
so obvious
and will be require no more time to change than putting in a COND code
- that will require processor time - where as comments require no processor time
- and is confusing - since no one at your site knew to do this, no one will understand what is going on

dneufarth · Posted: Fri May 07, 2010 2:54 am

Goes along with all those classroom discussions of "how can I skip step3 in a 5 step job using only cond"?

Sudhanshu Shekhar · Posted: Fri May 07, 2010 10:25 am

Escapa · Posted: Fri May 07, 2010 10:31 am

Just glanced in to see what this thread is about....

dick scherrer · Posted: Fri May 07, 2010 10:37 am

Hi Sambahji,

Not if the cond was placed on the exec statement.

The posted example should be more complete. . .

Escapa · Posted: Fri May 07, 2010 10:43 am

Hi Dick.. My reply was referencing to Sashi's query..
He said

PeterHolland · Posted: Fri May 07, 2010 4:15 pm

If step 5 is the last step put /*EOF before the last step EXEC.

dick scherrer · Posted: Fri May 07, 2010 8:49 pm

Hi Sambhaji,

Yup, There appear to be 2 separate conversations. . .

Hopefully, Sashi now has sufficient info. . .

PeterHolland · Posted: Fri May 07, 2010 9:26 pm

Or a construction like this :