One more addition to the list, as Ken Nutsford reminded me (and hope he
doesn't mind me repeating his comment):

> Just a comment on your recap, when we do a REPORT @.@;ONVS=TSL it
> always shows SYS/PUB with a 0 filespace-sectors in our list of private
> volume accounts and groups.  Is there an explanation for this
> incorrect reporting of PUB.SYS in the private volume domain?

The private volume directory always has an entry for the SYS account,
PUB.SYS, and the PUB group of any account(s) you have created on the
volume set.  Perhaps this is to "seed" the directory structure, or it
may some requirement of MPE; I don't know.  This is "normal", however.
For example, I have an old 7933 setup for system dumps.  It only has one
group on it (DUMP.TELESUP) that I "intended" to be there, yet the report
output shows the other enties as you noted:

ACCOUNT       FILESPACE-SECTORS     CPU-SECONDS    CONNECT-MINUTES
   /GROUP       COUNT    LIMIT    COUNT    LIMIT    COUNT    LIMIT
SYS                 0       **        0       **        0       **
   /PUB             0       **        0       **        0       **
TELESUP        241936       **        0       **        0       **
   /DUMP       241936       **        0       **        0       **
   /PUB             0       **        0       **        0       **

Jeff Kell <[log in to unmask]>