Subject: | |
From: | |
Reply To: | |
Date: | Wed, 6 Oct 1999 11:24:51 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
How about
ECHO ![finfo('/<upper case account name',12)]
> -----Original Message-----
> From: Patrick Santucci [mailto:[log in to unmask]]
> Sent: Wednesday, October 06, 1999 10:49 AM
> To: [log in to unmask]
> Subject: Need help with REPORT, LISTACCT limitations
>
>
> So far I haven't had any luck with this one, so I'm turning
> to the list
> for help. We're on 5.5 PP6.
>
> We have several accounts now that have account disc limits over 100
> million sectors. Unfortunately, when this happens we are no
> longer able to
> see exactly what the account limit is. A sample:
>
> :report xyzzy.groupins;onvs=admin
> ACCOUNT FILESPACE-SECTORS CPU-SECONDS CONNECT-MINUTES
> /GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT
> GROUPINS 94741664 99999999 0 0 0 0
> Non-existent group. (CIERR 908)
>
> Then when I do:
> :altacct groupins;files=110000000;onvs=admin
>
> I get:
> :report xyzzy.groupins;onvs=admin
> ACCOUNT FILESPACE-SECTORS CPU-SECONDS CONNECT-MINUTES
> /GROUP COUNT LIMIT COUNT LIMIT COUNT LIMIT
> GROUPINS 94741664 ** 0 0 0 0
> Non-existent group. (CIERR 908)
>
> Which *looks* like the account has *no* limit, when in fact, it does.
>
> So then I thought, "What about LISTACCT?" but I get [only the
> pertinent
> fields shown below]:
> :listacct groupins
> ********************
> ACCOUNT: GROUPINS
>
> DISC SPACE: 0(SECTORS)
> ...
> DISC LIMIT: 0(SECTORS)
> ...
>
> I think the DISC SPACE and LIMIT both say "0" because the
> account resides
> on a private volume set, not on the
> system_volume_set_with_the_ridiculously_long_name, where we keep the
> account limit at 0.
>
> So before I go to the ESC to file an S/R, does anyone out
> there know any
> way to query the system for the actual disc limit on an
> account over 100
> million sectors when it's on a private volume? If not, my S/R
> will request
> an ;ONVS= option on LISTACCT, which would make this much easier.
>
> Thanks,
> Patrick
>
|
|
|