<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Regular expression matching in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313177#M876313</link>
    <description>Hi Simon,&lt;BR /&gt;the reason why echo&lt;BR /&gt;"B.11.11" | grep -E "?.10.*|?.11.*"&lt;BR /&gt;&lt;BR /&gt;fails is that the -E specifies a so-called extended regular expression, and the question mark means - for an extended regular expression: one or more occurrances of the preceeding character. If there is no preceeding character, the expression fails, hence the need for a space (or another char.)&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;John K.&lt;BR /&gt; &lt;BR /&gt;  &lt;BR /&gt;</description>
    <pubDate>Thu, 24 Jun 2004 03:38:06 GMT</pubDate>
    <dc:creator>john korterman</dc:creator>
    <dc:date>2004-06-24T03:38:06Z</dc:date>
    <item>
      <title>Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313170#M876306</link>
      <description>Trying to get my head round a regexp problem.&lt;BR /&gt;&lt;BR /&gt;From swlist, you can get, for a piece of installed software, the os_release(s) it can run on.  This will be an extended regular expression, like the following examples: -&lt;BR /&gt;&lt;BR /&gt;B.11.00|B.11.11|B.11.20&lt;BR /&gt;B.11.*&lt;BR /&gt;?.10.*|?.11.*&lt;BR /&gt;&lt;BR /&gt;All three of these should match "B.11.11", for example.  So to test this: -&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E "B.11.00|B.11.11|B.11.20" (this works)&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E "B.11.*" (this works)&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E "?.10.*|?.11.*" (this fails)&lt;BR /&gt;&lt;BR /&gt;The error given is: -&lt;BR /&gt;&lt;BR /&gt;grep: ?, *, or + not preceded by valid regular expression&lt;BR /&gt;&lt;BR /&gt;If I precede the ? symbols with spaces, it works.  But why?  I want to feed my script arbitrary extended regular expressions and not worry about it throwing these wierd errors.  So what's causing them?&lt;BR /&gt;&lt;BR /&gt;Cheers, Sy</description>
      <pubDate>Wed, 23 Jun 2004 09:46:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313170#M876306</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-23T09:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313171#M876307</link>
      <description>(oh, and I will ultimately be doing these matches within awk, where I currently get the same error, but using grep -E just for illustration purposes)</description>
      <pubDate>Wed, 23 Jun 2004 09:47:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313171#M876307</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-23T09:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313172#M876308</link>
      <description>in grep -E (and perl and awk) '.' (the dot) is magic, and not taken as literal&lt;BR /&gt;&lt;BR /&gt;in perl, and your version of grep (there are sooo many versions of grep around that you cannot generalize) the '?' is a quantifier, meaning "zero or one occurance"&lt;BR /&gt;&lt;BR /&gt;grep/awk/perl regexes are not even close to sh-regexes&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E '.\.10\..*|.\.11\..*'&lt;BR /&gt;&lt;BR /&gt;is more likely to meet what you mean, but that's easier written with a character class instead of an alternation&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E '.\.1[01]\..*'&lt;BR /&gt;&lt;BR /&gt;And since trailing .* is only time consuming (zero or more of any character will always match)&lt;BR /&gt;&lt;BR /&gt;echo "B.11.11" | grep -E '.\.1[01]\.'&lt;BR /&gt;&lt;BR /&gt;Should do the trick&lt;BR /&gt;&lt;BR /&gt;Enjoy, Have FUN! H.Merijn</description>
      <pubDate>Wed, 23 Jun 2004 10:03:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313172#M876308</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2004-06-23T10:03:06Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313173#M876309</link>
      <description>Thanks for that.  Problem is though, I need to basically ask "is this piece of software installable on 11.00, 11.11, 11.23, 10.20 etc".  So I need to parse the expressions given to me from swlist, which is the format I gave.&lt;BR /&gt;&lt;BR /&gt;Is there another tool that will let me match against that format of expression?</description>
      <pubDate>Wed, 23 Jun 2004 10:05:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313173#M876309</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-23T10:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313174#M876310</link>
      <description>1. swinstall won't let you install software that doesn't meet the system architecture&lt;BR /&gt;&lt;BR /&gt;2. My statements still holds. You asked about the regular expression, and I explained. grep doesn't care what the input is from :)&lt;BR /&gt;&lt;BR /&gt;swlist -options | grep pattern&lt;BR /&gt;&lt;BR /&gt;a5:/u/usr/merijn 105 &amp;gt; swlist | grep '[         ][ABC]\.11'&lt;BR /&gt;  B3901BA                       B.11.02.06     HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800)&lt;BR /&gt;  B6192AA                       B.11.00.10     DCE/9000 Programming &amp;amp; Administration Tools Media and Manuals&lt;BR /&gt;  B6733AA                       B.11.00.10     DCE/9000 Kernel Threads Support&lt;BR /&gt;  HPUXEng64RT                   B.11.00        English HP-UX 64-bit Runtime Environment&lt;BR /&gt;  HWE1100                       B.11.00.0403.3 Hardware Enablement Patches for HP-UX 11.00, March 2004&lt;BR /&gt;  J2793B                        B.11.00.07     High Performance X.25 Link software for HP 9000&lt;BR /&gt;  OnlineDiag                    B.11.00.27.18  HPUX 11.00 Support Tools Bundle, Mar 2004&lt;BR /&gt;  QPK1100                       B.11.00.64.4   Quality Pack for HP-UX 11.00, March 2004&lt;BR /&gt;  UnlimUserLic                  B.11.00.02     HP-UX Unlimited-User License&lt;BR /&gt;  PHCO_26075                    1.0            q4 patch version B.11.20f&lt;BR /&gt;  PHCO_26823                    B.11.00.16     HP Array Manager/60 cumulative patch&lt;BR /&gt;  PHCO_28069                    1.0            q4 patch version B.11.22l&lt;BR /&gt;  PHSS_25714                    1.0            Shared libF90 B.11.01.12&lt;BR /&gt;  PHSS_28706                    1.0            ANSI C compiler B.11.11.06 cumulative patch&lt;BR /&gt;  Predictive                    C.11.00.24.01  HP Predictive Support&lt;BR /&gt;a5:/u/usr/merijn 106 &amp;gt;&lt;BR /&gt;&lt;BR /&gt;in this command I entered '[' 'space' 'Ctrl-V Tab' ']' (to clear the forum compression of whitespace)&lt;BR /&gt;&lt;BR /&gt;a5:/u/usr/merijn 106 &amp;gt; swlist | perl -ne '/\b[ABC]\.11/ and print'&lt;BR /&gt;  B3901BA                       B.11.02.06     HP C/ANSI C Developer's Bundle for HP-UX 11.00 (S800)&lt;BR /&gt;  B6192AA                       B.11.00.10     DCE/9000 Programming &amp;amp; Administration Tools Media and Manuals&lt;BR /&gt;  B6733AA                       B.11.00.10     DCE/9000 Kernel Threads Support&lt;BR /&gt;  HPUXEng64RT                   B.11.00        English HP-UX 64-bit Runtime Environment&lt;BR /&gt;  HWE1100                       B.11.00.0403.3 Hardware Enablement Patches for HP-UX 11.00, March 2004&lt;BR /&gt;  J2793B                        B.11.00.07     High Performance X.25 Link software for HP 9000&lt;BR /&gt;  OnlineDiag                    B.11.00.27.18  HPUX 11.00 Support Tools Bundle, Mar 2004&lt;BR /&gt;  QPK1100                       B.11.00.64.4   Quality Pack for HP-UX 11.00, March 2004&lt;BR /&gt;  UnlimUserLic                  B.11.00.02     HP-UX Unlimited-User License&lt;BR /&gt;  PHCO_26075                    1.0            q4 patch version B.11.20f&lt;BR /&gt;  PHCO_26823                    B.11.00.16     HP Array Manager/60 cumulative patch&lt;BR /&gt;  PHCO_28069                    1.0            q4 patch version B.11.22l&lt;BR /&gt;  PHSS_25714                    1.0            Shared libF90 B.11.01.12&lt;BR /&gt;  PHSS_28706                    1.0            ANSI C compiler B.11.11.06 cumulative patch&lt;BR /&gt;  Predictive                    C.11.00.24.01  HP Predictive Support&lt;BR /&gt;a5:/u/usr/merijn 107 &amp;gt;&lt;BR /&gt;&lt;BR /&gt;Enjoy, Have FUN! H.Merijn</description>
      <pubDate>Wed, 23 Jun 2004 10:17:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313174#M876310</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2004-06-23T10:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313175#M876311</link>
      <description>hai,&lt;BR /&gt;&lt;BR /&gt; echo "B.11.11" | grep -E "?.10.*|?.11.*" will make problem. If you use the special characters as like ?,*,+ in the regexp.&lt;BR /&gt;&lt;BR /&gt; Check regexp(5) man page for special characters. To sperate the ERE's on the regexp use the new line character \ or space in that.&lt;BR /&gt;&lt;BR /&gt; echo "B.11.11" | grep -E " ?.10.* | ?.11.*"&lt;BR /&gt;&lt;BR /&gt; It will work now.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Muthukumar.</description>
      <pubDate>Wed, 23 Jun 2004 10:32:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313175#M876311</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-06-23T10:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313176#M876312</link>
      <description>Hmmm, I think I need to explain what I'm trying to achieve.&lt;BR /&gt;&lt;BR /&gt;I know swinstall will only let it install software destined for it.  What I'm doing is scripting the automatic updating of a software asset database.  Basically swlist on all our servers, and populate a database with information about our software base.&lt;BR /&gt;&lt;BR /&gt;Within the database, we have flags for each software saying whether it's "10.20", "11.00", "11.11" etc compatible.  It can be one or more of these.&lt;BR /&gt;&lt;BR /&gt;What I need to do is, for any given regexp extracted from swlist, as it whether it's compatible with each of those releases in turn, and set TRUE if it is.&lt;BR /&gt;&lt;BR /&gt;So you see, I can't use different regexps, I can't really change them (though I guess I could do a sed to replace "?" with " ?" but would that solve it?)&lt;BR /&gt;&lt;BR /&gt;See?&lt;BR /&gt;&lt;BR /&gt;Cheers, Sy</description>
      <pubDate>Thu, 24 Jun 2004 03:09:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313176#M876312</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-24T03:09:09Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313177#M876313</link>
      <description>Hi Simon,&lt;BR /&gt;the reason why echo&lt;BR /&gt;"B.11.11" | grep -E "?.10.*|?.11.*"&lt;BR /&gt;&lt;BR /&gt;fails is that the -E specifies a so-called extended regular expression, and the question mark means - for an extended regular expression: one or more occurrances of the preceeding character. If there is no preceeding character, the expression fails, hence the need for a space (or another char.)&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;John K.&lt;BR /&gt; &lt;BR /&gt;  &lt;BR /&gt;</description>
      <pubDate>Thu, 24 Jun 2004 03:38:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313177#M876313</guid>
      <dc:creator>john korterman</dc:creator>
      <dc:date>2004-06-24T03:38:06Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313178#M876314</link>
      <description>Hmm, I can see this isn't going to be easy, then.&lt;BR /&gt;&lt;BR /&gt;According to the regexp manpage, as you say, "?" means "zero or one of the previous character", and "*" means "zero or more of the previous character".&lt;BR /&gt;&lt;BR /&gt;However, in the patterns from swlist, the "*" means "anything" and the "?" means any one character (like "." in regexp), and "." actually should mean the "." character rather than "any one character", as in regexp.&lt;BR /&gt;&lt;BR /&gt;Erk, this isn't going to be as easy as I'd hoped!&lt;BR /&gt;&lt;BR /&gt;One (crude) solution I've found, is that if I create a temporary directory with files called B.10.20, B.11.00, B.11.11 etc, then do ls pattern_from_swlist, then it displays the releases that match.  But this is crude, and doesn't work with the |, so this would need cutting end executing multiple times for each pattern.&lt;BR /&gt;&lt;BR /&gt;There must be a cleaner way?&lt;BR /&gt;&lt;BR /&gt;touch B.10.20 B.11.00 B.11.11 B.11.23&lt;BR /&gt;ls [AB].1?.*&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Jun 2004 04:21:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313178#M876314</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-24T04:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313179#M876315</link>
      <description>Hi again,&lt;BR /&gt;have you considered something like this:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;swlist -l patch | while read line&lt;BR /&gt;do&lt;BR /&gt;case "$line" in&lt;BR /&gt;      *B.10.20*|*B.11.00*|*B.11.11*|*B.11.23*) echo "$line";&lt;BR /&gt;esac&lt;BR /&gt;done&lt;BR /&gt; &lt;BR /&gt;regards,&lt;BR /&gt;John K.</description>
      <pubDate>Thu, 24 Jun 2004 05:47:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313179#M876315</guid>
      <dc:creator>john korterman</dc:creator>
      <dc:date>2004-06-24T05:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313180#M876316</link>
      <description>hai,&lt;BR /&gt;&lt;BR /&gt; To get the installed products with the o/s version category as like as 10.00 11.00 11.11 11.22 or 11.23,choose the regexp as like&lt;BR /&gt;&lt;BR /&gt; 11.23&lt;BR /&gt; swlist | grep -v "^#" | grep -v "^$" | grep -E "[A-Z]?\.11\.23"  &amp;gt;&amp;gt; /tmp/11.23_products.log&lt;BR /&gt;&lt;BR /&gt; 11.22&lt;BR /&gt; swlist | grep -v "^#" | grep -v "^$" | grep -E "[A-Z]?\.11\.22"  &amp;gt;&amp;gt; /tmp/11.22_products.log&lt;BR /&gt;&lt;BR /&gt; Change the regexp pattern only.&lt;BR /&gt; "[A-Z]?\.11\.0"&lt;BR /&gt;&lt;BR /&gt; To get 11.* version products&lt;BR /&gt; "[A-Z]?\.11\.[1-9]?"&lt;BR /&gt; &lt;BR /&gt; [A-Z]? - 1 or more A-Z variable&lt;BR /&gt; \.11\. - .11. format after that&lt;BR /&gt; [1-9]? - 1 or more 1-9 digits&lt;BR /&gt;&lt;BR /&gt; [A-Z] - we can use [[:upper:]] and&lt;BR /&gt; [1-9] - we can use [[:digit:]] classes as in regexp man page.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Muthukumar</description>
      <pubDate>Thu, 24 Jun 2004 06:05:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313180#M876316</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2004-06-24T06:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313181#M876317</link>
      <description>Cheers for answers all, I've not figured a solution.&lt;BR /&gt;&lt;BR /&gt;Basically I'm translating the "swlist expression" into a regexp by translating: -&lt;BR /&gt;&lt;BR /&gt;all "." to "\." (fixed dots)&lt;BR /&gt;all "?" to "."  (any single character)&lt;BR /&gt;all "*" to ".*" (zero or more "anythings")&lt;BR /&gt;&lt;BR /&gt;This seems to work, giving regexps as follows which I can use in awk: -&lt;BR /&gt;&lt;BR /&gt;* ----&amp;gt; .*&lt;BR /&gt;?.10.* ----&amp;gt; .\.10\..*&lt;BR /&gt;?.10.*|?.11.* ----&amp;gt; .\.10\..*|.\.11\..*&lt;BR /&gt;?.10.20 ----&amp;gt; .\.10\.20&lt;BR /&gt;?.11.* ----&amp;gt; .\.11\..*&lt;BR /&gt;?.11.00 ----&amp;gt; .\.11\.00&lt;BR /&gt;?.11.1* ----&amp;gt; .\.11\.1.*&lt;BR /&gt;?.11.11 ----&amp;gt; .\.11\.11&lt;BR /&gt;?.11.?? ----&amp;gt; .\.11\...&lt;BR /&gt;?.11.[01]* ----&amp;gt; .\.11\.[01].*&lt;BR /&gt;?.11.[01]? ----&amp;gt; .\.11\.[01].&lt;BR /&gt;?.1?.* ----&amp;gt; .\.1.\..*&lt;BR /&gt;?.1?.[0-9][0-9] ----&amp;gt; .\.1.\.[0-9][0-9]&lt;BR /&gt;B.10.00|B.10.01|B.10.10|B.10.20 ----&amp;gt; B\.10\.00|B\.10\.01|B\.10\.10|B\.10\.20&lt;BR /&gt;B.10.01|B.10.10|B.10.20 ----&amp;gt; B\.10\.01|B\.10\.10|B\.10\.20&lt;BR /&gt;B.10.10|B.10.20 ----&amp;gt; B\.10\.10|B\.10\.20&lt;BR /&gt;B.10.20 ----&amp;gt; B\.10\.20&lt;BR /&gt;B.11.00 ----&amp;gt; B\.11\.00&lt;BR /&gt;B.11.11 ----&amp;gt; B\.11\.11&lt;BR /&gt;[AB].1?.?? ----&amp;gt; [AB]\.1.\...</description>
      <pubDate>Thu, 24 Jun 2004 08:54:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313181#M876317</guid>
      <dc:creator>Simon Hargrave</dc:creator>
      <dc:date>2004-06-24T08:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: Regular expression matching</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313182#M876318</link>
      <description>If you are trying to build a list of products with the associated OS version for searches, then how about simplifying the OS version into a simple number. Here is a perl script that can do that.&lt;BR /&gt; &lt;BR /&gt;%vers=("B.10.20",1,"B.11.00",2,"B.11.11",3,"B.11.20",4);&lt;BR /&gt;open(INP,"swlist -R|");&lt;BR /&gt;while(&lt;INP&gt;) {&lt;BR /&gt; chomp;&lt;BR /&gt; /^(.).(\S+)\s+(\S+)\s+(.*)/;&lt;BR /&gt; next if $1 eq "#";&lt;BR /&gt; $name=$2; $ver=$3; $desc=$4;&lt;BR /&gt; if ($ix=$vers{substr($ver,0,7)}) { print join("\t",$ix,$name,$ver,$desc),"\n"; }&lt;BR /&gt;}&lt;BR /&gt; &lt;BR /&gt;This script will parse the swlist output and classify the OS version. As long as you include the possible OS versions in variable "%vers" and map it to a unique number.&lt;BR /&gt; &lt;BR /&gt;Then you get an output like this-&lt;BR /&gt;2       HPUXBaseAux.OBAM.OBAM-WEB       B.11.00.05.3.06 Web Application Server Support&lt;BR /&gt;3       HPUXBaseAux.Judy-lib.JUDY       B.11.11.04.13   Judy Library and Related files 20020319.213255 PA&lt;BR /&gt;3       HPUXBaseAux.Judy-lib.JUDY-COMMON        B.11.11.04.13   Judy Library and Related COMMON files 20020319.213255&lt;BR /&gt;3       HWEnable11i     B.11.11.0306.4  Hardware Enablement Patches for HP-UX 11i, June 2003&lt;BR /&gt; &lt;BR /&gt;"2" is for 11.00 and "3" is for 11.11. The script only looks at the first 7 characters of the revision. Send the output of this script to a file and you can scan based on the mapped numbers for specific OS version.&lt;BR /&gt; &lt;BR /&gt;HTH&lt;BR /&gt; &lt;BR /&gt;-- Rod Hills&lt;/INP&gt;</description>
      <pubDate>Thu, 24 Jun 2004 09:45:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/regular-expression-matching/m-p/3313182#M876318</guid>
      <dc:creator>Rodney Hills</dc:creator>
      <dc:date>2004-06-24T09:45:06Z</dc:date>
    </item>
  </channel>
</rss>

