<html><body><p><font size="2">The third option is to specify </font><font face="Menlo-Regular">the flavor of regex desired.</font><br><font face="Menlo-Regular">Right now, if specified, must be one of these: 'x','b','f', 'ix','ib'</font><br><font face="Menlo-Regular"> 'x' extended regular expressions - the default - as implemented by regcomp and regexec library functions</font><br><font face="Menlo-Regular"> with REG_EXTENDED flag</font><br><font face="Menlo-Regular"> 'b' basic regular expressions - without REG_EXTENDED</font><br><font face="Menlo-Regular"> 'f' glob like pattern matching as implemented by fnmatch library function</font><br><font face="Menlo-Regular"> The three 'i' are similar, except upper/lower case is ignored as implemented by the library function with the</font><br><font face="Menlo-Regular"> ignore case flag or option: REG_ICASE or FNM_CASEFOLD</font><br><font size="2">We haven't published this because it is not yet fully tested.</font><br><br><font size="2">Regards, The Spectrum Scale (GPFS) team<br><br>------------------------------------------------------------------------------------------------------------------<br>If you feel that your question can benefit other users of Spectrum Scale (GPFS), then please post it to the public IBM developerWroks Forum at <a href="https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479">https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479</a>. <br><br>If your query concerns a potential software error in Spectrum Scale (GPFS) and you have an IBM software maintenance contract please contact 1-800-237-5511 in the United States or your local IBM Service Center in other countries. <br><br>The forum is informally monitored as time permits and should not be used for priority messages to the Spectrum Scale (GPFS) team.</font><br><br><img width="16" height="16" src="cid:1__=0ABB0F8CDF12170D8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Todd Ruston ---02/20/2020 03:49:22 PM---Greetings, I've been working on creating some new policy rule"><font size="2" color="#424282">Todd Ruston ---02/20/2020 03:49:22 PM---Greetings, I've been working on creating some new policy rules that will require regular expression</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Todd Ruston <truston@mbari.org></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">02/20/2020 03:49 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">[EXTERNAL] [gpfsug-discuss] Policy REGEX question</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br>Greetings,<br><br>I've been working on creating some new policy rules that will require regular expression matching on path names. As a crutch to help me along, I've used the mmfind command to do some searches and used its policy output as a model. Interestingly, it creates REGEX() functions with an undocumented parameter. For example, the following REGEX expression was created in the WHERE clause by mmfind when searching for a pathname pattern:<br><br>REGEX(PATH_NAME, '*/xy_survey_*/name/*.tif','f')<br><br>The Scale policy documentation for REGEX only mentions 2 parameters, not 3:<br><br>REGEX(String,'Pattern')<br>Returns TRUE if the pattern matches, FALSE if it does not. Pattern is a Posix extended regular expression.<br><br>(The above is from <a href="https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.2/com.ibm.spectrum.scale.v5r02.doc/bl1adv_stringfcts.htm"><u><font color="#0000FF">https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.2/com.ibm.spectrum.scale.v5r02.doc/bl1adv_stringfcts.htm</font></u></a>)<br><br>Anyone know what that 3rd parameter is, what values are allowed there, and what they mean? My assumption is that it's some sort of selector for type of pattern matching engine, because that pattern (2nd parameter) isn't being handled as a standard regex (e.g. the *'s are treated as wildcards, not zero-or-more repeats).<br><br>-- <br>Todd E. Ruston<br>Information Systems Manager<br>Monterey Bay Aquarium Research Institute (MBARI)<br>7700 Sandholdt Road, Moss Landing, CA, 95039<br>Phone 831-775-1997 Fax 831-775-1652 <a href="http://www.mbari.org"><u><font color="#0000FF">http://www.mbari.org</font></u></a><br><tt><font size="2">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><tt><font size="2"><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></font></tt><tt><font size="2"> <br></font></tt><br><br><BR>
</body></html>