Hi,

i just tried this command and noticed, that you have to be logged on as the creator in the db-group. Otherwise, the command fails!

If you like, i can give you a source (cobol) of a little program, that i have written a few years ago to report db-capacity into a disc-file. If you do a few modifications, this might fulfill you needs. Email me privately, if you are interested.

Kind regards

Klaus Franke

-----Ursprüngliche Nachricht-----
Von:    Tony Furnivall [SMTP:[log in to unmask]]
Gesendet am:    Montag, 2. März 1998 15:42
An:     [log in to unmask]
Betreff:        Strange output from DBUTIL

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