× 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 Scott,

That would pretty well explain why "\s" does not work. So far I could not find any documentation of regcomp() or regexec() explaining the supported options. The only hint is "The functions regcomp(), regerror(), regexec(), and regfree() use regular expressions in a similar way to the UNIX awk, ed, grep, and egrep commands.".

"egrep" supports "\s", at least on Linux boxes I have access to.

Regards,

Thomas.

-----Ursprüngliche Nachricht-----
Von: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] Im Auftrag von Scott Klement
Gesendet: Sonntag, 3. November 2019 19:43
An: rpg400-l@xxxxxxxxxxxxxxxxxx
Betreff: Re: Regular expression (regcomp()) ccsid issue

Thomas,

Classes such as \s are not a standard part of regular expressions.  Can
you point me to documentation that states that regcomp() supports them? 
I am very skeptical that regcomp() supports nonstandard regular
expression classes like these.

I believe these were part of the Perl extensions to regular
expressions.  Java implemented them as well.   But they are not
available elsewhere except where the perl extensions are available.

-SK


On 11/3/19 10:10 AM, Tools/400 wrote:
Hi,

Hopefully somebody is smarter than me. The iSphere source member search
(using regular expressions) does not work when using character classes,
such as "\s".

Whatever I try, I cannot make it work.

I tried to convert the pattern and the value to ccsid 37 without success.

I tried retrieving the current ccsid with nl_langinfo(CODESET) and
convert the pattern and value to that ccsid without success.

Last but not least setting the locale with setLocale(LC_ALL:
LC_C_GERMANY) did not help.

Actually I wanted to change the source file search to use SQL function
REGEXP_COUNT. But that one is sooooo sloooow, that nobody wants to use
it. But at least it works.

REGEXP_COUNT takes 1644298 milliseconds when regexec() does the same job
in 8118 milliseconds. That is 200 times faster than SQL!!!

It was incredible if somebody could help me wit that. A working example
running on jobs with ccsid 37 and 273 would be great.

Regards,

Thomas.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.