HP3000-L Archives

July 2000, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Andreas Schmidt <[log in to unmask]>
Reply To:
Date:
Tue, 4 Jul 2000 09:55:28 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (83 lines)
Hi Leonard,

the ** is strange - I suppose it's because the account is spread over several
volume sets but I can't  proove this on 5.5 PP7.
By the way, I've written two little routines which checks that all groups do
belong to the same volume set, and checks for Orphan Groups (groups only known
in the directory of a PV but not in the SysVol one's).

The PUB.SYS must exist on all PVs. This is the place where the PV's directory
table is kept (I was told by HP).

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 03/07/2000 07:19:12 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/GIS/CSC)
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

ATOM RSS1 RSS2