cmviewcl output query

[Sajith Abeyanayake]

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):

PACKAGE STATUS STATE AUTO_RUN NODE
DES_DATABASE up running enabled kpux01

Now in order to reliably parse this, the fields would have to be whitespace separated (i.e. at least one blank &/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:

PACKAGE STATUS STATE AUTO_RUN NODE
DES_DATABASE1 up running enabled kpux01

If on the other hand, cmviewcl just uses fixed-length fields then we would see something like:

PACKAGE STATUS STATE AUTO_RUN NODE
DES_DATABASE1up running enabled kpux01

which is of course difficult to parse (or outright impossible if the package name was another character longer again, e.g. DES_DATABASE12).

This more in the nature of an inquiry rather than a problem.

Any suggestion welcome

[Sajith Abeyanayake]

cmviewcl adjusts fieldwidths if the name would otherwise overflow it.

Sajith

[Carsten Krege]

cmviewcl always guarantees at least one space character between package name and package status.

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.

Carsten

[Geoff Wild]

As far as I know - there is always a space...

On all my clusters there is.

As far as parsing, why not just
cmviewcl |grep up
or
cmviewcl |grep package

Rgds...Geoff

[Sanjay_6]

Hi,

The cmcviewcl output is not a fixed length output. There is always a blank space in between words.

Hope this helps.

Regds

[RAC_1]

I always use
cmviewcl -p pkg1 -v
cmviewcl -p pkg2 -v

Anil

[Stephen Doud]

# cat chkstat
PKG=ignite
STATUS=`cmviewcl | grep $PKG | awk {'print $2'}`
echo $STATUS

# ./chkstat
up

-StephenD.

[Kent Ostby]

As Stephen's example demonstrates, you can find fields easily in awk.

I would suggest looking into that for your needs since you could easily pipe the output you are looking for such as:

cmviewcl -v | grep ^PACKAGE | awk '{whatever}'

Best regards,

Kent M. Ostby