IBM Mainframe Forum

Hi,

My question may sound naive, but I have coded the following search commands:

And when the file contains "*UNMATCHED " then I get a RC0, while if it doesn't, I get a RC4.

In fact I need the other way around, RC4 if string is found, RC0 if not.

I have tried both NE instead of EQ, and OMIT instead of INCLUDE, but no difference.

Any ideas ? Thanks in advance,
George

why not try with exclude ???

Hi, Enrico, not quite what the EXCLUDE is. I also tried :

but again I get RC4 and RC0 the other way around from what I need

oops... sorry I had looked only at the code and not at the test history

I also tried:

which comes closer to what I need, but gives RC1 in case of FOUND, not RC4

George

Why do you need the RC to be reversed ?
Surely you can accommodate an RC4 by either COND= or IF / ELSE logic

Thank you expat, I had thought of it, but it won't do.

I need to intercept this new job in an existing OPC (Tivoli TWS) stream of jobs, so that it will stop the flow in case of "unexpected" records are identified. Therefore the RC0 should be in case of NOT FOUND, while RC>=4 should be in case of FOUND. If I would have to play with IF / ELSE /ENDIF I would have to build extra steps to set the RC as required. Instead I would have built a simple REXX exec to scan the file and set the RC's as required. But I find REXX interpreter an overkill for such simple case, while though that SEARCH and SORT would simplify this. But obviously they cannot.

Don't ask me why I do not set the RC's in the report generation routine, the report is generated on another node (Unix) and transferred to us by Connect Direct. Not the perfect design ... , I tend to agree, but it is now beyond our roles.

Thanks once again,

George

Finally worked with:

WHY do you need to CHANGE the RC ???

If the RC is zero do this, if not do that
Simple logic


But then what do I know after only 40+ years in the business

But well done on finding an alternative solution.