When groups are created the NEWGROUP command, if you don't specify what
VOLUME SET to place them in, it will default to the SYSTEM VOLUME SET (bad
default choice IMHO, should not be a default) . In the event you place
files in the group before specifying what volume set, they are there to
stay. I suggest you issue a LISTGROUP @ from the AMISYS account and you
will probably find quite a few on the system set. MPEX may have a work
around such as a VEAUDIT COPY command (nice feature). I have made a command
file for my account managers that will create groups form them in the
specified volume sets we use.
Example:
NEWGROUP TEST.SGAII;ONVS=SG_VOLUME_SET
NEWGROUP TEST.SGAII;HOMEVS=SG_VOLUME_SET
HTH
Jeff O. Harrison, Systems Engineer
Information Technology
Tele: (615)749-6476
Fax: (615)749-6598
Pager: (615)923-1431
Email: [log in to unmask]
-----Original Message-----
From: Leonard S. Berkowitz
[SMTP:[log in to unmask]]
Sent: Monday, July 03, 2000 12:19 PM
To: [log in to unmask]
Subject: [HP3000-L] Unexpected REPORT and LISTACCT command
output
I am accustomed to execute the REPORT command for a group that
exists in none of
out accounts in order to obtain a quick listing of file at the
account level:
MPE/iX:REPORT ZXQW.@;ONVS=PHC_DEVL
The following is the output returned from REPORT (I put the commas
in for
readability). Note the ** for the AMISYS account:
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)
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? 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.
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?
Thanks.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-3737
pager: 781-226-2431
|
