Hi Tony,
   Interesting info... thanks for letting us all know.... :)  .... now, is HP
going to name this bug after you?   After all they name comets after the
finders! hehehe

Art "Interesting?  hmm... " Bahrs

>>> Tony Furnivall <[log in to unmask]> 03/02/98 02:01pm >>>
Well, there's nothing like a wierdness on a Monday to get the brain cells
back in gear!

I reported earlier to day that DBUTIL produced strange output under some
conditions. I think I've got a definitive problem statement. Many thanks to
those who provided snippets and tid-bits along the way:

When using the SM capability of doing a SHOW <database.group.account>
CAPACITY, DBUTIL does not clear the input command buffer after completing
output. SO if I follow one such command with another, where the length of
the input string for the command is shorter, DBUTIL misinterprets the
command string. The fact that it goes ahead and does the work at anyrate,
interspersing it with error messages, is merrely an added frustration!

EG

SHOW DB.Q.SDL CAPACITY
<results are as predicted>

SHOW DB.QQQ.SDL CAPACITY
<results are as predicted - the second command string is longer than the first)

but try this one:

SHOW DB.QQQ.SDL CAPACITY
<results are as predicted>

SHOW DB.Q.SDL CAPACITY
<flying flobs of fecal matter - duck!>

The error messages in question indicate that sometimes the (effective)
account name os being extended (to SDLDL in the example above) and
sometimes, if the combination is just right, an extra period is causing a
different error message.

So,  I'm comfortable that this is the case. Only happens on SHOW <database>
CAPACITY, but it is indeed an error, not a feature! I'm working with HPRC to
assign it an SR/KPR number.

And now we return to our regularly scheduled programming
Tony