Evaluate statemet in cobol

bnveena · New User Joined: 29 May 2007 Posts: 50 Location: hyderabad

Hello

can we use if statement while using evaluate statement in cobol???

Terry Heinze · Posted: Fri Aug 28, 2009 9:16 am

Show us what you propose, and then we can answer. Your question is a bit vague.

bnveena · New User Joined: 29 May 2007 Posts: 50 Location: hyderabad

i have 8 conditions to be checked
like if TYP-CLM= 'A' or 'B' or 'C' or 'D' till 'H'

and inside every if condition i have to check for
if WS-TOTH-UP Not = 0

so for all 8 conditions i have to check the second condition.

i want to apply evaluate condition so can u please tell me whether i can apply if condition inside evaluate??

Terry Heinze · Posted: Fri Aug 28, 2009 9:31 am

IFs can be inside EVALUATEs and EVALUATEs can be inside IFs, so yes, you can do what you want. Depending on what exactly you want to do when these conditions are met, there may be more than one way to word your statement. Can you be even more specific?

steve6 · New User Joined: 10 Jul 2007 Posts: 7 Location: Chennai

I would suggest the following;

EVALUATE TYP-CLM ALSO WS-TOTH-UP NOT = 0

WHEN 'A' ALSO TRUE
......

WHEN 'B' ALSO TRUE
......

END-EVALUATE

_______________________________________
Stephan
Knowledge grows when shared

Ketan Varhade · Posted: Fri Aug 28, 2009 10:25 am

Hi Veena,
Check for the WS-TOTH-UP in the IF condition and then check for the other condition in the evaluate condition.

Terry Heinze · Posted: Fri Aug 28, 2009 10:39 am

Given your initial post, I'd assign a condition name (88 level) to TYP-CLM, then have an IF within an IF. Unless you can be more specific about the conditions you are checking for, that's all we can suggest.

bnveena · New User Joined: 29 May 2007 Posts: 50 Location: hyderabad

Hi... I got the logic.. thnks for the suggestions

I have used evaluate and if together its running fine

Terry Heinze · Posted: Fri Aug 28, 2009 11:10 am

Can you show us the code you decided on? As I said earlier, there are probably several ways to accomplish the end result and some are easier to maintain than others.

bnveena · New User Joined: 29 May 2007 Posts: 50 Location: hyderabad

Ketan Varhade · Posted: Fri Aug 28, 2009 11:53 am

Hi Veena,
Both of the if condtion in each of the case is diff so , i dont think so that u can check for the if condtion before the evaluate you need to check inside the case statement.

Terry Heinze · Posted: Fri Aug 28, 2009 12:02 pm

Given the fact that the 8 different values of TYP-CLM-TOT deal with 8 different fields, your solution is what I would've written too, except that what happens if WS-TCLN-AE = zero? It's okay if WS-PCT-DAYS30 has been previously initialized to zero. If not, it will not have a valid value. You could eliminate the IF by replacing the DIVIDE statement by:

GuyC · Posted: Fri Aug 28, 2009 12:29 pm

I would have stored WS-TCLN-AE ..WS-TCLN-AP in an array

Terry Heinze · Posted: Fri Aug 28, 2009 7:18 pm

veena,
As you can see, there are usually many variations that will yield the correct result. Try to pick one that is flexible enough for future changes and is easily understood by the next person who maintains the code. Because of CPU speeds these days, worry less about performance of an individual statement (there are exceptions of course) and more about maintainability.