Multiple checks in a WHEN clause

Kamlesh Kamal · Posted: Mon Sep 28, 2009 8:56 pm

Hi,

Can anyone confirm if this WHEN clause will work?

dick scherrer · Posted: Mon Sep 28, 2009 9:12 pm

Hello,

What happens if the code only checks for NOT EQUAL TO '72'? Does this evaluate true?

Robert Sample · Posted: Mon Sep 28, 2009 9:23 pm

dick scherrer · Posted: Mon Sep 28, 2009 9:27 pm

Hi Robert - welcome "back"

d

Kamlesh Kamal · Posted: Mon Sep 28, 2009 9:32 pm

Hi,

Got your point..Now I have divided my logic in two separate parts.

dbzTHEdinosauer · Posted: Mon Sep 28, 2009 9:43 pm

Why don't you get rid of that dumb NOT and:

Kamlesh Kamal · Posted: Mon Sep 28, 2009 10:20 pm

That can't be done I guess as I have to check for both the condition NOT EQUAL TO 72 AND the other ORs that I have..

Robert Sample · Posted: Mon Sep 28, 2009 11:05 pm

Thanks, Dick -- it was a nice vacation (although it rained every port, at least the ship was enjoyable).

Kamlesh, changing NOT EQUAL TO to IS NOT EQUAL TO is not going to change the COBOL results -- the two phrases are considered the same by COBOL. As you now have it coded, if the first two bytes of SPEC-PSTN-CD OF DCLTCSEPIPRDCR are equal to '72' then the condition evaluates to false and the rest of the condition will not be evaluated as per COBOL rules cited above. So have you verified that you have data records with something other than '72' in the first two bytes of SPEC-PSTN-CD OF DCLTCSEPIPRDCR?

The rule of thumb is that COBOL evaluates only as much as it has to; if a partial evaluation of a complex OR condition comes up TRUE, then the expression is going to be TRUE and COBOL stops evaluating at that point; similarly, if a partial evaluation of a complex AND condition comes up FALSE, then the expression is going to be FALSE and COBOL stops evaluating at that point.

dick scherrer · Posted: Tue Sep 29, 2009 12:29 am

Hello,

Terry Heinze · Posted: Tue Sep 29, 2009 1:09 am

In addition to the other suggestions, I would add that your EVALUATE is so wordy that it is difficult for many to understand. One option is to move POOL-CD OF DCLTCMPRDCR-ERN-DTL and SPEC-PSTN-CD OF DCLTCSEPIPRDCR(1:2) to field names and reference them by using condition names (88 levels).