message MCH2804 'Tried to go larger than storage limit for object QPGMR'

[karl Liss <kliss@xxxxxxx>]

Anyone run into this?

We are receiving message MCH2804 'Tried to go larger than storage limit
for object QPGMR'  on our model 310 running V3R2M0.  This message occurs
whenever a user performs a function that attempts to create an object.
The creation fails.

Our 310 is a development, not production, machine.  It has about 60G of
dasd.  Most of the 150 usrprfs have a group profile of QPGMR with the 
group profile becoming the owner of any new objects created.  This was 
designed to avoid the nightmare of managing objects owned by 150 
different people.  All users typically need access to the objects 
created by the other users.  Additionally, the objects created are 
commonly restored to AS/400s owned by our clients.  Since QPGMR exists
on all AS/400s we don't have to worry about object ownership converting 
to QDFTOWN at restore time.

Depending upon who we talk to at IBM we're told the message either has
something to do with reaching a maximum number of entries in a usrprf 
table or reaching a maximum size for the usrprf object QPGMR.  They 
say we've reached an architectural limit of the operating system and 
no fix is planned.  Only solution offered is to change ownership of 
some objects to another user profile.

Any ideas?  How do the really large shops cope with this?  We'd like to
keep our object management relatively simple.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *