Condition Parameter

withlovearif · New User Joined: 21 Mar 2005 Posts: 16

how this statement Executes

QAHDU500 EXEC PGM=FILEAID,REGION=8M,TIME=5,COND=(0,LT,QAHDU400)

priyesh.agrawal · Posted: Mon Jun 20, 2005 7:05 pm

The statement will be executed if QAHDU400 is greater than or equals to ZERO.

If you are checking for Return Code of that step, I think you need to write it like.

COND=(0,LT,QAHDU400.RC)

Forum any comment.

Regards,

Priyesh.

sree_2503 · Posted: Tue Jun 21, 2005 9:38 am

I agree with Priyesh. Considering QAHDU400 to be the step name, one needs to mention the QAHDU400.RC to indicate the return code value that the step returns.

And unless any other RC is explicitly passed, the step QAHDU400 will throw a RC of 0 or 4 under normal execution. Now, for 0, the condition as mentioned in QAHDU500 step, will execute the step ...500 whereas for 4, ...500 will not be executed.

Hope this clears.

dneufarth · Posted: Tue Jun 21, 2005 6:24 pm

Perhaps I'm wrong, but stepname.RC is not needed on the COND= parameter. I'm not sure it is even allowed. Can't find anything in the JCL references that mentions it.

It can be used in the IF/THEN/ELSE/ENDIF construct.

Dave

superk · Posted: Tue Jun 21, 2005 7:00 pm

Straight out of the JCL Reference Guide:

ederrod · Posted: Tue Jun 21, 2005 11:08 pm

Is there a negative cond (e.g. -1)? If not, the step will run from code 0000 to 9999, isn't it?

David P · Posted: Wed Jun 22, 2005 9:03 am

Hi,
I believe the condition codes can not be negative as the range for condition codes is from 0 to 4095.

Please correct me if I am wrong.

thanks
David.

sree_2503 · Posted: Wed Jun 22, 2005 10:24 am

Hi,

Yes, the condition codes cannot be negative. It ranges from 0-4095.

I checked out about the .RC usage in condition codes. No, I didnt find any explicit mention of .RC in the condition parameter anywhere. So, I was wrong.

Well, theres a lead -

If i want to include an Abender step ( step will will lead the job to abend) following a step which calls a proc then this will be like -

//STEP1 EXEC AABBCC,
//.............
//.............
//.............
//*--------------------------------------------
//*HERE COMES THE ABENDER STEP****
//*--------------------------------------------
//ABEND EXEC PGM=ABENDER,
// COND=(4,GE,STEP1.AABBCC01)
//*
//*------------------END----------------------

where AABBCC is the proc called by Step1 in my job, and AABBCC01 is, say, the first step of the proc AABBCC.

Now, if I want to include AND/OR both in my condition param based on the steps of the job as well as that of the proc, how would I club them by?

Any examples, anyone?

P.S - Sorry, for the rather long post - I oughta open a New topic, but considered the thread of the discussion similar...

anuradha · Posted: Thu Jun 23, 2005 5:05 pm