Donna Garverick wrote:

> "Leonard S. Berkowitz" wrote:
>
> > ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
> >    /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
> > AMISYS             **       **        0       **        0       **
> > FSEN      245,322,128       **        0       **        0       **
> > SYS                 0       **        0       **        0       **
> > TAURUS          47760       **        0       **        0       **
>  > No groups found in group set. (CIWARN 432)
>
> the '**' for your amisys account is strange.  i thought it might be
> because your amisys account is spread over several volumes but i can't
> replicated it (on 5.5pp7)

Yes, you can. I posted on this some time ago, and have put in an S/R with
HP on it (I'll dig it up and send it to you, Leonard). It's a limitation
in the REPORT command. Any account or group with a COUNT or LIMIT over
99,999,999 sectors will display '**'. Here's how you, too, can see this
bug in action. Our INVENTRY account limit is set to 125 million sectors
and a REPORT command shows:

:report work.inventry;onvs=admin
ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
   /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
INVENTRY     92709344       **        0        0        0        0
   /WORK      4416976 86000000        0       **        0       **

Note the '**' in the LIMIT column for the account. Now let's see how high
we can go:

:altgroup work.inventry;files=99999999;onvs=admin
:report work.inventry;onvs=admin
ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
   /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
INVENTRY     92709472       **        0        0        0        0
   /WORK      4416976 99999999        0       **        0       **

That works. How about 110 million?

:altgroup work.inventry;onvs=admin;files=110000000
:report work.inventry;onvs=admin
ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
   /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
INVENTRY     92709472       **        0        0        0        0
   /WORK      4416976       **        0       **        0       **

Nope. This is bad. Unless you keep track of the limits you impose, there's
no way to get this number with REPORT; you have to use LISTGROUP (and yes,
that works). Let's change it back now:

:altgroup work.inventry;onvs=admin;files=86000000
:report work.inventry;onvs=admin
ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
   /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
INVENTRY     92709472       **        0        0        0        0
   /WORK      4416976 86000000        0       **        0       **
SYSB [/TS/PSANTUCC] {34}:

Pretty good disappearing act, eh? :-) BTW, the reason the LISTACCT command shows DISC SPACE and DISC LIMIT as "0" (zero) is probably
because that's the limit specified for the account on your system volume
set.

In my S/R I asked HP to a) enhance LISTACCT to be able to use ONVS= so you
can see the limit and space used by an account on a particular volumeset
(since, as Donna pointed out, it could be spread across several), and b)
fix REPORT to properly display more than 99,999,999 sectors.

Donna, I tried the SHOWVOL command file, but it only shows space used,
*not* LIMITs. :-(

Patrick
--
Patrick Santucci
Technical Services Analyst
Seabury & Smith, Inc.