Hi Donna,

Subsys 200 is 'traps'. I cannot find what '52' means at the moment, it's
supposed to be the 'trap code'.

Some years ago I encounted a similar problem, the 'info' being 12 in
that case a bounds violation. This old service request was 5003-180596
(1994). The cause of that old problem (and perhaps your current problem)
was that drives have there own unique ways of responding to a poll. The
problem only occured when 'dstatus' was used.  The code in VOLUTIL
that parses the poll return trapped because rather than getting back
a binary vendor string it gets back an ASCII string. For example, a C2203
responds with a hex '02203000' whereas a C2474S returns the string
"C2474S".

The peculiar aspect of this old problem was that VOLUTIL seemed not to
always trap when this happened. I tried to force the problem by intercepting
the poll return and modifying it to look like that used by the reporting
customer. They run VOLUTIL and it trapped, I do the same thing and it
just prints gibberish for the volume type, ie. C2474S reports as being
a type "433234" (C247 is hex 43323437!).

So, it seems that you might be seeing the problem described in SR
5003-180596.  It's easy to confirm but it requires running VOLUTIL with
debug and setting break points. I don't think that original problem ever got
fixed and I do not know why that would be either! Perhaps a call to the HPRC
would help?

Hope this helps!

Bill
HP/CSY



>hi all!
>
>any profound explanation for the following from volutil?
>
>volutil: showset dev_set1 dstatus
>
>Volume name:               State:   Ldev:      Type:
>Path:
>-----------                -----    ----       ----
>----
>
>  MASTER
>
>*Error: Subsys     200, Info:      52.
>
><sigh>         - d
>
>--
>Donna Garverick     Sr. System Programmer
>925-210-6631        [log in to unmask]
>
>"Unix _is_ user friendly.
>It's just very selective about who its friends are.
>And sometimes even best friends have fights."
>
>>>>MY opinions, not Longs Drug Stores'<<<
>