Hi Tony,
   um... you seem to imply that you are not physically connected with the
machine containing the databases.... this further implies that you are using
either a modem or 'telnet-type' connection...

    Could you be having some line noise adding "letters" to the account name?

    I suggest this because one of our vendors occasionally has trouble logging
into our 957 'cause they have a lot of line noise at their end ... (of course it
couldn't be at our end :) hehehe) They find that the line noise corrupts their
passwords alot???

Art "Short-Timer :) " Bahrs

>>> Tony Furnivall <[log in to unmask]> 03/02/98 06:41am >>>
Hi there DB Gurus!
I am experiencing some strange output from DBUTIL when trying to capture
dataset capacities.
Here is what I'm doing:

1.  Using MPEX to get a listing of all Image root files on a system
2.  Using this list as input to DBUTIL to create a list of all datasets
capacities on a system
3.  Piping this list to a scanning utility to perform predictive expansion
on datasets.

This at least is the goal! It is not feasible to create "creator" access to
the database with QUERY, so I am using the MANAGER.SYS and DBUTIL SHOW
<database> CAPACITY approach, because this must work with several thousand
database on many widely distributed network nodes.

My problem is that when I use the SHOW <database> CAPACITY command from
MANAGER.SYS, I <sometimes> get a message that the specified account name is
too long ( it isn't, it's only 7 characters!). I can get in using QUERY and
do a FO SETS, because in some instances I know the available passwords.
HOwever, Each site is able to change things to suit themselves, and I can't
always do this.

Anybody else ever encountered this strange behavior? Am I overlooking
something "Duh"ish? Is this merely a Monday Morning Manifestation?

Your help is eagerly solicited!

Tony "Scratching his head in frustration" Furnivall