(gosh, it's quiet today :-)

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

> MPE/iX:LISTACCT AMISYS
>
> The following is the output returned from LISTACCT. Note DISC SPACE: 0(SECTORS)
> for the AMISYS account. (I just noticed that the account has PM; I will have to
> find out why this is the case):
>
> ********************
> ACCOUNT: AMISYS
>
> DISC SPACE: 0(SECTORS)          PASSWORD: **
> CPU TIME  : 7708847(SECONDS)    LOC ATTR: $00000000
> CONNECT TIME: 980421(MINUTES)   SECURITY--READ    : ANY
> DISC LIMIT: 0(SECTORS)                    WRITE   : ANY
> CPU LIMIT : UNLIMITED                     APPEND  : ANY
> CONNECT LIMIT: UNLIMITED                  LOCK    : ANY
> MAX PRI  : 150                            EXECUTE : ANY
> GRP UFID : $05630003 $0BCD01D2 $000732C6 $17831C48 $0354A8D5
> USER UFID: $00000000 $00000000 $00000000 $00000000 $00000000
> CAP: AM,AL,GL,OP,CV,UV,LG,NM,CS,ND,SF,BA,IA,PM,MR,DS,PH
>
> Now I know independently (MPEX) that the AMISYS account has 1,224,270,400. Can
> the reason for the ** in the REPORT output and the 0(SECTORS) in the LISTACCT
> output be a numerical overflow?

it could be.  afaik, though, the 0 sectors for listacct is normal for accounts on
private volumes.

> If so, will this be fixed in 6.5? The only
> machine here that has 6.5, so far, does not have enough files to test 1 billion
> or more sectors.

that's a very good question.  i'd (at least) call the rc...although they probably
won't be able to answer your question.  you have an ase or a rc advocate, yes?  i'd
get them busy on answering your questions.....

> Something else that I just noticed in the REPORT command output. SYS shows up as
> having a group on this particular user volume. When I check further (REPORT
> @.SYS;ONVS=PHC_DEVL), I find that it is PUB. A LISTGROUP PUB.SYS indicates that
> it resides on the system volume set. Can someone explain this?

other than it's normal, i don't have much of an explanation.  i suspect it's mpe's
way of keeping track of all the private volumes on the system.

let me suggest you hop over to tim's site at denkor and pick up 'showvol'.  this is
a real handy little script for reporting where each group in an account lives and
how many sectors each group is using.              - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<