<?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: cmviewcl output query in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276167#M706795</link>
    <description>cmviewcl adjusts fieldwidths if the name would otherwise overflow it.&lt;BR /&gt;&lt;BR /&gt;Sajith&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 14 May 2004 01:14:29 GMT</pubDate>
    <dc:creator>Sajith Abeyanayake</dc:creator>
    <dc:date>2004-05-14T01:14:29Z</dc:date>
    <item>
      <title>cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276166#M706794</link>
      <description>To automatically establish the status of a MCSG package, I need to parse the output of cmviewcl(1).  The bit that gives the package status looks like (for example):&lt;BR /&gt;&lt;BR /&gt;    PACKAGE      STATUS       STATE        AUTO_RUN     NODE&lt;BR /&gt;    DES_DATABASE up           running      enabled      kpux01&lt;BR /&gt;&lt;BR /&gt;Now in order to reliably parse this, the fields would have to be whitespace separated (i.e. at least one blank &amp;amp;/or tab).  If cmviewcl guarantees whitespace separation, then if the package name in this example was one character longer, we'd see something like this:&lt;BR /&gt;&lt;BR /&gt;    PACKAGE      STATUS       STATE        AUTO_RUN     NODE&lt;BR /&gt;    DES_DATABASE1 up           running      enabled      kpux01&lt;BR /&gt;&lt;BR /&gt;If on the other hand, cmviewcl just uses fixed-length fields then we would see something like:&lt;BR /&gt;&lt;BR /&gt;    PACKAGE      STATUS       STATE        AUTO_RUN     NODE&lt;BR /&gt;    DES_DATABASE1up           running      enabled      kpux01&lt;BR /&gt;&lt;BR /&gt;which is of course difficult to parse (or outright impossible if the package name was another character longer again, e.g. DES_DATABASE12).&lt;BR /&gt;&lt;BR /&gt;This more in the nature of an inquiry rather than a problem.&lt;BR /&gt;&lt;BR /&gt;Any suggestion welcome&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2004 00:26:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276166#M706794</guid>
      <dc:creator>Sajith Abeyanayake</dc:creator>
      <dc:date>2004-05-14T00:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276167#M706795</link>
      <description>cmviewcl adjusts fieldwidths if the name would otherwise overflow it.&lt;BR /&gt;&lt;BR /&gt;Sajith&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2004 01:14:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276167#M706795</guid>
      <dc:creator>Sajith Abeyanayake</dc:creator>
      <dc:date>2004-05-14T01:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276168#M706796</link>
      <description>cmviewcl always guarantees at least one space character between package name and package status.&lt;BR /&gt;&lt;BR /&gt;There is an enhancement request pending (SR8606217344) that requests a new option for cmviewcl to provide machine readable output, but so far the Serviceguard lab has not worked on this.&lt;BR /&gt;&lt;BR /&gt;Carsten&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2004 01:47:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276168#M706796</guid>
      <dc:creator>Carsten Krege</dc:creator>
      <dc:date>2004-05-14T01:47:16Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276169#M706797</link>
      <description>As far as I know - there is always a space...&lt;BR /&gt;&lt;BR /&gt;On all my clusters there is.&lt;BR /&gt;&lt;BR /&gt;As far as parsing, why not just &lt;BR /&gt;cmviewcl |grep up &lt;BR /&gt;or&lt;BR /&gt;cmviewcl |grep package&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 14 May 2004 08:18:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276169#M706797</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-05-14T08:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276170#M706798</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The cmcviewcl output is not a fixed length output. There is always a blank space in between words.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2004 08:24:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276170#M706798</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2004-05-14T08:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276171#M706799</link>
      <description>I always use&lt;BR /&gt;cmviewcl -p pkg1 -v&lt;BR /&gt;cmviewcl -p pkg2 -v&lt;BR /&gt;&lt;BR /&gt;Anil</description>
      <pubDate>Fri, 14 May 2004 08:26:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276171#M706799</guid>
      <dc:creator>RAC_1</dc:creator>
      <dc:date>2004-05-14T08:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276172#M706800</link>
      <description># cat chkstat&lt;BR /&gt;PKG=ignite&lt;BR /&gt;STATUS=`cmviewcl | grep $PKG | awk {'print $2'}`&lt;BR /&gt;echo $STATUS&lt;BR /&gt;&lt;BR /&gt;# ./chkstat&lt;BR /&gt;up&lt;BR /&gt;&lt;BR /&gt;-StephenD.</description>
      <pubDate>Fri, 14 May 2004 09:22:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276172#M706800</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2004-05-14T09:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: cmviewcl output query</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276173#M706801</link>
      <description>As Stephen's example demonstrates, you can find fields easily in awk.&lt;BR /&gt;&lt;BR /&gt;I would suggest looking into that for your needs since you could easily pipe the output you are looking for such as:&lt;BR /&gt;&lt;BR /&gt;cmviewcl -v | grep ^PACKAGE | awk '{whatever}'&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Kent M. Ostby&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2004 09:34:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cmviewcl-output-query/m-p/3276173#M706801</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2004-05-14T09:34:46Z</dc:date>
    </item>
  </channel>
</rss>

