× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Barbara

Just jumping in here - seems I remember that FNDSTRPPDM does not take fields into account when run against a non-source physical file - hope this has not been said already - have been asleep!

This has been a good tool for me when looking in a library for where some value appears - anywhere - in a PF. But I've always assumed I COULD get false positives.

Vern

At 09:17 PM 8/31/2007, you wrote:

Scott Klement wrote:
>
> I'd be tempted to write my own, which would be pretty easy to do. In
> RPG it'd pretty much just be reading the flat record (without splitting
> it into fields) and running %scan() over it. And do that in a loop.
> Pretty easy.
>

If you don't split it into fields, you run the risk of getting false
hits if you get a match that spans two fields. You could do the scan
and then add a check that the location of the hit was entirely within
one fields.

And to nitpick one nit too far, I suppose you should also check that it
wasn't within a binary or packed field. 2206311169 = x'8381a301' = 'cat.'


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.