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

Tony-

If you have MPEX, you can do a listf,db that will show you all of capacities
for IMAGE datasets.  You can tell it to show only those over (or under) a %
of fullness.  And with the alt___ command you can increase the capacity (if
you own the right db tool)

HELP CAPACITY


  1. DBSETCAPACITY, dataset attribute variable
  2. %DBADGALT, MPEX command
  3. %DBGENALT, MPEX command
  4. %DBMGRALT, MPEX command


I realize, of course, that you may have been wanting to something enirely
different.  If so, ignore this message.

Gary


Gary Jackson
Nevada CSOS
(530) 478-6407 - voice
(530) 478-6410 - fax