BIF %Found trouble

[Guest.Visitor]

Has anyone had any trouble using %Found on a SetLL???? I am having a problem with this in my program and no it isn't working properly. Has anyone applied a PTF that fixed it??? I can't figure out why it doesn't work. * C MSTPKEY SETLL TSLSTOP5 C IF %FOUND(TSLSTOP5) Here is my code, and I know for a fact the record doesn't exist, but it passes the check and executes the rest of the code.

[B.Myrick]

Trevor, I will try this on my machine. I don't use this method, but I was wondering: Since this is an op code associated with READx, perhaps the %EOF bif would be better suited for this operation. -bret

[Guest.Visitor]

Thanks Bret, I have used it like this at a previous shop, but can't seem to get it to work here. Out on the redbooks it says that it can be used for the following, so it SHOULD work, but ya know how that goes :-). File Operations: Chain Delete SetGt SetLL String Ops: Thnx for checking Trev Check CheckR Scan Search: LookUp

[Guest.Visitor]

Trevor, You want %Equal, not %Found. From the manual:

 The resulting indicators reflect the status of the operation. You can specify an indicator in positions 71-72 that is set on when the search argument is greater than the highest key or relative record number in the file. This information can also be obtained from the %FOUND built-in function, which returns '0' if no record is found, and '1' if a record is found. You can specify an indicator in positions 75-76 that is set on when a record is present whose key or relative record number is equal to the search argument. This information can also be obtained from the %EQUAL built-in function, which returns '1' if an exact match is found. 

Bill

[B.Myrick]

Trevor, Here is what I wrote: *************** Beginning of data ****************** foehdrflg if e k disk c key klist c kfld oeord# c kfld oeosfx c eval oeord# = 1 c key setll oehdrflg c if %found c eval oeosfx = 123 c oeosfx dsply c endif c oeosfx dsply c eval *inlr = *on ****************** End of data ********************* Order # 1 does not exist in the OEHDRFLG file. I know the %found does not indicate a found record in this instance. This is again confirmed when the DSPLY of OEOSFX results in '0' (ZERO). -bret

[B.Myrick]

Bill, Good point, but in many cases I don't want %equal, because I am positioning inside the file, based on data entered by the user. Don't expect too many exact matches when they key in a part description or customer name. -bret

[Guest.Visitor]

Bret, I agree, but in the "usual" circumstances, a Setll preceedes a Read which is looped. In this case any kind of conditioning on the Setll is superfluous. The only good use for the %Found condition that I can think of right now would be to use a conditional logic branch to load a "No records found at search position" message in a subfile. This would be a bit neater than checking the RRN of the subfile to see if any records had been loaded. Bill

[Guest.Visitor]

Bill, Basically in my application, I know that the record does not exist therefore, when using the %Found it should be '0'........it is not though, it is coming back as a '1' as if it found it. If I were to use the %Equal why would this work and not the %Found. Trev

[Guest.Visitor]

Bret, With the code you provided, did this work for you???? -Trev

[B.Myrick]

Yes it worked. Otherwise I would not have put it on the forum. Quite an EGO I have actually. Did you have problems with it compiling? I am on V4R4M0 if that makes any difference. What results (if any) did you get? -bret